Preview and deliberately rebuild this repository's governance onto the current Singularity Flow model.
Install
npx skillscat add ashokraj2011/singularityflow/sflow-governance-rebuild Install via the SkillsCat registry.
Rebuild this repository's governance
Output contract: Let the CLI validate and mutate state; preserve its exact result, warnings, publication status, artifacts, and next actions. For suggested actions, pair Shell with the returned Copilot command; honor commandGuidance. If absent, say "Copilot: no verified equivalent"; never invent a slash command.
Boundary: no Story required; cwd=opened Git root or verified repositoryPath from singularity-flow workspace current --json; refuse if neither resolves; never search $HOME/parents.
A rebuild replaces every framework-owned workflow, template and agent with the
installed package, keeps every repository-owned definition byte-identical,
recompiles every workflow under the current rules, and archives every existing
Story. It never touches application code, tests or documents.
- Run
singularity-flow governance rebuild --dry-run --jsonfirst. - Show the complete plan:
plan, the configuration source and commit, everyreplacedfile with its old and new digest,removed,kept, every
workflow with its owner and status, every failing workflow's findings and
repair action, every Story with its branch tips, and every blocker. Do not
summarize away files, workflows or Stories. - If
blockersis not empty, stop: the plan cannot be confirmed. Relay each
blocker and its repair, then preview again after the contributor repairs it. - Otherwise ask the contributor whether to proceed. A failing repository
workflow listed ininactivestays byte-identical and unstartable until it
is repaired; the confirmation must name it with--accept-inactive. - Only after the contributor gives the exact plan digest, run the returned
nextcommand with--jsonand showcommit,receipt,archived,backupandinvariants. Tell them to push the branch for teammates. - To undo a rebuild, run
singularity-flow governance restore --plan <PLAN> --dry-run --json, show every file, and confirm only with their consent.
Never supply a confirmation yourself, infer consent from the original request,
edit a workflow to make it pass, commit, push, or delete a branch. If the CLI
refuses, relay its code and repair and stop.