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

lib/place-callbacks.ts

View on GitHub
/**
 * Renders the size callback the loop ships into the adopter's callbacks directory, so the
 * appraiser hands an issue sized over the ceiling to the knife without knowing the knife exists.
 *
 * The rendered file is `on-size-over-<maxPoints>`; its second line is an ownership marker, and
 * only files carrying the marker are ever removed or overwritten. A file at the rendered name
 * without the marker is the adopter's and is refused, logged, and left alone. Importable without
 * running the loop, so it is tested against a temporary directory.
 */

import { chmodSync, existsSync, lstatSync, mkdirSync, readdirSync, readFileSync, renameSync, rmSync, writeFileSync } from 'node:fs';
import { join } from 'node:path';

export const OWNERSHIP_MARKER = '# rendered by burn-down-github-issues; edits are overwritten';

export type PlacedCallbacks = { rendered: string | null; removed: string[]; refused: string | null };

/** Single-quoted for a bash script: a quote inside the value becomes '\'' . */
function shellQuote(value: string): string {
  return value.replaceAll("'", "'\\''");
}

function marked(path: string): boolean {
  try {
    if (!lstatSync(path).isFile()) return false;
    return readFileSync(path, 'utf8').split('\n')[1]?.trim() === OWNERSHIP_MARKER;
  } catch {
    return false;
  }
}

export function renderSizeCallback(template: string, vars: { repoRoot: string; carveDir: string; maxPoints: number }): string {
  return template
    .replaceAll('{{REPO_ROOT}}', shellQuote(vars.repoRoot))
    .replaceAll('{{CARVE_DIR}}', shellQuote(vars.carveDir))
    .replaceAll('{{MAX_POINTS}}', String(vars.maxPoints));
}

export function placeSizeCallbacks(
  dir: string,
  template: string,
  vars: { repoRoot: string; carveDir: string; maxPoints: number },
  log: (message: string) => void,
  dryRun: boolean,
): PlacedCallbacks {
  const result: PlacedCallbacks = { rendered: null, removed: [], refused: null };
  const name = `on-size-over-${vars.maxPoints}`;
  const target = join(dir, name);
  if (dryRun) {
    log(`DRY RUN  would render ${name} into ${dir}`);
    result.rendered = target;
    return result;
  }
  mkdirSync(dir, { recursive: true });
  // Any other rendering of ours (a previous ceiling) comes off first; the adopter's files stay.
  for (const file of readdirSync(dir)) {
    if (file === name || !/^on-size-over-\d+$/.test(file)) continue;
    const path = join(dir, file);
    if (!marked(path)) continue;
    rmSync(path);
    result.removed.push(path);
    log(`removed ${path}, rendered for an earlier ceiling`);
  }
  if (existsSync(target) && !marked(target)) {
    result.refused = target;
    log(`not overwriting ${target}: it is not the loop's rendering (no ownership marker on line 2)`);
    return result;
  }
  const body = renderSizeCallback(template, vars);
  const temp = join(dir, `.${name}.${process.pid}.tmp`);
  writeFileSync(temp, body);
  chmodSync(temp, 0o755);
  renameSync(temp, target);
  result.rendered = target;
  log(`rendered ${name} into ${dir}`);
  return result;
}
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