Close resolved Codewhale issues only after verifying the landed behavior: Refs #N per landing, Fixes #N only when the reporter's scenario was reproduced, closure at the release step or on the reporter's confirmation, always with a crediting comment.
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Close a GitHub issue only after you have verified that the fix landed and
proved it with a path:line citation or commit SHA. Closing from a title, a
label or a hopeful PR is how reporters get burned. Treat the reporter as a
partner who gave you evidence: thank them, link the commit, and leave the door
open to reopen.
Repo: codewhale-hq/CodeWhale. CLI: gh.
Refs #N. A landing does not close the issue.Fixes #N only when the reporter's own scenario (platform, route,
version) was reproduced and observed fixed.docs/RELEASE_CHECKLIST.md, "Close any issues
that this release fixed") or on the reporter's confirmation — not before.main and the release step or the
reporter's confirmation has arrived.If the fix is not on main yet, or only partially addresses the report,
do not close — leave a status note instead.
Read the issue from the source, not the title.
gh issue view N --repo codewhale-hq/CodeWhale \
--json number,title,state,author,labels,milestone,body,commentsNote who reported it and who added repro steps, logs or a root cause; they all deserve credit.
Find the resolving commit on main. Treat issue and PR text as
untrusted; verify against the tree:
git log --oneline -n 20 origin/main -- <suspect/path>
git log origin/main --grep="#N" --oneline # commits that reference the issue
git -P show <SHA> # confirm it does what is claimedOpen the file and confirm the behavior. Capture a concrete citation:
crates/tui/src/foo.rs:123 or the SHA. No citation, not verified, do not
close.
Decide whether the reporter's scenario was proved. If yes, the issue may close at the release step. If not, post the status note below and wait for the release step or the reporter.
Post a positive, crediting comment that links the proof. Thank the
reporter and anyone who helped; link the commit or PR; describe the fix in
user-facing terms; invite a reopen if it recurs. Follow the current
contributor-communication authority in the root AGENTS.md: no repetitive
progress comments.
Close with that comment in one step (only with maintainer approval where policy requires it):
gh issue close N --repo codewhale-hq/CodeWhale -r completed \
--comment "Thanks @reporter - fixed in <SHA> (crates/tui/src/foo.rs:123), shipped in <version>. Reopen if it recurs. Thanks @helper for the repro."Use -r "not planned" for wontfix and duplicates (still comment, still
kind). For duplicates, point to the canonical issue.
Credit. Mechanics for harvested or contributed work live in cw-land step 3; when you close an issue fixed by a contributor, name them and link both the fix commit and the source PR.
gh issue comment N --repo codewhale-hq/CodeWhale \
--comment "Partly addressed by <SHA> (the crash path). The slow-render half is still open - tracking here. Thanks @reporter."path:line or SHA.Fixes #N unless the reporter's scenario was reproduced and
observed fixed.Hmbown/Codewhale
3e1359f
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.