Loading...
Loading...
Found 224 Skills
Explain what Fusion PM MCP is and guide setup of the hosted HTTP+OAuth server for its GitHub project-management retrieval tools. USE FOR: setting up or troubleshooting Fusion PM MCP, understanding its issue/PR/milestone tools, filing a setup bug. DO NOT USE FOR: implementing changes to the fusion-pm-mcp service itself, GitHub issue authoring/triage workflows, or general Fusion Framework/docs/EDS retrieval — use `fusion-mcp` for that.
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.
This skill monitors PR CI checks by polling GitHub status until completion or timeout. Use when the user requests to check CI status, wait for CI to pass, monitor PR checks, or verify build status. Applicable for queries like "check my CI", "wait for CI to pass", "is my PR green", or "monitor CI checks".
Create GitHub pull requests. Use when user asks to "create a pull request", "open a PR", "/create-pr", or requests creating pull requests.
Guides technical evaluation of code review feedback before implementation. Use when receiving PR comments, review suggestions, GitHub feedback, or when asked to address reviewer feedback. Emphasizes verification and reasoned pushback over blind agreement.
Go back through the previous year of work and create a Notion doc that groups relevant links into projects that can then be documented as SRED projects.
Issue Planning and Automation prompt that generates comprehensive project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated tracking.
Review git diffs, staged changes, and GitHub PRs. Change-focused analysis across seven pillars (Security, Performance, Architecture, Error Handling, Testing, Maintainability, Paranoia) with numeric scoring 1-10. Supports GitHub PR review, staged changes, and arbitrary diffs. Use when: reviewing a PR, reviewing staged changes, reviewing a diff, pre-commit review. Triggers: review PR, review my changes, review the diff, review staged, review-pr, check my changes.
Plan a new feature from concept to approved implementation plan. Activates Product Council for strategic evaluation, then Feature Council for technical planning. Produces a documented decision and scoped task breakdown. Use when starting any new feature work.
Reviews PR comments from GitHub (Copilot, reviewers), evaluates against actual code, replies with reasoning, and resolves threads. Triggers on "review pr comments", "address pr feedback", "fix pr comments", or "review copilot suggestions".
Git / GitHub guidelines