kazunori279
@kazunori279
Public Skills
issuelooper-merger
by kazunori279
"The merger of this repository's issue loop (issuelooper), for a session whose CC_ROLE is already merger: resolve one pull request that conflicts with main. Rebase in a worktree, resolve so both sides survive, re-sweep, run the review gate, push, and leave the merge to the supervisor. Hand back only when the rebase needs a decision about behavior. Do not load this to find out what your role is."
issuelooper-shared
by kazunori279
"Shared reference for this repository's issue loop (issuelooper): the roles (worker, merger, tester, monitor, aide), how the supervisor ccpool.py runs them, the label scheme and who may set what, the merge gates a pull request must pass, comment signing, and the limits every session works under. Read it first, then .issuelooper/project.md, then the skill for your CC_ROLE."
issuelooper-worker
by kazunori279
"The worker of this repository's issue loop (issuelooper), for a session whose CC_ROLE is already worker: one claimed issue from trace to pull request. Worktree from origin/main (or from the branch an earlier worker left), cause traced to a line, a failing pytest first (Fail-before), the fix, the sweep, the PR in the loop's format, stage:pr. Also covers updating a PR that came back, and releasing a claim. Do not load this to find out what your role is."
issuelooper-tester
by kazunori279
"The tester of this repository's issue loop (issuelooper), for a session whose CC_ROLE is already tester. Two units: the live check of one stage:live issue against the live environment, and the UX run, which walks the deployed app the way a person would (desktop and phone, every language the app offers, screenshots while work is in progress, scrolling, reload), reads every screenshot together against the spec as a harsh UX reviewer, and files at most five new findings; and, when the workers have nothing to do, the spec check, which tests the app against the spec one requirement at a time. Do not load this to find out what your role is."
issuelooper-monitor
by kazunori279
"The monitor of this repository's issue loop (issuelooper), for the session whose CC_ROLE is already monitor: the moderator of the whole backlog. Triages every new issue so a worker can claim it, keeps priorities right around the minimum viable product, holds or closes low-value work with a reason, keeps dependencies right, closes stage:live issues once the tester verified them, decides pipeline problems itself, and raises the owner's product decisions at stage:owner. Do not load this to find out what your role is."