Skip to content

simiancraft/simiancraft-skills / skills/burn-down-github-issues

burn-down-github-issues

Unverified

Run 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.

FileKindSize
SKILL.mdskill md17.0 KB
board.tsscript6.5 KB
callbacks/README.mdmarkdown1.1 KB
callbacks/on-size-over-ceilingother843 B
card.tsscript4.3 KB
chart-machine.tsscript3.9 KB
claim-race.tsscript6.1 KB
export-machine.tsscript1.8 KB
lanes.tsscript5.2 KB
lib/admission.test.tsscript7.6 KB
lib/admission.tsscript5.5 KB
lib/board-writer.test.tsscript3.6 KB
lib/board-writer.tsscript11.8 KB
lib/carving-revisit.test.tsscript7.5 KB
lib/carving.tsscript26.9 KB
lib/floor/config.test.tsscript456 B
lib/floor/config.tsscript8.1 KB
lib/floor/floor.test.tsscript9.9 KB
lib/floor/floor.tsscript28.7 KB
lib/floor/incident.tsscript11.2 KB
lib/floor/ledger.tsscript5.6 KB
lib/floor/probe.tsscript3.6 KB
lib/lanes.tsscript4.4 KB
lib/machine.test.tsscript11.2 KB
lib/machine.tsscript52.4 KB
lib/place-callbacks.test.tsscript2.5 KB
lib/place-callbacks.tsscript3.0 KB
lib/preflight.test.tsscript4.5 KB
lib/preflight.tsscript1.2 KB
lib/pressure.test.tsscript56.9 KB
lib/refs.test.tsscript1010 B
lib/refs.tsscript1.9 KB
lib/run-scope.test.tsscript5.4 KB
lib/run-scope.tsscript1.2 KB
lib/scenarios.test.tsscript17.1 KB
lib/simulate.test.tsscript7.3 KB
lib/simulate.tsscript7.0 KB
lib/world-sweep.test.tsscript21.4 KB
loop.source.test.tsscript4.8 KB
loop.tsscript66.2 KB
prompts/diagnose.mdmarkdown2.1 KB
prompts/walk.mdmarkdown3.6 KB
references/adopting.mdmarkdown26.3 KB
references/architecture.mdmarkdown20.7 KB
references/floor.mdmarkdown14.6 KB
references/operating.mdmarkdown19.6 KB
references/state-machine.mdmarkdown31.1 KB
status.tsscript4.9 KB
watch.tsscript6.4 KB

export-machine.ts

View on GitHub
#!/usr/bin/env bun
/**
 * Print the burndown's state machine as an XState v5 `createMachine` call, for pasting into
 * https://stately.ai/viz or importing into a project that has xstate installed:
 *
 *   bun run <skill-dir>/export-machine.ts > burndown.machine.js
 *
 * The machine is `lib/machine.ts`; this only rewrites its absolute state paths into XState id
 * references (`#burndown.ticket.work.coding`) and gives each lane state a description the
 * visualizer shows on hover. Nothing here is read by the loop.
 */

import { MACHINE, type StateNode, type Transition } from './lib/machine.ts';

const ID = 'burndown';

function ref(target: string): string {
  return `#${ID}.${target}`;
}

function transition(t: Transition): Record<string, unknown> {
  const out: Record<string, unknown> = { target: ref(t.target) };
  if (t.guard) out.guard = t.guard;
  if (t.actions) out.actions = t.actions;
  return out;
}

function node(n: StateNode): Record<string, unknown> {
  const out: Record<string, unknown> = {};
  if (n.type === 'parallel' || n.type === 'history' || n.type === 'final') out.type = n.type;
  if (n.lane) out.description = `${n.lane.key} ${n.lane.name}: ${n.lane.description}`;
  if (n.entry) out.entry = n.entry;
  if (n.exit) out.exit = n.exit;
  if (n.initial) out.initial = n.initial;
  if (n.always) out.always = n.always.map(transition);
  if (n.on) {
    out.on = Object.fromEntries(
      Object.entries(n.on).map(([event, list]) => [event, Array.isArray(list) ? list.map(transition) : transition(list)]),
    );
  }
  if (n.states) out.states = Object.fromEntries(Object.entries(n.states).map(([name, child]) => [name, node(child)]));
  return out;
}

const machine = { id: ID, ...node(MACHINE) };
console.log(`import { createMachine } from 'xstate';\n\nexport const burndown = createMachine(${JSON.stringify(machine, null, 2)});`);
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall