semantic-git by siviter-xyz/dot-agent
npx skills add https://github.com/siviter-xyz/dot-agent --skill semantic-git使用约定式提交格式管理 Git 提交,实现原子化提交和简洁的提交信息。
此技能兼容 zagi,专为与 AI IDE(如 Cursor 等)良好协作而设计。
zagi(一个为智能体设计的更好的 Git 接口)。
git 被别名设置为 zagi,或zagi 二进制文件。git 视为可能兼容 zagi 的工具,避免使用生僻的标志。git 命令,让任何 git → zagi 的集成来处理它们。广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
git。git 命令(这些命令可能通过别名/包装器由 zagi 处理),并询问用户希望:
<类型>[可选范围]: <主题>
[可选正文]
[可选脚注]
feat:新功能fix:错误修复docs:仅文档更改style:不影响代码含义的更改(空格、格式、缺少分号等)refactor:既不修复错误也不添加功能的代码更改perf:提高性能的代码更改test:添加缺失的测试或更正现有测试build:影响构建系统或外部依赖项的更改ci:对 CI 配置文件和脚本的更改chore:维护任务(更新构建任务、依赖项等;不涉及生产代码更改)revert:恢复先前的提交在类型/范围后使用 ! 来指示破坏性变更:
feat!: 添加新 APIfix(api)!: 更改响应格式BREAKING CHANGE: <描述>test:。pnpm ci、npm run ci、just ci)。git(可能是别名或包装器,如 zagi)构造明确的 shell 命令,例如:
git add path/to/file1 path/to/file2
GIT_AUTHOR_DATE="YYYY-MM-DD HH:MM:SS" \
GIT_COMMITTER_DATE="YYYY-MM-DD HH:MM:SS" \
git commit -m "feat: add feature"
如果用户请求"继续到 X"或"自动化直到 X":
在以下情况前停止并询问用户:
@ts-ignore、# type: ignore 等)时。any 类型或类似的类型逃逸时。reset --hard、checkout .、clean -f、push --force);优先选择更安全的替代方案并解释风险。简单的功能或行为更改:
feat: add user authentication
带范围的功能:
feat(api): add user endpoint
错误修复:
fix: resolve memory leak in cache
破坏性变更:
feat!: migrate to new API version
仅测试更改:
test: improve unit tests for auth service
重构(无行为更改):
refactor: extract validation logic into separate function
复杂更改(带正文):
feat(api): add pagination support
Implements cursor-based pagination for large datasets.
See docs/api/pagination.md for details.
详细指南,请参阅:
references/conventional-commits.md – 提交格式和示例references/ci-verification.md – CI 检查模式和验证references/co-authors.md – 处理 Co-Authored-By 尾注和 zagi 的共同作者剥离每周安装量
75
代码仓库
GitHub 星标数
7
首次出现
2026 年 1 月 20 日
安全审计
安装于
codex51
cursor49
claude-code43
gemini-cli41
opencode40
github-copilot39
Manage Git commits using conventional commit format with atomic commits and concise messages.
This skill is zagi-aware and is designed to work well with AI IDEs (Cursor, etc.)
zagi (a better git interface for agents).
git is aliased to zagi in the shell orzagi binary is available.git as if it may be zagi-compatible and avoid using exotic flags.git commands and let any git → zagi integration handle them.git when zagi is not available.git commands that will be run (which may be handled by zagi via alias/wrapper), and ask whether the user wants:
<type>[optional scope]: <subject>
[optional body]
[optional footer(s)]
feat: A new featurefix: A bug fixdocs: Documentation only changesstyle: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)refactor: A code change that neither fixes a bug nor adds a featureperf: A code change that improves performancetest: Adding missing tests or correcting existing testsbuild: Changes that affect the build system or external dependenciesci: Changes to CI configuration files and scriptsUse ! after the type/scope to indicate breaking changes:
feat!: add new APIfix(api)!: change response formatBREAKING CHANGE: <description>Implement atomic change : Code + tests together.
test: for test-only changes.Run CI checks : Verify types, tests, and linting pass before staging.
pnpm ci, npm run ci, just ci).Stage atomic changes : Group related files together (implementation + tests).
Suggest commit message : Generate a conventional commit message based on changes.
Generate commands :
Construct explicit shell commands using git (which may be an alias or wrapper such as zagi), for example:
If user requests "continue to X" or "automate until X":
Stop and ask user before:
@ts-ignore, # type: ignore, etc.).any type or similar type escapes.reset --hard, checkout ., clean -f, push --force); prefer safer alternatives and explain the risks.Simple feature or behaviour change:
feat: add user authentication
Feature with scope:
feat(api): add user endpoint
Bug fix:
fix: resolve memory leak in cache
Breaking change:
feat!: migrate to new API version
Test-only change:
test: improve unit tests for auth service
Refactor (no behavior change):
refactor: extract validation logic into separate function
Complex change (with body):
feat(api): add pagination support
Implements cursor-based pagination for large datasets.
See docs/api/pagination.md for details.
For detailed guidance, see:
references/conventional-commits.md – Commit format and examplesreferences/ci-verification.md – CI check patterns and verificationreferences/co-authors.md – Handling Co-Authored-By trailers and zagi co-author strippingWeekly Installs
75
Repository
GitHub Stars
7
First Seen
Jan 20, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
codex51
cursor49
claude-code43
gemini-cli41
opencode40
github-copilot39
React 组合模式指南:Vercel 组件架构最佳实践,提升代码可维护性
122,000 周安装
Datadog自动化监控:通过Rube MCP与Composio实现指标、日志、仪表板管理
69 周安装
Intercom自动化指南:通过Rube MCP与Composio实现客户支持对话管理
69 周安装
二进制初步分析指南:使用ReVa工具快速识别恶意软件与逆向工程
69 周安装
PrivateInvestigator 道德人员查找工具 | 公开数据调查、反向搜索与背景研究
69 周安装
TorchTitan:PyTorch原生分布式大语言模型预训练平台,支持4D并行与H100 GPU加速
69 周安装
screenshot 截图技能:跨平台桌面截图工具,支持macOS/Linux权限管理与多模式捕获
69 周安装
chorerevert: Revert a previous commitgit add path/to/file1 path/to/file2
GIT_AUTHOR_DATE="YYYY-MM-DD HH:MM:SS" \
GIT_COMMITTER_DATE="YYYY-MM-DD HH:MM:SS" \
git commit -m "feat: add feature"
Always print these commands to the user in order.
Ask for execution preference :
Commit :
Next commit :