simiancraft/simiancraft-skills / skills/burn-down-github-issues
burn-down-github-issues
UnverifiedRun an unattended burndown of a GitHub issue backlog as cards on a per-operator GitHub Projects board whose lanes are an explicit state machine: appraise and size the inbox, carve what is over the ceiling, fix the ready ones in parallel git worktrees, prove each fix on a draft pull request, have an isolated second-engine reviewer judge it, land one branch at a time with freshness checks, and dead-letter per phase whatever a machine cannot finish. Use when the task is "work the backlog unattended", "triage and fix recent issues", "run the issue loop", "burn down issues", or "where is issue N on the board". Requires a per-repository burn-down-github-issues.config.ts at the target repo's root (the loop refuses to start without it), the prove-work-on-github skill, the codex and claude CLIs for the default seats, and a gh token with the project scope for the board. Skip for one-off fixes to a known issue you are already working interactively, and for backlogs whose issues are mostly product decisions rather than code.
callbacks/README.md
View on GitHub# Size callbacks the loop ships
`on-size-over-ceiling` is a template. On every start the loop renders it into the adopting
repository's callbacks directory (`callbacksDir`, by default `<worktreeRoot>/appraisal-callbacks`)
as `on-size-over-<maxPoints>`, substituting the repository root, the knife's directory, and the
ceiling, so the appraiser hands every issue it sizes over the ceiling to `carve-github-issue`
without knowing the knife exists. The ladder and both callback forms are documented in
`../../appraise-github-issues/references/callbacks.md`.
The rendered file's second line is an ownership marker (`# rendered by burn-down-github-issues;
edits are overwritten`). Only files carrying it are ever removed (a rendering for an earlier
ceiling) or overwritten; a file at the rendered name without the marker is the adopter's, is
refused with a log line, and is left alone. The rendering happens in `lib/place-callbacks.ts`,
which is tested against a temporary directory.
The knife runs with the seats the loop chose (`--carver`, `--carve-confirmer`, or the config's),
passed through the environment as `LOOP_CARVER` and `LOOP_CARVE_CONFIRMER`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |