gk-review

Audit source code against documentation and test suites for architectural drift.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/gkganesh12/gk-stack --skill gk-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gk-review
Source: https://github.com/gkganesh12/gk-stack/tree/main/skills-extra/gk-review
Command: npx skills add https://github.com/gkganesh12/gk-stack --skill gk-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents architectural drift and technical debt by enforcing a mandatory, evidence-based quality gate after every development phase, ensuring that code quality remains high and consistent throughout the project lifecycle.

Core Features & Use Cases

  • Architecture Drift Detection: Automatically compares current code against documented architectural decisions to identify violations.
  • Automated Quality Gates: Runs linting, testing, and security audits to block progression if P0-level issues are detected.
  • Use Case: Use this skill at the end of a development phase to audit the codebase, generate a structured review report, and ensure all P0 and P1 issues are addressed before proceeding to the next phase or deployment.

Quick Start

Run the gk-review skill to audit the codebase and verify that the current phase meets all quality and architectural standards.

Frequently Asked Questions about gk-review

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

FAQPage Schema
How do I detect architectural drift in my codebase against documented decisions?

Code quality audits and architectural drift analysis verify source code against project documentation and automated test suites. This process ensures strict adherence to SOLID principles, security standards, and architectural patterns, generating actionable remediation tasks to prevent technical debt.

How do I automate quality gates to block deployment when P0 security issues are found?

Automated quality gates run linting, testing, and security audits to block progression if P0-level issues are detected. This enforces a mandatory, evidence-based quality gate after every development phase, requiring integration with local test runners and static analysis tools to validate code integrity.

Do I need local test runners and static analysis tools to validate code integrity?

Yes, validating code integrity requires integration with local test runners and static analysis tools. This skill depends on these tools to perform rigorous code quality audits and verify that the current development phase meets all architectural and security standards before proceeding.

What is the best way to prevent technical debt during the software development lifecycle?

The best way to prevent technical debt is enforcing a mandatory, evidence-based quality gate after every development phase. This skill performs rigorous code quality audits and architectural drift analysis to ensure code quality remains high and consistent throughout the project lifecycle.

When should I run an evidence-based code quality audit in my development workflow?

You should run an evidence-based code quality audit at the end of a development phase. This ensures all P0 and P1 issues are addressed and the codebase meets quality and architectural standards before proceeding to the next phase or deployment.