This project uses Claude Code skills (.claude/skills/) to standardize
recurring workflows. Skills are invoked with /skill-name in a Claude Code
session. This page is for contributors who want to understand what each
skill does without reading individual SKILL.md files.
For ctx plugin skills (/ctx-status, /ctx-history, etc.), see the
ctx skills documentation.
| Skill | Purpose | Invoke |
|---|---|---|
| absorb | Merge changes from a parallel directory | /absorb |
| audit | Detect and fix code-level drift | /audit |
| backup | Backup context to SMB share | /backup |
| brainstorm | Design before implementation | /brainstorm |
| check-links | Audit docs for dead links | /check-links |
| qa | Run QA checks before committing | /qa |
| release | Full release process | /release |
| release-notes | Generate release notes | /release-notes |
| sanitize-permissions | Audit granted permissions | /sanitize-permissions |
| skill-creator | Create or improve a skill | /skill-creator |
| update-docs | Sync docs with code changes | /update-docs |
| verify | Verify before claiming completion | /verify |
Extracts a diff between two copies of the same project and applies it as a
patch. The companion to /ctx-worktree: worktree splits work apart, absorb
merges it back. Useful when git push/pull isn't practical (USB copies,
disconnected machines, worktrees without a shared remote).
- Use when: merging from a parallel worktree or separate checkout
- Skip when: directories share a git remote (just
git pull)
Detects code-level drift: predicate naming, magic strings, hardcoded values, missing godoc. Follows the 3:1 consolidation ratio; run after every ~3 rapid implementation sessions.
- Use when: after YOLO sprints, before releases
- Skip when: mid-feature with intentionally incomplete code
Structured design thinking before implementation. Transforms vague ideas into validated designs with trade-offs, constraints, and a recommended approach.
- Use when: before new features, architectural changes, behavior modifications
- Skip when: bug fixes with clear solutions, well-defined requirements
Crawls documentation files for broken internal and external links.
- Use when: before releases, after restructuring docs
- Skip when: editing a single doc (just eyeball it)
Runs go vet, go test, build checks, and convention compliance before
committing. Catches issues locally instead of in CI.
- Use when: after writing Go code, before committing
- Skip when: only docs/markdown/config changed (no Go code touched)
Runs the full release pipeline: version bump, build, release notes, tag, push.
- Use when: cutting a tagged release
- Skip when: only generating release notes (use
/release-notesinstead)
Generates dist/RELEASE_NOTES.md from commits since the last tag.
Required by hack/release.sh before it can run.
- Use when: preparing a release, drafting changelog
- Skip when: writing a blog post (use
/ctx-blog-changeloginstead)
Audits settings.local.json for overly broad or dangerous permission grants
that accumulated during development.
- Use when: periodically, after granting many permissions in a session
- Skip when: actively debugging permission issues
Guides creation of new skills or evaluation of existing ones. Ensures skills follow the project's structure and quality standards.
- Use when: building a new skill, improving an existing one
- Skip when: one-off instructions that don't warrant a reusable skill
Checks that documentation stays consistent with code after changes. Covers CLI flags, file formats, defaults, and conventions.
- Use when: after modifying user-facing behavior, before committing
- Skip when: purely internal changes with no docs impact
Runs the actual commands (build, test, lint) to verify a claim before reporting it. Prevents "tests pass" without having run the tests.
- Use when: before claiming anything is done, working, or fixed
- Skip when: documentation-only changes with no testable outcome