Sanctum

Use this skill for PR preparation. Use when preparing PRs for submission, running quality gates, drafting PR descriptions and templates. Do not use when reviewing existing PRs - use pr-review instead. DO NOT use when: just generating commit messages - use commit-messages.

Uses subagents for parallel execution with code review gates between batches. Use when addressing issues systematically, multiple related issues need fixing, tasks can be parallelized across subagents, quality gates needed between task batches. Do not use when single simple fix - just implement directly. DO NOT use when: issue needs clarification - comment first to clarify scope.

Use this skill for scope-focused PR reviews. Use when reviewing PRs, validating against requirements, triaging findings to backlog, preventing overengineering. Do not use when preparing PRs - use pr-prep instead. DO NOT use when: deep code review - use pensive:unified-review.

Use this skill for general documentation updates with built-in quality gates. Use when updating documentation after code changes, enforcing writing guidelines, maintaining ADRs. Do not use when README-specific updates - use update-readme instead. DO NOT use when: complex multi-file consolidation - use doc-consolidation.

Run git-workspace-review first to understand which tests need updates. Use when updating existing tests, generating new tests for features, enhancing test quality, ensuring detailed coverage, pre-commit validation. Do not use when auditing test suites - use pensive:test-review. DO NOT use when: writing production code - focus on implementation first.

Provides structural context for downstream review and refactoring workflows. Use when before architecture reviews to understand file organization, exploring unfamiliar codebases to map structure, estimating scope for refactoring or migration. Do not use when general code exploration - use the Explore agent. DO NOT use when: searching for specific patterns - use Grep directly.

Run git-workspace-review first to capture repo context. Use when README requires structural refresh, adding features to documentation, aligning readme with exemplar standards, improving project presentation. Do not use when updating inline docs - use doc-updates. DO NOT use when: consolidating ephemeral reports - use doc-consolidation.

Generate conventional commit messages from staged changes with correct type/scope. Use when generating commit messages in conventional commits format. DO NOT use when: full PR preparation - use pr-prep instead.

Use this skill for version management and release preparation. Use when bumping project versions, updating changelogs, preparing releases, coordinating version changes across files. Do not use when just documentation updates - use doc-updates. DO NOT use when: full PR preparation - use pr-prep.

Orchestrate tutorial generation from VHS tapes and Playwright specs to dual-tone markdown with GIF recording. tutorial update, gif generation, tape recording, update tutorial, regenerate gifs, tutorial manifest Use when: regenerating tutorial GIFs, updating documentation demos, creating tutorials from tape files DO NOT use when: only updating text - use doc-updates.

Merges valuable content into permanent documentation, then deletes source files. Use when you have untracked *_REPORT.md or *_ANALYSIS.md files, git status shows markdown artifacts that shouldn't be committed, preparing PR and need to clean up working artifacts, preserving insights from code reviews. Do not use when files are already in docs/ or skills/ locations. DO NOT use when: files are intentionally temporary scratch notes. DO NOT use when: source files have no extractable value.

Manage Claude Code sessions with naming, checkpointing, and resume strategies. Use when organizing long-running work, creating debug checkpoints, managing PR reviews.

Use this skill as foundation for git workflows. Use when verifying workspace state before other git operations, checking staged changes, preflight checks before commits or PRs. Do not use when full commit workflow - use commit-messages instead. DO NOT use when: full PR preparation - use pr-prep.

Retrospective workflow evaluation and improvement of skills, agents, commands, and hooks. workflow improvement, retrospective, workflow efficiency Use when: workflow felt slow, confusing, or needs optimization DO NOT use when: simple one-off fixes - use fix-pr or do-issue instead.