scm-utils

Plugin scm-utils from marketplace ai-mktpl in nsheaps/ai-mktpl. Commands read from the repo's manifest — today.

Skills (19)

• auth-user

  Identify the authenticated user for GitHub CLI (gh) and Git

• automated-code-review

  Perform a comprehensive automated code review using granular review skills. Orchestrates review-pr-contents, review-commits, review-commit-messages, review-diff, review-code, validate-review, and post-review as building blocks. Use this for new review workflows — scm-utils:code-review is maintained

• code-review

  Code review a pull request. Triggers on "review this PR", "code review", "review PR #123", "request a review", "review bot", "code review CI", "automated PR review", "claude review workflow", or when the user wants to add automated code review to a repository.

• commit

  Intelligently commit outstanding changes in logical, focused commits. Use this when you want to commit code using git.

• fix-review-findings

  Fix issues found during a review. Use when asked to "fix review findings", "address review comments", "fix the issues found", or after a review identifies problems that need code changes.

• git-worktree

  Best practices for Git worktrees, especially branch naming when checking out PRs. Use this when creating worktrees, checking out PRs into worktrees, or working in multi-agent/multi-worktree setups.

• post-review

  Post or update a review on GitHub. Use when asked to "post the review", "submit review", "leave a review on the PR", "update the review", or when you have review findings ready to publish on a pull request.

• pr-review-workflow

  Quick-reference index for the full PR review workflow. Redirects to automated-code-review for the full orchestration. Use when asked to "do a full review", "review everything", or "comprehensive review".

• pr-workflow

  Full PR lifecycle management: creating, iterating on feedback, and merging. Triggers on: "review my PR", "iterate on PR feedback", "address review comments", "PR workflow", "get this merged", "respond to reviewer", "handle PR feedback".

• rebase

  Rebase a feature branch onto its base branch to produce a linear commit history. Use when the user asks to "rebase my branch", "rebase onto main", "rebase PR #123", "linearize history", "rebase and force push", or when a clean linear history is preferred over merge commits.

• request-a-review

  Best practices and procedures for creating and maintaining high-quality pull requests. Covers PR creation, body formatting, title conventions, lifecycle management, and requesting reviews. Counterpart to review-code, respond-to-review, and other review-receiving skills. Triggers on: "create a PR", "

• respond-to-review

  Respond to review comments on a PR. Use when asked to "respond to review", "reply to reviewer", "address review comments", "respond to PR feedback", or when crafting responses to reviewer questions and suggestions.

• review-code

  Review code quality, patterns, and bugs. Use when asked to "review the code", "check code quality", "look for bugs", "review implementation", or when evaluating code correctness, security, and maintainability independent of the diff or PR context.

• review-commit-messages

  Review commit message quality. Use when asked to "review commit messages", "check commit message format", "are commit messages good", or when evaluating whether commit messages are conventional, descriptive, and useful.

• review-commits

  Review commit structure and organization. Use when asked to "review commits", "check commit history", "are commits atomic", "review commit structure", or when evaluating whether commits are logically grouped and ordered.

• review-diff

  Review the diff against the base branch. Use when asked to "review the diff", "check what changed", "review changes against main", "is this PR complete", or when evaluating whether a diff is scoped correctly and complete.

• review-pr-contents

  Review PR title, body, labels, and metadata. Use when asked to "review the PR", "check PR description", "is the PR body good", "review PR metadata", or when evaluating whether a PR is well-presented for reviewers.

• update-branch

  This skill should be used when the user asks to "update the PR", "update PR #123", "sync the branch", "update the branch", "merge base into feature branch", "pull and push changes", "get latest from main", "synchronize with upstream", or when working in CI and needing to synchronize a feature branch

• validate-review

  Validate that review findings are accurate and actionable. Use when asked to "validate review", "check if review findings are correct", "verify review accuracy", or when confirming that a review's claims match actual code state.

Slash commands (1)

• /scm-utils:fix-pr

  Fix or update the PR description for the current branch to follow best practices

Hooks (1)

• PostToolUse

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/post-git-push-reminder.sh

Similar plugins