architecture-overview
Use when asked about harness9 architecture, module design, or how components interact — explains the system design
Use when the user invokes /commit or asks to commit changes, after a code review has been completed and the changes are confirmed ready to stage and commit to git.
$ npx -y skills add zhangshenao/harness9 --skill commit --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/commitContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when the user invokes /commit or asks to commit changes, after a code review has been completed and the changes are confirmed ready to stage and commit to git.
name: commit description: Use when the user invokes /commit or asks to commit changes, after a code review has been completed and the changes are confirmed ready to stage and commit to git.
在 Code Review 通过后,将有效的代码变更暂存并提交到本地 Git 仓库。
1. 确认本次对话中已执行过 `/cr`(Code Review) 2. 若 Review 报告存在 **Critical** 问题,**停止执行**,提示用户先修复 3. 若未执行过 `/cr`,先调用 `cr` skill 完成 Review,再继续
git status git diff --stat git diff --cached --stat
**不使用 `git add -A` 或 `git add .`**,逐文件或逐目录添加:
git add <具体文件或目录>
排除规则:
参考以下格式(优先遵循仓库现有风格,通过 `git log --oneline -10` 判断):
<type>: <简明描述>(50 字符以内) <可选正文:说明 why,不是 what>
常用 `type`:`feat` / `fix` / `docs` / `refactor` / `test` / `chore`
**禁止**在提交信息中添加任何 AI 工具相关的署名,例如 `Co-Authored-By: Claude` 或类似内容。
git commit -m "$(cat <<'EOF' <提交信息> EOF )"
git log --oneline -3 # 确认提交已记录 git status # 确认工作区干净
输出提交的 hash 与摘要,告知用户提交成功。
| 问题 | 处理 | |------|------| | pre-commit hook 失败 | 修复 hook 报告的问题,重新 `git add` 后创建**新** commit,不使用 `--amend` | | 暂存了不该提交的文件 | `git restore --staged <file>` 取消暂存,重新操作 | | 工作区已无变更 | 告知用户没有可提交的内容 |
Local-First · Lightweight · Complete · Production-Ready general-purpose Agent framework, written in Go.
Use when asked about harness9 architecture, module design, or how components interact — explains the system design
Feature auto-development — clarify requirements, generate spec, dispatch dev sub-agent to implement and merge into current branch
Use when the user invokes /cr, requests a code review, or before committing to verify correctness, security, and quality of new…
Use when debugging Go errors, test failures, or unexpected behavior — step-by-step diagnosis approach
Use when writing or reviewing Go code — explains harness9 project coding conventions and patterns
Use when the user invokes /pr or asks to push changes and open a pull request, after commits are ready to be pushed to a remote…