skills.rest
openshift-eng
openshift-engCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Suggest Reviewers Helper

Analyze git blame data to propose reviewers for changed lines.

112|305|Updated Oct 10, 2025
Search Tags:#git#developer tools#code review#collaboration#blame analysis
One-click install
npx skills add https://github.com/openshift-eng/ai-helpers --skill suggest-reviewers-helper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Suggest Reviewers Helper
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/git/skills/suggest-reviewers
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill suggest-reviewers-helper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the guesswork in finding the right code reviewers by automatically analyzing git blame data to identify the original authors of modified code.

Core Features & Use Cases

  • Git Blame Analysis: Automatically identifies which developers authored the specific lines being changed in a pull request.
  • Bot Filtering: Automatically excludes common bot accounts from reviewer suggestions.
  • Use Case: Imagine you're working on a feature branch with changes across multiple files. Use this Skill to automatically find the developers who originally wrote the code you're modifying, ensuring the most knowledgeable reviewers see your changes.

Quick Start

Use the suggest-reviewers helper to analyze git blame for the current uncommitted changes in the repository.

Frequently Asked Questions about Suggest Reviewers Helper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify the right code reviewers for a pull request using git blame?▼

Git blame analysis identifies which developers originally authored the specific lines being changed in your pull request. This Skill automatically maps those authors to propose the most knowledgeable reviewers, filtering out bot accounts and the current user to surface relevant candidates.

Can I use git blame analysis to suggest reviewers across multiple files?▼

Yes. This Skill accepts multiple --file inputs to analyze blame data across several files in a single run, comparing changes against your base branch and outputting per-author metrics in JSON format to help you identify reviewers across your entire changeset.

What are the prerequisites to run blame-based reviewer suggestions?▼

You need Python 3.6 or later and Git installed and accessible in your PATH. The Skill analyzes uncommitted and committed changes in your repository, so ensure your working directory is a valid git repository before running the analysis.

How does this approach differ from manually selecting code reviewers?▼

Blame-driven reviewer suggestion eliminates guesswork by automatically surfacing developers who wrote the original code you're modifying, ensuring knowledgeable reviewers see changes without manual lookup or institutional memory.

Does this Skill filter out automated accounts from reviewer suggestions?▼

Yes. The Skill automatically excludes common bot accounts and the current user from reviewer recommendations, outputting only genuine developer candidates in the JSON results.

Related Skills

Explore More Software Engineering Skills→
carlosamesarcarlosamesar
1

git-archaeology

Extract blame and commit metadata for specific lines in Git repositories.

Community
Intermediate
semicolon-devteamsemicolon-devteam

assign-task

Assign GitHub issues to assignees, manage workload points, and send Slack notifications.

Official
Intermediate
edwifiguyedwifiguy
1

git-workflow

Enforce best practices for commits, branches, merges, and pull requests.

Community
Intermediate
castrojocastrojo
2

codeowners

Create and update .github/CODEOWNERS files mapping paths to GitHub teams or users.

Community
Intermediate