agentleFS
optaveoptave/ops-codegraph-tool/.claude/skills/titan-reset/SKILL.md

titan-reset

Skill94 starsChanged 3 months agoApache-2.0View on GitHub

Clean up all Titan Paradigm artifacts and snapshots, restoring the codebase to pre-Titan state

  • Deletes or force-pushes
  • Commits and pushes

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Delete the grind baseline snapshot (if it exists):

    line 30
  2. Very specific:

    Delete all local titan working branches.

    line 69
  3. Distinctive:

    Delete from remote, reusing the names captured above (best-effort — failures are non-fatal):

    line 84
  4. Very specific:

    If $ARGUMENTS does NOT contain --keep-graph:

    line 96
  5. Very specific:

    If $ARGUMENTS contains --keep-graph, skip this step.

    line 104

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Titan RESET — Pipeline Cleanup

You are resetting the Titan Paradigm pipeline, removing all artifacts and restoring the codebase to its pre-Titan state.


Step 1 — Restore baseline snapshot (if available)

codegraph snapshot restore titan-baseline 2>/dev/null && echo "Baseline restored" || echo "No baseline snapshot found"

This restores the graph database to its pre-GAUNTLET state.


Step 2 — Delete all Titan snapshots

codegraph snapshot delete titan-baseline 2>/dev/null

Delete the grind baseline snapshot (if it exists):

codegraph snapshot delete titan-grind-baseline 2>/dev/null

Also delete any batch snapshots dynamically:

for name in $(codegraph snapshot list --json 2>/dev/null | node -e "let d='';process.stdin.on('data',c=>d+=c).on('end',()=>{try{JSON.parse(d).filter(s=>s.name.startsWith('titan-batch-')).forEach(s=>console.log(s.name))}catch(e){}})"); do
  codegraph snapshot delete "$name" 2>/dev/null
done

Step 3 — Remove all Titan artifacts

rm -rf .codegraph/titan/

This removes:

  • titan-state.json — session state
  • GLOBAL_ARCH.md — architecture document
  • gauntlet.ndjson — audit results
  • gauntlet-summary.json — aggregated results
  • sync.json — execution plan
  • gate-log.ndjson — gate audit trail
  • issues.ndjson — cross-phase issue tracker
  • close-summary.json — close phase summary
  • drift-report.json — staleness detection across phases
  • grind-targets.ndjson — grind phase adoption targets and outcomes
  • arch-snapshot.json — pre-forge architectural snapshot

Step 4 — Delete titan working branches

Delete all local titan working branches. These accumulate across runs and leave orphaned commits that never reach main. The actual PR content lives on focused PR branches created by /titan-close — the working branches are safe to remove.

Capture the branch names once, before any deletion — querying git branch --list again after the local delete would find nothing, silently turning the remote cleanup below into a no-op:

REFACTOR_BRANCHES=$(git branch --list 'refactor/titan-*' | sed 's/^[* ]*//')
DOCS_BRANCHES=$(git branch --list 'docs/titan-*' | sed 's/^[* ]*//')
echo "$REFACTOR_BRANCHES" | xargs -r -I{} git branch -D {} || true
echo "$DOCS_BRANCHES" | xargs -r -I{} git branch -D {} || true

Note: -I{} ensures each branch is deleted individually so a failure on one (e.g. the currently checked-out worktree branch, which git refuses to delete in-place) is skipped rather than aborting the entire pipeline. The current worktree branch is cleaned up when the worktree itself is torn down.

Delete from remote, reusing the names captured above (best-effort — failures are non-fatal):

echo "$REFACTOR_BRANCHES" | xargs -r git push origin --delete 2>/dev/null || true
echo "$DOCS_BRANCHES" | xargs -r git push origin --delete 2>/dev/null || true

Print how many branches were removed.


Step 5 — Rebuild graph (unless --keep-graph)

If $ARGUMENTS does NOT contain --keep-graph:

codegraph build

This ensures the graph reflects the current state of the codebase without any Titan-era corruption.

If $ARGUMENTS contains --keep-graph, skip this step.


Step 6 — Report

Titan pipeline reset complete.
  - Baseline snapshot: restored and deleted
  - Grind snapshot: deleted
  - Batch snapshots: deleted
  - Artifacts: removed (.codegraph/titan/)
  - Titan branches deleted: N local, N remote
  - Graph: rebuilt (clean state)

To start a fresh Titan pipeline, run /titan-recon

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.