anorth/agent-skills

prepare-commit

Checklist before making a commit: check and update the originating ticket or task, run tests and lint, and commit if asked.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/anorth/agent-skills --skill prepare-commit

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Prepare commit

Checklist before a commit. Proceed to commit if explicitly asked, else stop when the checklist is done and wait.

Workflow

Run in this order.

1. Originating artifacts

Re-read the ticket, task, or any other artifacts that were the starting point for this conversation, and the code diff.

  • Is everything in the ticket addressed?
  • Summarise the ticket and what changes have been made.
  • Note whether this change completes the ticket.

Where we have made decisions that contradict the ticket, keep the original brief and append a note saying what changed and why.

If there is no written starting point, say so and continue.

2. Tests and lint

Prefer the project's documented lint and test entrypoints. Run lint, then tests. Fail-stop on either — do not present the work as ready to commit if either fails. If asked to commit and a check fails, don't commit; report.

Don't run a full production build unless the project documents that as the check to use.

3. Commit (only if asked)

  • Stage only the files that belong to this change.

If the working tree has unrelated changes, stop and ask before committing; don't sweep them in.

  • Follow the project's commit and branch conventions.
  • Write a message saying what changed and why, and reference the ticket, if there is one.
  • Don't bypass hooks (--no-verify). If a hook fails or changes files, stop and report.
  • Afterwards, check git status, and report the branch status and anything left uncommitted.
  • If you committed on main itself and the change completes the ticket, close the ticket.

Otherwise leave it open.

Hard rules

  • Do not amend, rewrite history, or push unless explicitly asked.
同じリポジトリから

関連する Skills

すべての Skills
anorth
コミュニティ

build-ticket

Builds one ready ticket through to a reviewed result with evidence, without stopping for routine decisions: checks it's ready, builds to its design, runs its done checks, reflects, reviews, and reports. Use when the user asks to build, implement, or pick up a ticket.

1時間の導入数
2
GitHub Stars
1
更新日
11月3日
anorth
コミュニティ

deep-review

Deep, themed review of a diff: the review-diff flow and its standard lenses, plus one cheap reviewer subagent per theme, using distinctive preferences distilled from Alex North's public GitHub reviews (naming, API shape, errors, tests, coupling, and related themes). Needs the review-diff skill. Use when the user asks for a deep review, themed review, or anorth-style review.

1時間の導入数
2
GitHub Stars
1
更新日
11月3日
anorth
コミュニティ

domain-modeling

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

1時間の導入数
2
GitHub Stars
1
更新日
11月3日
anorth
コミュニティ

grilling

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

1時間の導入数
2
GitHub Stars
1
更新日
11月3日