pr-completion
Ensure PR checks pass and conflicts are resolved before completing tasks. Use after creating a PR, when marking tasks as done, or when completing work that resulted in a PR.
Discover content media git workflows skills, compare source repositories and read the instructions for each workflow.
Ensure PR checks pass and conflicts are resolved before completing tasks. Use after creating a PR, when marking tasks as done, or when completing work that resulted in a PR.
GitHub Actions workflow management specialist. Use for gh run commands, workflow monitoring, log analysis, re-running jobs, and CI/CD debugging.
Merge conflict resolution conventions. Use when resolving git merge conflicts, especially in dependency files and lock files.
Generate commit message, PR title, and PR body for a pull request. Use when the user wants to create a PR, generate PR content, prepare a pull request, or fill a PR template from code changes.
CI/CD pipeline design, GitHub Actions, and deployment automation. Auto-triggers when setting up pipelines, automating deployments, or configuring workflows.
Perform comprehensive code reviews with actionable feedback. Use when reviewing pull requests, checking code quality, analyzing changes, or when the user mentions "review", "PR", "pull request", "check code", "...
Perform comprehensive code reviews with actionable feedback. Use when reviewing pull requests, checking code quality, analyzing changes, or when the user mentions "review", "PR", "pull request", "check code", "...
Guide completion of development work by presenting merge/PR options. Use when "I'm done", "merge this", "create PR", "finish up", or when implementation is complete and tests pass.
This skill should be used when the user asks to "create worktree", "remove worktree", "work in worktree", "switch to worktree", "clean up worktree", mentions "repo--branch pattern", or during plan execution whe...
Set up the development environment, understand code conventions, and implement type-safe patterns. Use when starting development work, writing new components, or following project-specific coding guidelines.
Understand Conventional Commits, GitHub issue management, and Pull Request workflows. Apply best practices for collaborative development.
Conventions for GitHub repo locations, forks, and open source contribution boundaries.
Patterns for delegating tasks to Codex CLI (GPT 5.2) experts including bug analysis, code review, and plan revision via the mcp__codex__codex tool.
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD che...
Automated code review for pull requests using specialized review patterns. Analyzes code for quality, security, performance, and best practices. Use when reviewing code changes, PRs, or doing code audits.
Update AGENTS.md in CloudRadar with a fully automated GitHub flow. Use when the user asks to change AGENTS.md, mentions the meta issue
Create a pull request after code changes are complete and reviewed. Use proactively after self-review passes and documentation is updated.
PR review workflow after push. Use proactively immediately after creating a pull request to check CI status and Codex review results.
Protect against wrong-repo edits and enforce production parity assumptions.
Remove completed or abandoned worker worktrees and their branches. Use to clean up after workers finish their tasks.
Spawn a Claude worker to handle a GitHub issue. Fetches issue details, creates a feature branch, and works autonomously. Use when you want to delegate an issue to a worker.
Spawn a Claude worker to handle a GitHub issue. Fetches issue details, creates a feature branch, and works autonomously. Use when you want to delegate an issue to a worker.
List all active Claude workers and their git worktrees. Shows branch status, commits, and suggests next actions. Use to see what workers are running.
Guide git operations using a three-tier branching model (main → staging → feature). Use this skill when the user asks about git commands, branch strategy, PRs, rebasing, merging, deploying to production, hotfix...
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.