skills.rest
workinprogress-ai
workinprogress-aiOFFICIAL
Explore all skills by this author →
GitHub

devenv-code-review

Analyze GitHub PR or local git diffs and generate structured code review feedback.

Updated Jul 4, 2024
Search Tags:#automation#git#static analysis#code review#pull request#software quality
One-click install
npx skills add https://github.com/workinprogress-ai/devenv --skill devenv-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devenv-code-review
Source: https://github.com/workinprogress-ai/devenv/tree/main/copilot/skills/devenv-code-review
Command: npx skills add https://github.com/workinprogress-ai/devenv --skill devenv-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill removes the ambiguity and manual effort from code reviews by providing consistent, structured, and actionable feedback on pull requests or local branches.

Core Features & Use Cases

  • Automated Diff Analysis: Automatically fetches and analyzes code changes from PRs or local git refs.
  • Structured Findings: Categorizes feedback into Blockers, Concerns, Nits, and Praise using a standardized hotspot format.
  • Context-Aware Reporting: Identifies missing tests, surfaces TODOs/FIXMEs, and highlights potential risks without reviewing unchanged code.
  • Use Case: Use this skill to perform a pre-PR self-check on your current branch to catch bugs and design issues before submitting your code for human review.

Quick Start

Invoke the devenv-code-review skill to analyze the changes in your current branch against the default repository branch.

Frequently Asked Questions about devenv-code-review

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

FAQPage Schema
How do I automate code review feedback for a GitHub pull request?▼

Automated code review feedback for a GitHub pull request is generated by analyzing diffs fetched via the GitHub CLI, categorizing findings into blockers, concerns, nits, and praise to provide structured, actionable reports.

Can I run a static analysis pre-check on my local git branch before submitting a PR?▼

Yes, you can run a pre-PR self-check on your local git branch by generating a diff against the default repository branch, which surfaces missing test coverage and technical debt like TODOs before human review.

What is the best way to identify missing test coverage and TODOs in my git diff?▼

The best way to identify missing test coverage and TODOs in a git diff is to use context-aware reporting that analyzes code changes and surfaces technical debt without reviewing unchanged code.

Do I need to install the GitHub CLI to analyze pull request diffs?▼

Yes, you need to install the GitHub CLI to retrieve pull request data for automated diff analysis, while local git is used for generating diffs from local branches.

How does hotspot-formatted reporting improve software quality during code reviews?▼

Hotspot-formatted reporting improves software quality by standardizing code review feedback into structured categories like blockers and concerns, removing ambiguity and manual effort from the assessment process.

Related Skills

Explore More Software Engineering Skills→
JonnyCBBJonnyCBB

pr-description

Generate structured PR descriptions from git diffs for GitHub flows.

Community
Advanced
CivicActionsCivicActions
2

triage

Assesses issue tickets and assigns status, priority, and tags per project contract.

Official
Intermediate
KrismithReddy12KrismithReddy12

health

Calculate a weighted 0-10 code quality score from linters and test runners.

Community
Advanced
samChang72samChang72
1

code-review

Automates code reviews to detect bugs, style violations, and performance issues in submissions via static analysis tools.

Community
Intermediate