final-audit

Audit merged feature code changes for systemic security, logic, and consistency issues.

1|Updated May 11, 2026
One-click install
npx skills add https://github.com/skalanux/puntofiles --skill final-audit-skalanux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: final-audit
Source: https://github.com/skalanux/puntofiles/tree/main/dot_agents/skills/final-audit
Command: npx skills add https://github.com/skalanux/puntofiles --skill final-audit-skalanux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams prevent subtle, cross-module bugs and security gaps by performing a holistic review of everything produced for a feature, after implementation is complete and ready for final sign-off.

Core Features & Use Cases

  • Feature-scoped discovery: Reads the full parent PRD issue (including child issues) to confirm scope and acceptance criteria match the completed implementation.
  • Cross-cutting systemic review: Audits the full set of in-scope files for consistency, security, logic flaws, and best-practice issues that can’t be fully detected within a single PR.
  • Actionable, prioritized reporting: Produces a severity-grouped report with locations, categorized findings, and suggested fixes, then lets you choose what to address first.

Quick Start

Ask the AI to run a final audit by providing the parent PRD issue number and an exact list of files created or modified for the feature, then request the prioritized findings report for security, logic, consistency, and best practices.

Frequently Asked Questions about final-audit

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

FAQPage Schema
How do I perform a final code audit before a feature release?

To perform a final code audit, provide the parent PRD issue number and an exact list of modified files. The audit cross-checks the full implementation against PRD acceptance criteria to detect systemic security, logic, and consistency issues before release.

What is cross-cutting code review for completed features?

Cross-cutting code review analyzes the full set of in-scope files for a completed feature to detect security gaps, logic flaws, and consistency issues. This systemic review catches subtle, cross-module bugs that cannot be fully detected within a single pull request.

How do I verify PRD compliance across multiple merged pull requests?

Verify PRD compliance by ingesting the full parent PRD issue, including child issues, to confirm the scope and acceptance criteria match the completed implementation. This holistic review ensures all merged PRs align with the original feature requirements.

Can I check release readiness for security and best practices after all PRs are merged?

Yes, you can check release readiness by auditing the complete set of in-scope files for security vulnerabilities and best-practice issues. It produces a severity-grouped report with locations and suggested fixes, letting you choose what to address first.

What is the best way to prioritize systemic issues found during a feature review?

Prioritize systemic issues by using a severity-grouped report that includes specific locations, categorized findings, and suggested fixes. This allows you to review the prioritized findings for security, logic, and consistency, then choose what to address first.

Does a final feature audit work without a parent PRD issue number?

No, a final feature audit requires the full parent PRD issue number and an exact list of created or modified files. Ingesting the PRD with acceptance criteria is essential to confirm scope and build an accurate implementation mental model for the review.