kestrel-mcp-audit-diff

Analyze git diffs to generate structured code-review briefings.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Srain021/KesTREL --skill kestrel-mcp-audit-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kestrel-mcp-audit-diff
Source: https://github.com/Srain021/KesTREL/tree/main/.cursor/skills-cursor/kestrel-mcp/audit/diff
Command: npx skills add https://github.com/Srain021/KesTREL --skill kestrel-mcp-audit-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review git diffs and pending changes to identify security, correctness, and quality gaps during code review, reducing manual review time.

Core Features & Use Cases

  • Analyze diff scope and summarize touched files, added/removed lines, and commit messages.
  • Cross-check changes against RFCs and governance policies to ensure alignment.
  • Generate actionable findings and suggested improvements for reviewers.

Quick Start

Provide the latest diff to this skill to receive a structured PR-review summary.

Frequently Asked Questions about kestrel-mcp-audit-diff

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

FAQPage Schema
How do I automate git diff code review for security and correctness?

Automate git diff code review by providing pending changes to generate a structured briefing focused on security, correctness, and test coverage. It analyzes touched files and commit messages to produce actionable findings for reviewers.

Can I check pending code changes against RFCs and governance policies?

Check pending code changes against RFCs by cross-referencing diffs with available governance policies. This ensures alignment during code review and enforces modern coding standards alongside safety checks.

How do I review uncommitted changes for test coverage gaps?

Review uncommitted changes for test coverage by analyzing the diff scope to identify gaps and generate actionable findings. The process enforces safety checks and outputs clear improvements for reviewers.

What is the best way to generate a structured PR review summary from a diff?

Generate a structured PR review summary from a diff by summarizing touched files, added lines, and commit messages. The output includes actionable findings and suggested improvements referencing RFCs when available.

Does this code review approach work with any codebase?

This code review approach works with any codebase by analyzing uncommitted or committed changes. It enforces modern coding standards and clear actionable review outputs regardless of the underlying programming language.