plan-coding-guideline-audit

Plans structured audits of repository codebases against master coding guidelines.

Updated May 16, 2026
One-click install
npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill plan-coding-guideline-audit-alimtvnetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-coding-guideline-audit
Source: https://github.com/alimtvnetwork/img-pdf-v2/tree/main/.agents/skills/plan-coding-guideline-audit
Command: npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill plan-coding-guideline-audit-alimtvnetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually checking an entire codebase against coding guidelines is slow and inconsistent. This Skill plans a structured, phased audit of repository code against the master coding guidelines in 02-spec/02-coding-guidelines/, producing organized findings and remediation plans. ## Core Features & Use Cases - Guideline Coverage: Audits boolean naming conventions, control flow nesting depth, naming and type rules, error handling with Result containers, and code metrics like function and file length limits. - Fast Discovery Toolchain: Uses dedicated Python scripts for file inventory, cached grep, folder exploration, and codebase topology to avoid tool truncation limits. - Structured Output: Generates audit logs and phased remediation plans with subtask micro-batches in .ai-memory/plans/pending/. - Use Case: Before a major release, run a full audit of Go and TypeScript code to find boolean naming violations, deeply nested conditionals, and functions exceeding 15 lines, then get a phased fix plan. ## Quick Start Ask the agent to plan a coding guideline audit of the repository against the master coding guidelines.

Frequently Asked Questions about plan-coding-guideline-audit

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

FAQPage Schema
How do I audit a codebase against coding guidelines automatically?

Run this Skill to plan a structured audit covering boolean naming, control flow depth, naming conventions, error handling, and code metrics. It produces audit logs and phased remediation plans in .ai-memory/plans/pending/.

What coding rules does the guideline audit check?

It checks five areas: boolean conventions with is/has prefixes, maximum nesting depth of 1 with guard clauses, naming and type rules like PascalCase, Result container error handling with appfault types, and metrics like 15-line functions and 100-line files.

Which languages does the coding guideline audit support?

The audit targets Go and TypeScript codebases, as shown by the file scanner invocation with --lang go,ts. Rules reference Go-specific conventions like no underscores and appfault Result types.

Why use the Python discovery scripts instead of normal file search?

The Python scripts avoid 50-result tool truncation limits and eliminate multi-turn exploratory roundtrips. They provide fast cached grep under 15ms, sub-millisecond folder reading, and codebase topology summaries.

Where does the audit output remediation plans?

Audit logs and phased remediation plans are written to .ai-memory/plans/pending/ with subtask micro-batches, allowing incremental execution of fixes across the codebase.