Loading...
Loading...
Found 23 Skills
Guidelines for maintaining external Dart packages, covering versioning, publishing workflows, and pull request management. Use when updating Dart packages, preparing for a release, or managing collaborative changes in a repository.
Create pull request from completed feature branch using GitHub-native stacked PRs. Use when the user says 'create PR', 'submit for review', 'synthesize', or runs /synthesize. Validates branch readiness, creates PR with structured description, and manages merge queue. Do NOT use before review phase completes. Not for draft PRs.
Use when reviewing pull requests with comprehensive code analysis, incremental or full review options, and constructive feedback - provides thorough code reviews with severity ratings
Inspect, triage, approve, and merge GitHub Renovate pull requests with gh. When no repository is provided, use the default preset repository set, build a candidate execution plan, and execute only after explicit user confirmation. Use when the user asks to check, batch-handle, approve, or merge Renovate PRs.
Push commits and create/update pull request
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.
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.
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
Lead Software Engineer. Use this skill whenever the user mentions coding, debugging, refactoring, or implementation, even if they don't explicitly ask for an "engineer." Use it to translate technical blueprints into clean code.
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.
GitHub PR lifecycle: branch, commit, open, CI, merge.