Apply commit message style: conventional commits format (type: subject), imperative mood, <50 char subject, explain why in body. Use when writing commits, reviewing commit messages, or discussing git history.
Generate clear, concise commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or formatting git history.
Create a new git branch from main/master with a maximum of 17 characters. Prompts for branch name or infers from context.
Reorganizes commits and working changes into optimal structure. Use when: user wants to squash commits, reorganize history, or clean up commits.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Fetch GitHub issues, PRs, repo contents, and code using the gh CLI. Use when the user shares GitHub URLs (issues, PRs, repos, source files) or asks about GitHub content. The gh CLI provides complete content that web fetching often misses due to JavaScript rendering.
Use when user wants to create new autonomy branch with dedicated worktree for parallel agent workflows
Verify GF(3) skill conservation on pull requests. Ensures every contribution
Activates when user needs help with git operations including branching, rebasing, merging, cherry-picking, stashing, and resolving conflicts. Triggers on "help me rebase", "fix merge conflict", "create branch", "git history", "undo commit", "squash commits", or any git workflow questions.
Commit message standards following Conventional Commits specification. Use this when writing commit messages for the Hey Jarvis project.
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
Clone and track external repos. Use when user shares GitHub URL to study or develop, or says "search repos", "find repo", "where is [project]". Actions - learn (clone for study), incubate (clone for development), search/find (search repos), list (show tracked).
Advanced dependency scenarios in uv projects: Git dependencies, path dependencies, editable installs, dependency groups, extras, constraints, and custom indexes. Use when user mentions git+https dependencies, local path dependencies, editable installs, dependency groups, or private package indexes.
Pre-merge security validation detecting secrets, user-specific paths, insecure SSH configurations, and security-weakening flags
Generate a pull request using GitHub CLI following the project's pull request template.
Validate documentation requirements before creating a PR. Checks for scratchpad entries, CHANGELOG updates, tests, and plan files based on change type. Use before creating pull requests to ensure all documentation gates are satisfied.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Read-only access to external repositories for cross-repo context. Use when you need to reference code, patterns, or documentation from other local repositories.
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
