사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
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
mainitself 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.

