Loading...
Loading...
Found 2,055 Skills
Create GitHub Issues from a github_backlog_input.json (the output of classify-github-issues) via the bundled create_github_issues.py script. Always shows a visual dry-run table first and only creates real issues after the user explicitly approves. Use this whenever there is a github_backlog_input.json or any file of items to file in GitHub, or when the user says "create these GitHub issues", "file the backlog", "push these to GitHub", or "create the issues". This is the step that actually writes to the repo, so prefer it over hand-rolling API calls. After creating, it writes github_backlog_result.json for github-writeback-tracking.
Use when the user wants to change a GitHub repository and open a PR from ANY terminal, even one where that repo is not checked out. Clones via ghq if absent, branches off the fresh default branch, forks automatically when there is no write access, and opens a PR. Invoke as /pr-anywhere <owner/repo> <change>.
Keeps an open GitHub PR moving to merge: detects the PR from the current branch, watches for merge conflicts, red CI (GitHub Actions, Buildkite, Vercel, Fly.io), inbound review comments, and merge readiness, fixes what is safe, and reports only state changes. Also runs one-shot: diagnose and fix CI, rebase and resolve conflicts, or triage and answer review comments. Use when asked to "babysit a PR", "watch this PR", "keep the PR green", "fix CI", "why is CI red", "resolve conflicts", "rebase onto main", "address the review comments", "reply to the reviewers", "is this PR ready to merge", or "what is blocking the merge". For opening or editing the PR use pr-creator; for reviewing the local diff use pr-reviewer; for applying a pr-reviewer report use tidy; for npm release PRs use autoship.
Manage GitHub Issues 2.0 relationships with gh CLI: parent issues, sub-issues, blocked-by, and blocking links.
Enforces a lean GitHub Actions Flutter CI where every gate maps to one named release-blocking contract — pinned runner + subosito/flutter-action@v2 toolchain, dart format --set-exit-if-changed, flutter analyze --fatal-infos, build_runner and drift schema freshness (git diff --exit-code), flutter test --test-randomize-ordering-seed random, static import/banned-string greps that catch what runtime can't, coverage-as-report-never-a-gate with the upward-lie fixed, verify-never-bless goldens (no --update-goldens in CI), and an honest statement of what CI cannot prove (audio, real fonts, on-device behaviour). Use when editing .github/workflows/*.yml, adding or removing a job or step, wiring a codegen/schema/format/analyze/coverage gate, writing a grep-based policy test or gate script under test/policy or tool/, pinning action versions, or claiming CI proves something it can't.
Codex 連接 GitHub CLI。說「連接 GitHub」時載入。
Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Documentation in llms.txt format, (3) GitHub repository analysis, (4) Documentation without direct llms.txt support, (5) Multiple documentation sources in parallel
Search GitHub code, repositories, issues, and PRs via MCP
Complete GitHub repository setup with production-grade standards including community health files, CI/CD workflows, issue templates, documentation site, badges, CODEOWNERS, and release management. Handles initialization, configuration, GitHub Pages deployment, and automated quality checks for professional open-source or enterprise projects.
Lifecycle manager for GitHub-based skills. Use this to batch scan your skills directory, check for updates on GitHub, and perform guided upgrades of your skill wrappers.
Securely authenticate with GitHub using stored credentials for API operations and git commands
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.