Loading...
Loading...
Found 147 Skills
Update a GitHub issue with new title, body, labels, or assignees. Use when the user wants to edit an issue, change labels, or update issue details.
Fetch, preview, merge, and test GitHub PRs locally. Great for trying upstream PRs before they're merged.
Verify that a pull request fully implements the requirements described in its linked GitHub issue. Use when asked to "verify PR implementation", "check PR coverage", "does PR implement the issue", "verify PR against issue", "is PR complete", or "PR completeness check". Extracts the linked issue from the PR body or GitHub linked issues, analyzes the diff against issue requirements, and reports either missing items or confirms 100% coverage.
Auto-updates GitHub issues with commit progress. Use when starting work on an issue, tracking progress during implementation, or completing work with a PR.
Review PR comments, discuss improvements, and reply with resolution status
Use when the user asks to create a pull request. Build a complete PR using best-practice structure with rich details on changes, verification, QA evidence, risks, and rollout notes. Include issue linkage and clear testing commands/results in the PR body.
Load all open issues from GitHub and save them as markdown files
Fix review comments on current PR
Fetch review comments from an existing GitHub pull request and implement the requested changes. Use when user says 'address PR feedback', 'implement review comments', 'fix the PR review', 'reviewer asked for changes', or 'my PR got comments'. Do NOT use for initial PR creation (use create-pr) or for writing your own review (use review-diff).
Create GitHub Issues with a parent-child structure (sub-issues). Generate parent and child issues using `gh issue create`, and link the parent-child relationship with `gh api .../sub_issues`. It is recommended to use Conventional Commits format (`feat:`, `fix:`, etc.) for titles. Used for scenarios like "Create an Issue" and "Break down tasks into Issues".
Create GitHub PRs in Conventional Commits format. OWASP Top 10 security checks are mandatory; PR creation will be aborted if issues are found. Generate a PR body including Summary/Test plan/Design. Trigger with commands like "Create PR", "Pull Request", or `gh pr create`. Use the contribute-skill for contributions to upstream repositories.
Batch archive project items with Status set to Done using `gh project item-archive`. Also checks and guides on the configuration status of the Auto-archive built-in workflow (manual execution is basically unnecessary if enabled). Used for scenarios like "archive completed items", "organize Done items", "clean up the board", etc.