code-gap-reviewer

Identify discrepancies between project specifications and code implementations.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/serguei9090/Agentic-Governance-Framework --skill code-gap-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-gap-reviewer
Source: https://github.com/serguei9090/Agentic-Governance-Framework/tree/main/MasterPrompts/.agents/skills/code-gap-reviewer
Command: npx skills add https://github.com/serguei9090/Agentic-Governance-Framework --skill code-gap-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Specialized auditing to identify discrepancies between project specifications (AGENTS.md, rules, docs/) and the actual codebase implementation. Use this for architectural audits and logic-gap discovery.

Core Features & Use Cases

  • Identify Source of Truth: Read relevant specifications (AGENTS.md, .agents/rules/System/Architecture.md, docs/).
  • Scan the Implementation: Inspect code to locate feature implementations and architecture patterns.
  • Perform the Gap Analysis: Detect missing logic, spec discrepancies, interface drift.
  • Document Findings: Update docs/track/codegapreview.md with issue, location, impact, remediation.

Quick Start

Run a gap audit to compare AGENTS.md and architectural docs against the codebase and document findings in docs/track/codegapreview.md.

Frequently Asked Questions about code-gap-reviewer

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

FAQPage Schema
How do I audit code gaps against project specifications and architecture docs?

To audit code gaps, compare project specifications like AGENTS.md and architectural docs against the actual codebase implementation to detect missing logic, spec discrepancies, and interface drift.

What is a code gap analysis and when do I need it?

A code gap analysis identifies discrepancies between project specifications and code implementations. You need it for architectural audits, onboarding to unfamiliar repos, and milestone reviews.

How do I document discrepancies between specs and code implementations?

Document code discrepancies by updating docs/track/codegapreview.md with the identified issue, location, impact, and recommended remediation steps for traceability.

Can I use this to find interface drift and missing logic in an unfamiliar repo?

Yes, onboarding to unfamiliar repos is a core use case. It inspects code to locate feature implementations and architecture patterns, detecting missing logic and interface drift.

What is the best way to ensure traceability to AGENTS.md and .agents/rules during a code audit?

Ensure traceability by reading source of truth files like AGENTS.md and .agents/rules, scanning the implementation, and documenting all findings in docs/track/codegapreview.md.