github▌

Interactive design-plan review that scores design quality, identifies unresolved UX issues, and improves the plan before anyone ships UI.

Founder-mode review that asks what product is really being built, not just what feature was requested. Supports scope expansion, selective expansion, hold-scope, and scope-reduction modes.

Patterns for automating GitHub workflows with AI assistance, inspired by Gemini CLI and modern DevOps practices.

Production-ready GitHub Actions workflow patterns for testing, building, and deploying applications.

Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.

Systematically address GitHub PR review comments and issue feedback using the gh CLI. \n \n Fetches and inspects PR comments and review threads to understand feedback before applying fixes \n Guides categorization and planning of comments, with user confirmation checkpoints for prioritization \n Applies code changes and responds to comment threads as resolved using gh CLI commands \n Requires gh authentication; includes auth status verification as a prerequisite step \n

Reusable GitHub Actions patterns to build React Native apps for iOS simulators and Android emulators in the cloud, then publish artifacts retrievable via gh CLI or GitHub API.

Search GitHub code, repositories, issues, and pull requests with flexible filtering. \n \n Four search types: code, repositories, issues, and pull requests, each with full GitHub search syntax support \n Optional filtering by repository owner and name to narrow results to specific projects \n Requires GitHub personal access token configured in mcp_config.json for authentication \n Command-line interface with straightforward parameters for integration into agent workflows \n

Sanitize code for secrets and artifacts, then create and publish GitHub releases with version tags. \n \n Two-phase workflow: Phase 1 runs blocking checks (secrets scan with gitleaks, LICENSE/README validation, personal artifact removal) and stops on failures; Phase 2 creates version tags and publishes via gh CLI \n Requires gh CLI authenticated, gitleaks installed, and a Git repository with a remote configured \n Includes non-blocking checks for build success and dependency vulnerabilities, plu

Create GitHub Issues automatically from implementation plan phases. \n \n Analyzes implementation plan files to identify phases and generates one issue per phase \n Uses feature_request.yml or chore_request.yml templates, with fallback to default issue format \n Checks for existing issues before creation to avoid duplicates, and updates existing issues when needed \n Includes phase details, requirements, and context in issue descriptions with appropriate labels \n