跳到正文
cccskills
免费在 GitHub 公开

validate-agent-work

Use when finishing any change to this repository, or when the user says "validate", "check my work", "run checks", or "verify changes". Also use automatically after adding a feature, fixing a bug, or editing Go, Python or documentation here.

中文简介正在准备中。当前显示原文说明。

kryptamine/herdr-auto-title星标 271(GitHub 271 + cccskills 0)

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md2.6 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Validate Agent Work

The rules live in AGENTS.md and CONTRIBUTING.md; this is the order to check them in before handing work back.

Steps

  1. See what changed — the branch against main, and whatever is not committed yet:

    git diff --name-only main...HEAD
    git status --short
    

    Stage nothing: every check below runs over the whole module, and the index is the user's to decide.

  2. Run the gate:

    make check
    

    fmt runs first and rewrites files, so re-read one before editing it again.

  3. Comment pass — the ## Comment pass in .claude/rules/comments.md, over the comments this change added or touched.

  4. Read the diff against the mandatory rules in AGENTS.md — the language, commit, type, script and comment rules, and the "Working here" list. The linter checks none of them. Two need a search rather than a read: a field, method or constant added without a reader in the same change, and a probe whose finding has not reached docs/architecture/herdr-socket-api.md, which is the record — AGENTS.md takes it only if it misleads the code in silence.

  5. Check nothing was left running:

    make ps
    
  6. Before opening a pull request, write its body with the pr skill and check it against .github/pull_request_template.md: every section filled, no HTML comment left, no attribution line.

  7. Fix and re-run — fix what a step found, then run that step again to confirm it. If a failure is not yours to fix, say so rather than working around it.

  8. Report — always say what happened:

    • Clean: a brief confirmation.

    • Found and fixed, one line each:

      Validation found and fixed 3 issues:
      - golangci-lint: unused parameter in resolver.qualify
      - Comments: dropped a caller note in app/reads.go
      - Type rule: removed PaneInfo.Cols, which nothing read
      
    • Still broken: what is wrong and why you could not fix it.

make check is the whole gate on this machine, but CI also builds and tests on the Go floor go.mod names and on macOS — see CONTRIBUTING's "Pull requests". The user should never be surprised by a failure that could have been caught here.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

pr

免费

Use when writing a pull request body, or before `gh pr create` or `gh pr edit --body`.

中文简介正在准备中。当前显示原文说明。

kryptamine/herdr-auto-title2712026年10月26日 更新

查看 kryptamine 的全部技能

报告此技能的问题