Loading...
Loading...
Found 132 Skills
Use when reviewing code, pull requests, branches, diffs, or changed files for quality, correctness, security, performance, and style issues.
Use this skill when reviewing or managing BitBucket pull requests: inspect PR metadata and diffs, post inline comments, reply to comments, edit or resolve comment threads, create pull requests, update PR title or description, check PR activities, summarize PR changes, or cross-reference Jira issues. Trigger phrases include: review PR, review pull request, check PR, comment on PR, post PR feedback, create a PR, create a pull request, what changed in PR, look at PR, summarize PR, PR activities.
Perform thorough code reviews following Google's 5-step methodology. Use when reviewing pull requests, change lists, or any code changes to ensure quality, correctness, and maintainability.
Reviews code changes for correctness, maintainability, security, and adherence to project conventions. Use when reviewing PRs, auditing recent changes, or getting a second opinion on implementation quality.
GitHub CLI workflows for repositories, issues, pull requests, actions, releases, projects, and API calls. Use when creating PRs, reviewing code, triaging issues, triggering workflows, publishing releases, managing projects, verifying attestations, or querying the GitHub API. Use for gh cli, github automation, code review, release management.
Deploy approved features to production. Creates PRs, runs pre-deployment checks, and updates TASKS.md. Use after /document completes. Supports task IDs for easier invocation.
Sync local changes to GitHub in one command: detect state, branch, commit, push, create PR. Use when user wants to push work to GitHub, create a PR, or sync a feature branch. Use for "push my changes", "create a PR", "sync to GitHub", "open pull request", or "ship this". Do NOT use for reviewing PRs (use /pr-review), cleaning up after merge (use pr-cleanup), or CI checks (use ci).
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
Create pull requests using GitHub CLI with proper templates and formatting
Create GitHub Pull Request from specification using pull_request_template.md. Use when: spec needs to be converted to PR, spec is ready for review/merge, need to automate PR creation from specification file with template-based body and title.
Patterns and conventions for creating a good PR
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an