skills.rest
lossyrob
lossyrobCOMMUNITY
Explore all skills by this author →
𝕏@lossyrobGitHub

paw-review-gap

Identify correctness, safety, testing, and maintainability gaps in code changes and PRs.

39|6|Updated Oct 8, 2025
Search Tags:#quality-assurance#code-review#risk-analysis#pr-review#gap-analysis#must-should-could
One-click install
npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-review-gap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paw-review-gap
Source: https://github.com/lossyrob/phased-agent-workflow/tree/main/skills/paw-review-gap
Command: npx skills add https://github.com/lossyrob/phased-agent-workflow --skill paw-review-gap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams systematically uncover gaps in correctness, safety, testing, and maintainability within code changes, and to categorize findings by severity.

Core Features & Use Cases

  • Identify correctness issues (logic errors, edge cases, error handling)
  • Assess safety and security gaps (permissions, input validation)
  • Evaluate test coverage (qualitative and references to Phase artifacts)
  • Produce GapAnalysis.md artifacts with Must/Should/Could classifications
  • Facilitate cross-repo coordination checks when multiple PR reviews exist

Quick Start

Use the paw-review-gap skill to generate a GapAnalysis.md for your PR by providing the repository, PR identifier, and the paths to prerequisite artifacts. The skill will output a structured set of findings categorized as Must/Should/Could along with evidence and remediation suggestions.

Frequently Asked Questions about paw-review-gap

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

FAQPage Schema
How do I find gaps in correctness and safety during a code review?▼

Code review gap analysis identifies correctness and safety issues by examining PR artifacts and categorizing findings into Must, Should, and Could severity levels with file:line evidence and remediation guidance.

What is the best way to categorize code review findings by severity?▼

Categorizing code review findings by severity uses a Must/Should/Could classification system to prioritize remediation for correctness, safety, testing, and maintainability gaps found within code changes.

How do I generate a gap analysis report for a pull request?▼

To generate a gap analysis report for a pull request, provide the repository, PR identifier, and prerequisite artifact paths to produce a structured GapAnalysis.md with categorized findings and remediation suggestions.

Can I assess test coverage gaps qualitatively across multiple PR reviews?▼

Yes, qualitative test coverage gaps can be assessed across multiple PR reviews to facilitate cross-repo coordination checks and evaluate testing references within the generated GapAnalysis.md artifacts.

Does PR gap analysis work without external dependencies?▼

PR gap analysis works without external dependencies, systematically surfacing maintainability and input validation findings directly from standard review artifacts across your existing PR workflows.

Related Skills

Explore More Software Engineering Skills→
dazzajidazzaji
9

adherence-check

Validate artifacts against specifications and generate structured adherence reports.

Community
Advanced
Tnemo65Tnemo65

code-reviewer

Identify and fix code quality, security, and maintainability issues across codebases.

Community
Advanced
OWASPOWASP
141

mcp-server-review

Audits MCP server implementations for security risks across seven defined review areas.

Official
Intermediate
RangeyRoverRangeyRover
3

speckit.checker

Run static analysis across multiple languages and generate prioritized issue reports.

Community
Intermediate