git-workflow

Run parallel analysis agents for comprehensive codebase health check

Context-aware PR review with ticket integration and multi-phase validation

Review code for bugs, security issues, and adherence to project standards. This agent SHOULD be used when reviewing code changes for quality, security, and standards compliance.

Creates clean, atomic git commits. Invoked through the git-commit skill with context: fork for delegation isolation. Do not invoke directly — use the git-commit skill instead.

Verify change completeness, find orphaned code, and detect development artifacts. This agent SHOULD be used after implementation to verify nothing was missed or left behind.

Comprehensive git branch cleanup and organization

Generate changelog using git-cliff, optionally bump version tag

Run hooks and create clean, logical commits <example> Context: User just finished implementing a feature across multiple files. user: "I've finished adding the authentication module" assistant: "Great! You have changes across several files." <commentary> User completed coding task with multiple modified files. Proactively trigger commit-craft to organize changes into clean atomic commits. </commentary> assistant: "I'll use the commit-craft agent to organize these changes into logical, atomic commits." </example> <example> Context: User explicitly requests commit creation. user: "create commits for these changes" assistant: "I'll analyze your changes and group them logically." <commentary> Explicit commit request. Agent will identify related changes and create well-structured commits. </commentary> assistant: "I'll use the commit-craft agent to create clean, atomic commits following conventional format." </example> <example> Context: User has uncommitted work and wants to commit. user: "let's commit all this" assistant: "Let me review what's changed first." <commentary> User wants to commit work. Agent analyzes changes and creates multiple atomic commits rather than one large commit. </commentary> assistant: "I'll use the commit-craft agent to organize these into logical commits." </example> <example> Context: Large refactoring with many file changes. user: "I've refactored the database layer, ready to commit" assistant: "That's a significant change set." <commentary> Large changeset after refactoring. Agent will split into reviewable chunks and group related changes. </commentary> assistant: "I'll use the commit-craft agent to split this into reviewable, atomic commits." </example>

Summarize the current state of the git repository

This skill should be used when the user asks to "make commits", "commit all changes", "create a branch", "name a branch", "organize commits", "conventional commits", "generate changelog", "release version", "bump version", or needs guidance on git workflow best practices including commit organization, branch naming, and conventional commit format.