skills.rest
Milovan-Crowley
Milovan-CrowleyCOMMUNITY
Explore all skills by this author →
GitHub

audit

Review code changes against project requirements before merging.

Updated Aug 23, 2026
Search Tags:#audit#best-practices#quality-assurance#code-review#pull-request#production-readiness
One-click install
npx skills add https://github.com/Milovan-Crowley/Consilium --skill audit-milovan-crowley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/Milovan-Crowley/Consilium/tree/main/generated/claude/skills/audit
Command: npx skills add https://github.com/Milovan-Crowley/Consilium --skill audit-milovan-crowley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that code changes conform to project requirements by surfacing issues before they reach production.

Core Features & Use Cases

  • Structured review templates and checklists to assess code quality, architecture, and testing.
  • Quick feedback loops that guide developers to fix critical issues early in the task lifecycle.
  • Applicable to task-driven development, major feature implementations, and pre-merge code reviews.

Quick Start

Review the latest changes against the project requirements and safety guidelines and deliver a structured report.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I perform a pre-merge code review to check production readiness?▼

Pre-merge code review checks production readiness by applying structured templates to assess code quality, architecture, and testing. This surfaces issues in code changes before they reach the main branch.

What is the best way to catch code quality issues before merging to main?▼

The best way to catch code quality issues is using structured review checklists that verify changes against project requirements. This creates quick feedback loops to guide developers in fixing critical issues early.

When do I need to run a structured code review in a task-driven development workflow?▼

You need structured code review in task-driven development after completing tasks, implementing major features, or right before merging to main branches. It ensures code changes satisfy production readiness criteria.

How does a pull request review template improve quality assurance?▼

A pull request review template improves quality assurance by providing structured checklists for qualitative checks. It verifies code changes conform to project requirements and safety guidelines before merging.

Can I use structured review checklists for major feature implementations?▼

Yes, structured review checklists apply to major feature implementations. They verify that new code changes conform to project requirements by surfacing architecture and testing issues before production deployment.

What are the limitations of manual code review for production readiness?▼

Manual code review limitations include slower feedback loops compared to structured reviews. Without review planning templates, manual checks may miss qualitative checks and critical production readiness criteria before merging.

Related Skills

Explore More Software Engineering Skills→
mattolsonmattolson
195

plan-milestone

Decompose project milestones into sequenced tasks with dependencies and risks.

Community
Intermediate
wsxwj123wsxwj123
7

requesting-code-review

Automate structured code reviews before merging to main branches.

Community
Intermediate
zizzfizzixzizzfizzix

code-review

Automate code review for architectural, security, and quality compliance.

Community
Advanced
saschadudkin-sketchsaschadudkin-sketch

code-review

Automate code review for rezidence4/DomHub repository changes.

Community
Advanced