issue-prerequisite
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
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.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification. Verifies .gitignore, runs project setup, confirms clean test baseline. Do NOT use for quick fixes or small changes - worktrees add overhead; use simple branch switching for trivial changes.
Manages Git config. Use for user/email, remotes. Triggers - setup, personalization.
Creates a GitHub pull request using gh CLI with proper formatting. Use when: user wants to create a PR, open a pull request, or submit changes for review.
Get GitHub repository information including stars, forks, issues, languages, and metadata. Use when the user asks for repository details, GitHub stats, or repo information.
Grizzly Gabe is the Fixer and Red Team specialist. Systematically resolves issues from reports. Hacker mindset - knows every exploit because he has used them. Thinks like an attacker to fix like a defender. Grizzled veteran who fixes with care. Invoke with "Gabe, fix these" or "Gabe, red team this".
Complete feature work and merge back to main branch. Use when user wants to finish a feature, close a feature, or merge feature branch. Switches to main, pulls latest changes, merges feature branch, and pushes to remote.
Maintain and update this Clash/Mihomo configuration repo (mihomo.yaml, mihomo.js, rules/*.list, *Merged.list, force_ttl_rules.txt). Use when editing proxy groups, rule providers, DNS/TTL rules, or regenerating merged lists in this project.
Prevents destructive Git operations by requiring backup and confirmation. Blocks git reset --hard, git push --force on main, git clean -fd. Requires backup before git checkout, git reset, git rebase. Activate on any destructive git command.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans
Handle squashing multiple commits and rebasing feature branches safely. Use when consolidating commits into a single commit, or rebasing feature branches onto updated development branches. Falls back from jj when not available.
Set up the agent-friendly git wrapper router (venv, PATH shims, config, verification). Use when installing or troubleshooting the router, git/gh shims, or CLI routing behavior for this project.
Guide for adding environment variables. Use when adding new env vars to ensure all 4 locations are updated (code, SST, workflow, GitHub secrets).