pro-workflow

Create a well-crafted commit after running pro-workflow quality checks.

Build a feature using Research > Plan > Implement phases

Diagnose pro-workflow setup and Claude Code configuration

Generate a structured handoff document that another Claude session (or your future self) can consume immediately to continue where you left off.

Surface patterns from your pro-workflow learnings and session history.

Capture a lesson from this session into permanent memory.

Learn Claude Code best practices and capture lessons into persistent memory.

Display all learnings stored in the pro-workflow database.

Set up parallel Claude Code sessions using git worktrees.

Automatically find and surface relevant learnings from your pro-workflow database before you start working. Like muscle memory for your coding sessions.

Search the pro-workflow learnings database using full-text search (BM25).

End your Claude Code session with intention.

Specialized debugging agent. Use when facing hard bugs, test failures, or runtime errors that need systematic investigation.

Multi-phase development agent. Research > Plan > Implement with validation gates. Use PROACTIVELY when building features that touch >5 files or require architecture decisions.

Break down complex tasks into implementation plans before writing code. Use when task touches >5 files, requires architecture decisions, or has unclear requirements.

Code review specialist that checks for logic errors, security issues, and quality problems. Use before committing, for PR reviews, or after major changes.

Confidence-gated exploration that assesses readiness before implementation. Scores 0-100 across five dimensions and gives GO/HOLD verdict.

Optimize token usage and context management. Use when sessions feel slow, context is degraded, or you're running out of budget.

Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, and strips defensive code. Use when cleaning up code, simplifying, removing boilerplate, or before committing.

Show session analytics, learning patterns, correction trends, heatmaps, and productivity metrics. Computes stats from project memory and session history. Use when asking for stats, statistics, progress, how am I doing, coding history, or dashboard.

Capture a correction or lesson as a persistent learning rule with category, mistake, and correction. Stores, categorises, and retrieves rules for future sessions. Use after mistakes or when the user says "remember this", "don't forget", "note this", or "learn from this".

Wire Commands, Agents, and Skills together for complex features. Use when building features that need research, planning, and implementation phases.

Run quality gates, review staged changes for issues, and create a well-crafted conventional commit. Use when saying "commit", "git commit", "save my changes", or ready to commit after making changes.

Create and manage git worktrees for parallel coding sessions with zero dead time. Use when blocked on tests, builds, wanting to work on multiple branches, context switching, or exploring multiple approaches simultaneously.

Complete AI coding workflow system. Orchestration patterns, 18 hook events, 5 agents, cross-agent support, reference guides, and searchable learnings. Works with Claude Code, Cursor, and 32+ agents.

Surface past learnings relevant to the current task before starting work. Searches correction history, recalls past mistakes, and applies prior patterns. Use when starting a task, saying "what do I know about", "previous mistakes", "lessons learned", or "remind me about".

Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".

End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session.

17 hooks across 12 events