code-audit-hardcore

Audit code changes and expand review scope to related files.

30|2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/hawkyre/hawk-skills --skill code-audit-hardcore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-audit-hardcore
Source: https://github.com/hawkyre/hawk-skills/tree/main/skills/code-audit-hardcore
Command: npx skills add https://github.com/hawkyre/hawk-skills --skill code-audit-hardcore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggressive cleanup audits scoped to user changes expand the review to tangibly relevant surrounding code and always improve when possible.

Core Features & Use Cases

  • Expanded review scope: includes setup, wiring, and sibling files that influence the core changes.
  • Posture hardcore: prompts auditors to aggressively improve, not just flag issues.
  • Plan-based routing: big fixes are routed through plans; small fixes are applied inline.
  • Consistent output: provides a structured audit report detailing scope, applied fixes, and checks.

Quick Start

Provide your diff to trigger an aggressive cleanup pass over tangibly related code.

Frequently Asked Questions about code-audit-hardcore

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

FAQPage Schema
How do I audit surrounding code impacted by my diff for cleanup and refactoring?

Aggressive code audits expand review scope from your diff to tangibly related setup, wiring, and sibling files, applying concrete cleanup improvements to all affected surrounding code.

What is an aggressive code audit posture for improving code quality?

A hardcore audit posture means aggressively improving code rather than just flagging issues, directly applying small fixes inline while routing big changes through structured plans.

How do I triage code audit fixes by size during a refactor?

Audit-triage classifies identified cleanup fixes as small or big, routing large changes through plans and applying small fixes inline to ensure safe refactoring.

Can I review setup and wiring files alongside my core code changes?

Expanded review scope includes setup, wiring, and neighboring sibling files that influence your core changes, ensuring the full context of your diff is audited.

What does a structured code audit report include after a cleanup pass?

The formal output template summarizes the expanded review scope, applied inline fixes, routed plans, and checks performed during the aggressive code audit.