stayfixed
@stayfixed Organization
Public Skills
memory-sweep
by stayfixed
Sweep the working-memory store — inventory by size, verify anchors resolve, rewrite notes to rule-plus-pointer, check the link graph and the paths notes name. Use when memory notes have accumulated history or the index has grown.
file-bug
by stayfixed
File a bug-ledger entry that a later reader can act on — the reproduction, the evidence and its boundary, and a suggested fix marked as the hypothesis it is. Use when a defect is found and is not being fixed in the same change.
adopt
by stayfixed
Take a repository that has run init to its gates enforced — assess it, asking before any command of its own runs, brainstorm and write the adoption's design and plan, and hand over the promotion. Use right after init, in a later session that carries an adoption on, or in a clone of a repository that has adopted stayfixed.
review-plan-three-lenses
by stayfixed
Review an implementation plan through three lenses before it is executed — whether each task's premise holds in the tree, whether each assertion can fail, and whether each trust ruling names its anchor. Use on any plan longer than one task, before the first dispatch.
uninstall
by stayfixed
Remove stayfixed's scaffold from a repository, leaving hand-edited files in place and listed. Use when the user asks to uninstall or remove stayfixed from a project.
close-bug
by stayfixed
Close a bug ledger entry correctly — frontmatter, Fix section, index regeneration, and the checks that catch a half-closed entry. Use when marking a ledger entry fixed, partial, or rejected.
retro-to-guard
by stayfixed
Turn a retrospective into guards — for each finding, a test with its mutation, a check, a refusal or a standing rule, and a routing table that gives every finding a terminal state. Use after a retrospective is written and before its lessons are forgotten.
doctor
by stayfixed
Diagnose a stayfixed installation — hooks, memory store, budgets, overrides and trust. Use when a hook is silent, memory does not arrive, a gate fails unexpectedly, or the user asks whether stayfixed is set up correctly.
upgrade
by stayfixed
Upgrade the stayfixed scaffold in a repository after a plugin update, keeping every hand edit. Use when the user asks to upgrade, update or refresh stayfixed's files, or after the plugin version changed.
setup
by stayfixed
Configure the machine for stayfixed — the preset, the personal parameters, and the per-repository git hook. Use on a new computer, when the user asks to install stayfixed's defaults, or when a commit-message hook is wanted.
run-correctness-audit
by stayfixed
Audit a repository for correctness defects by component — candidates first, then each one executed to a verdict, then the survivors filed. Use before a release, after a large merge, or when the owner asks whether the code does what its documents say.
attribute-failure
by stayfixed
Attribute one failing test or command to the change or to the environment with three runs and one verdict, never a guess. Use when a test fails and it is not obvious whether the change caused it.
sweep-defect-class
by stayfixed
Turn one defect into its class and close every instance — enumerate the shape across the tree, prove which tests take the branch, fix or file each hit, and declare the mutation that reddens each fix. Use after a bug fix whose shape could recur.
init
by stayfixed
Take a repository onto stayfixed — show what it detected, ask the questions a person may answer, write the scaffold, and offer the adoption that assesses it. Use when a project has no .stayfixed/manifest.json yet, or the user asks to initialise stayfixed in it.
attach
by stayfixed
Bind a repository to its private memory overlay and point the harness at its notes, or detach it. Use when a session reports "not attached", or the user asks to attach or detach the overlay.