sanctum

Draft a slop-free Conventional Commit message for staged changes using the commit-messages skill with AI slop detection.

Create git tags from merged PRs or version arguments

Implement issues (GitHub/GitLab/Bitbucket) using progressive analyze-specify-plan-implement workflow

Command options, configuration, and best practices.

> **Navigation**: [← Main Workflow](../workflow-steps.md) | [Step 2: Triage →](2-triage.md)

> **Navigation**: [← Step 1: Analyze](1-analyze.md) | [Main Workflow](../workflow-steps.md) | [Step 3: Plan →](3-plan.md)

> **Navigation**: [← Step 2: Triage](2-triage.md) | [Main Workflow](../workflow-steps.md) | [Step 4: Fix →](4-fix.md)

> **Navigation**: [← Step 3: Plan](3-plan.md) | [Main Workflow](../workflow-steps.md) | [Step 5: Validate →](5-validate.md)

> **Navigation**: [← Step 4: Fix](4-fix.md) | [Main Workflow](../workflow-steps.md) | [Step 6: Complete →](6-complete.md)

> **Navigation**: [<- Step 5: Validate](5-validate.md) | [Main Workflow](../workflow-steps.md)

> **Navigation**: [<- Reconciliation](reconciliation.md) | [Step 6 Hub](../6-complete.md) | [Next: Thread Resolution ->](thread-resolution.md)

> **Navigation**: [<- Thread Resolution](thread-resolution.md) | [Step 6 Hub](../6-complete.md) | [Next: Summary ->](summary.md)

> **Navigation**: [<- Step 6 Hub](../6-complete.md) | [Next: Issue Creation ->](issue-creation.md)

> **Navigation**: [<- Issue Linkage](issue-linkage.md) | [Step 6 Hub](../6-complete.md) | [Next: Verification ->](verification.md)

> **Navigation**: [<- Issue Creation](issue-creation.md) | [Step 6 Hub](../6-complete.md) | [Next: Issue Linkage ->](issue-linkage.md)

> **Navigation**: [<- Summary](summary.md) | [Step 6 Hub](../6-complete.md) | [Main Workflow](../../workflow-steps.md)

Error handling, troubleshooting guide, and known issues.

Detailed step-by-step guide for fix-pr command execution.

Address PR/MR review feedback using progressive workflow (GitHub/GitLab)

Retrospective analysis and improvement of workflow components with self-evolving patterns

Catch up on repository changes with structured analysis and actionable insights

Consolidate ephemeral LLM-generated markdown files into permanent documentation.

Comprehensive PR/MR review with scope validation and code analysis (GitHub/GitLab)

Command options, configuration, best practices, and integration details.

Review classification system and scope mode details.

Detailed workflow phases, examples, and advanced features.

Complete PR preparation - updates documentation, dogfooding, README, tests, then validates with code review

Batch-resolve all unresolved PR/MR review threads via platform GraphQL API (GitHub/GitLab)

Update pre-commit hooks and CI/CD workflows based on recent project changes

Scan and update dependencies across all ecosystems with conflict detection

Update project documentation with consolidation, debloating, AI slop detection, capabilities sync, and accuracy verification.

Audit and sync plugin.json files with disk contents (commands, skills, agents, hooks)

After registration audit completes, automatically analyze improvement opportunities.

Run meta-evaluation on evaluation-related skills to validate recursive quality.

Check the memory-palace research queue for items needing evaluation.

Update tests using TDD/BDD principles with quality validation

Generate or update tutorials with VHS and Playwright recordings

Bump project versions using the git-workspace-review and version-updates skills.

Conventional commit message generation agent specializing in change classification, semantic versioning awareness, and consistent commit formatting. Use when drafting commit messages for staged changes, classifying change types, formatting breaking change footers, linking issues in commits. Do not use when analyzing repository state - use git-workspace-agent first. preparing full PR - use pr-agent. ⚠️ PRE-INVOCATION CHECK (parent must verify BEFORE calling this agent): - Single file with <20 lines? → Parent commits directly - Obvious type (typo, version bump, deps)? → Parent uses `fix(scope): message` - Can write message in <30 seconds? → Parent commits directly ONLY invoke this agent for: multi-file changes, ambiguous classification, breaking changes, or complex scope decisions. Generates complete conventional commit messages ready for use.

Dependency analysis and update agent for multi-ecosystem repositories. Scans pyproject.toml, Cargo.toml, package.json, and go.mod files. Use when checking for outdated dependencies, updating package versions, resolving version conflicts, preparing dependency update PRs. Do not use when installing new dependencies - use ecosystem-specific tools. debugging dependency issues - analyze manually first. Provides conflict detection, compatible version resolution, and code migration assistance for breaking changes.

Git workspace analysis agent specializing in repository state assessment, file structure mapping, and change tracking. Use when preflight checks before commits/PRs/reviews, understanding repository state, mapping codebase structure, analyzing staged and unstaged changes. Do not use when generating commit messages - use commit-agent. preparing PR descriptions - use pr-agent. ⚠️ PRE-INVOCATION CHECK (parent must verify BEFORE calling this agent): - "What branch?" → Parent runs `git branch --show-current` - "Show status" → Parent runs `git status` - "What changed?" → Parent runs `git diff --stat` - Any single git command → Parent runs it directly ONLY invoke this agent for: full workspace analysis, theme extraction, structure mapping, or multi-aspect preflight validation. Provides read-only analysis and state assessment for downstream workflows.

Pull request preparation agent specializing in quality gate execution, change summarization, and PR template completion. Use when preparing detailed PR descriptions, running pre-PR quality gates, documenting testing evidence, completing PR checklists. Do not use when just writing commit messages - use commit-agent. only analyzing workspace state - use git-workspace-agent. ⚠️ PRE-INVOCATION CHECK (parent must verify BEFORE calling this agent): - Single commit, <50 lines? → Parent runs `gh pr create --fill` - Obvious fix (typo, bump)? → Parent creates PR directly - No quality gates needed? → Parent uses `gh pr create --title "..." --body "..."` ONLY invoke this agent for: multi-commit PRs, breaking changes, quality gate execution, or complex change narratives. Executes quality gates and produces complete PR descriptions ready for submission.

Analyzes a recreated workflow slice and produces multiple improvement approaches with explicit trade-offs and confidence scores. Use when generating improvement options after workflow recreation, comparing trade-offs between approaches, scoring improvement confidence. Do not use when recreating workflow first - use workflow-recreate-agent. already have chosen approach - use workflow-improvement-planner-agent. Second step in /fix-workflow: generates 3-5 improvement approaches with trade-offs.

Implements agreed workflow improvements across skills, agents, commands, and hooks while keeping diffs focused, consistent, and test-backed. Use when executing improvement plan from planner agent, applying focused plugin asset edits, adding tests for behavior changes. Do not use when still planning - use workflow-improvement-planner-agent. validating changes - use workflow-improvement-validator-agent. Fourth step in /fix-workflow: applies focused changes following sanctum conventions.

Converges on the best workflow improvement approach, defines acceptance criteria, and produces an execution plan coordinating implementer and validator subagents. Use when selecting best approach from analysis, defining acceptance criteria, creating bounded execution plan, coordinating implementer/validator agents. Do not use when still analyzing approaches - use workflow-improvement-analysis-agent. ready to implement - use workflow-improvement-implementer-agent. Third step in /fix-workflow: produces bounded plan with acceptance criteria.

Validates that workflow improvements make a substantive difference by running targeted tests/validators and replaying a minimal workflow reproduction. Use when confirming improvements after implementation, running targeted validation, comparing before/after metrics, documenting evidence. Do not use when still implementing - use workflow-improvement-implementer-agent. issues found - route back to implementer agent. Final step in /fix-workflow: confirms substantive improvement with evidence.

Recreates the most recent command/session slice workflow from context, identifies involved skills/agents/commands/hooks, and surfaces inefficiencies. Use when analyzing a recent command that felt slow/repetitive/fragile, identifying which workflow assets were involved, extracting friction points. Do not use when directly improving workflows - use workflow-improvement-analysis-agent next. implementing changes - use workflow-improvement-implementer-agent. First step in /fix-workflow: reconstructs what happened before analysis.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

5 hooks across 4 events