Goal Issues And Release
Clear the open issue backlog and then cut a release, in one autonomous run: use the...
Install
npx skills add dyoshikawa/rulesync --skill goal-issues-and-release -g -a claude-code -y- Repository
- dyoshikawa/rulesync1.6k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,527 tokens
- Runs scripts
- No, instructions only
What it does
Clear the open issue backlog and then cut a release, in one autonomous run: use the `batch-all-issues` skill to resolve every open issue, then the `goal-release` skill to draft, merge, and see the release through publication. Never asks the user anything, every decision is made autonomously, and blockers are reported at the end instead of interrupting the run.
Goal Issues and Release
Run the project's two long-form maintenance skills back to back, without stopping to ask the user anything:
- the
batch-all-issuesskill, resolve every open issue, one at a time. - the
goal-releaseskill, cut the release that ships whatever those fixes merged.
Use this skill when the user wants the whole backlog cleared and a release cut in a single unattended run.
Autonomy Rule
Do not ask the user any questions during this run. Both underlying skills have steps that say to stop and ask the user; in this skill those steps become "decide autonomously, record the decision, and keep going", with the single exception of the safety stops listed under Safety Boundaries below, which remain hard stops.
Concretely, when an underlying step would ask the user:
- Choose the option that moves the work forward, implement the fix, merge the PR, close the issue, cut the release, unless it hits one of the Safety Boundaries below. Leaving an issue open or a PR unmerged is reserved for those boundaries, not for design questions that merely lack a maintainer's sign-off.
- For an open design point, pick the option that best fits the project's existing conventions and the tool's documented behavior, and state the choice in the PR body so it can be revisited later.
- Record every such decision, so it lands in the final report.
Acting decisively never means guessing at facts, bypassing CI, or widening a fix beyond the issue it resolves.
Safety Boundaries
The autonomy rule above relaxes convenience questions only. The conditions below keep exactly the triggers the underlying skills give them; the only difference is that instead of asking, the run halts that step and reports at the end. No decision made here may override them:
