Individual skill
issue-pr
Fixes one issue and lands it as a merged pull request — branch, implement, run the repo's own gate, open a PR that closes the issue, merge. Use when asked to fix, do, or ship a specific issue.
skills/issue-pr/SKILL.md
Source commit 83315e4f8206fad56f9791a8f7884eec5609296a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
Repository context
- Repository stars (not skill ratings)
- 14
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- dotfiles Repository topic
- hooks Repository topic
- agent-skills Repository topic
- claude-code-config Repository topic
- claude-skills Repository topic
- code-review Repository topic
- release-automation Repository topic
- subagents Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,159 bytesSKILL.mdcore · 6,159 bytesSKILL.mdcore · 6,159 bytesSKILL.mdcore · 6,159 bytesscripts/pr-cycle.shruns · 7,288 bytestests/pr-cycle.shruns · 1,991 bytes
Read excerpt
# Ship one issue
One issue in, one merged PR out. The mechanics — gate, push, open, merge — are a script, so
nothing reaches the remote without passing the gate. Everything else is judgment.
## 1. Read the issue before touching anything
Re-check its claims against `HEAD`. A filed issue describes a tree that has moved; fixing
what it says rather than what is there is how a PR ends up reverting someone's work.
`~/.claude/skills/issue-verify/scripts/issue-facts.sh <N>` prints the file and symbol rows
and the commits that have touched them since filing. If the finding is already fixed, say
so and close the issue — do not manufacture a change.