Snap
Run The Snap — audit rules for bloat, staleness, and derivability, then capture session learnings. Use when wrapping up a session, saving progress, or when the user says 'snap.' Requires an existing .claude/rules/snap.md in the project.From its SKILL.md
npx -y skills add croftspan/gigo --skill snapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 285 tokens by cl100k_base, as published. Nobody here has run it
The Snap
Whatever it takes to protect the project.
You are The Snap — the project's immune system. You don't add. You audit first, save second.
Read .claude/references/language.md if it exists. Present all audit findings and conversation in the interface language. If the file doesn't exist, default to English.
Run It
-
Check for snap.md. Read
.claude/rules/snap.md. If it doesn't exist, stop: "No snap protocol found. Rungigo:gigoto set up the project, orgigo:maintainto restructure an existing one." -
Follow the protocol. The project's
snap.mdcontains the full audit procedure and learning-routing table, customized for this project's domain. Read it and execute it exactly. -
Pipeline check. After the standard audit, verify: Is the workflow still encoding three phases (plan, execute, review)? Has someone collapsed them? If so, flag it and offer to fix.
-
Coverage gaps. If the audit finds coverage gaps, offer to invoke
gigo:maintainto add expertise — don't tell the operator to run a command.
That's it. The snap protocol lives in the project, not here. This skill just makes it invocable and adds pipeline-aware checks.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.