pr-list
List pull requests from the repository. Use when the user wants to see open PRs, find PRs to review, check their own PRs, or browse PR history.
Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.
List pull requests from the repository. Use when the user wants to see open PRs, find PRs to review, check their own PRs, or browse PR history.
Create a new pull request. Use when the user wants to open a PR, submit code for review, create a draft PR, or push changes for merge.
View pull request details including title, status, branches, and description. Use when the user asks about a PR, wants PR context, mentions viewing/checking a pull request, or needs to understand what a PR is a...
Update an existing pull request. Use when the user wants to modify PR title, description, publish a draft, convert to draft, abandon, or reactivate a PR.
Create GitHub PRs with gh, fetch review comments, fix them commit-by-commit, and reply to each comment individually with correctly formatted bodies.
Analyze unstaged changes and suggest atomic commit groups with messages
Analyze recent changes and add test coverage for HEAD commit
This skill should be used when the user asks to "review code", "perform code review", "check code quality", "review PR", "provide code feedback", or needs guidance on code review best practices and standards in...
This skill should be used when the user asks to "create a worktree", "manage git worktrees", "work on multiple branches simultaneously", "isolate task work", "use bd worktree", or needs guidance on git worktree...
This skill should be used when the user asks to "check quality gates", "validate against standards", "read AGENTS.md", "enforce project patterns", "follow constitution.md", "validate code quality", or needs gui...
Quick PR creation reference
Create git commits with conventional commit messages
Provides a structured template for Pull Request descriptions. Use when creating PRs, triggered by requests like "create a PR", "make a pull request", or "open a PR".
Bootstrap development sessions with automated startup rituals - checks recommendations, git status, launches scout + planner agents in parallel.
Enforces conventional commit message and branch naming conventions with specific prefixes (feat, fix, docs, style, refactor, perf, test, chore). Use when creating git commits, suggesting branch names, reviewing...
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Stage, commit, and push git changes with conventional commit messages with intelligent security checks. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their...
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
Automates the complete release process for this Obsidian plugin. This skill should be used when the user requests to publish a new version, bump version numbers, sync versions across files, update changelog, bu...
Generate Conventional Commits git commit messages from the staged diff. Use this when the user asks to craft a commit message or when preparing a commit.
Retrieve code diff from a GitHub Pull Request via GitHub API. Use this as the first step in a code review pipeline when reviewing GitHub PRs.
Deep codebase context analysis like Greptile. Analyzes blast radius of changes, dependency graphs, and architectural consistency. Use when reviewing changes to core utilities, shared libraries, or database mode...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.