Repository Audit
Resolve the request
Determine the audit strategy, included and excluded scope, focus areas,
depth, and constraints.
Read repository-level audit specifications, agent definitions, architecture
documents, and instructions when present. Apply documented defaults and record
every inferred value in the resulting report.
Inspect systematically
- Read the repository overview, architecture, decisions, and applicable specifications.
- Review existing audits before recording new findings.
- Inspect automation, manifests, workflows, source, tests, and documentation relevant to scope.
- Run read-only diagnostics when they provide reproducible evidence.
- Record material files, tools, commands, or environments that were unavailable.
Maintain evidence integrity
- Label statements as observed, inferred, recommended, or unverified.
- Cite repository-relative paths, symbols, configuration keys, or command results precisely.
- Assign lower confidence when evidence is incomplete.
- Separate the observation, its significance, and the recommendation.
- Record strengths and effective practices, not only defects.
- Avoid repeating prior findings without checking their current state.
- Never present an unavailable or blocked check as completed.
Write the report
Follow the repository's audit specification and output conventions when they
exist.
Otherwise, create a uniquely named Markdown report under audits/. Never
overwrite an existing report.
During a normal audit, modify only the new audit report. Do not apply fixes,
update dependencies, reformat files, open issues, create commits, or alter
repository configuration unless the request explicitly expands the scope.
Validate
Confirm that the report documents:
- scope and exclusions
- evidence sources
- commands executed
- positive observations
- findings
- severity and confidence
- uncertainties
- blocked checks
- recommended follow-up work
- a prioritized backlog
When the audit cannot be completed, produce a truthful partial or blocked
report and identify the next evidence required.
1---2name: repository-audit3description: Perform an evidence-based, non-destructive repository audit and write a structured report. Use for holistic or focused reviews of architecture, code quality, testing, security, CI/CD, dependencies, documentation, developer experience, maintainability, accessibility, performance, or repository hygiene.4---56# Repository Audit78## Resolve the request910Determine the audit strategy, included and excluded scope, focus areas,11depth, and constraints.1213Read repository-level audit specifications, agent definitions, architecture14documents, and instructions when present. Apply documented defaults and record15every inferred value in the resulting report.1617## Inspect systematically18191. Read the repository overview, architecture, decisions, and applicable specifications.201. Review existing audits before recording new findings.211. Inspect automation, manifests, workflows, source, tests, and documentation relevant to scope.221. Run read-only diagnostics when they provide reproducible evidence.231. Record material files, tools, commands, or environments that were unavailable.2425## Maintain evidence integrity2627- Label statements as observed, inferred, recommended, or unverified.28- Cite repository-relative paths, symbols, configuration keys, or command results precisely.29- Assign lower confidence when evidence is incomplete.30- Separate the observation, its significance, and the recommendation.31- Record strengths and effective practices, not only defects.32- Avoid repeating prior findings without checking their current state.33- Never present an unavailable or blocked check as completed.3435## Write the report3637Follow the repository's audit specification and output conventions when they38exist.3940Otherwise, create a uniquely named Markdown report under `audits/`. Never41overwrite an existing report.4243During a normal audit, modify only the new audit report. Do not apply fixes,44update dependencies, reformat files, open issues, create commits, or alter45repository configuration unless the request explicitly expands the scope.4647## Validate4849Confirm that the report documents:5051- scope and exclusions52- evidence sources53- commands executed54- positive observations55- findings56- severity and confidence57- uncertainties58- blocked checks59- recommended follow-up work60- a prioritized backlog6162When the audit cannot be completed, produce a truthful partial or blocked63report and identify the next evidence required.
egohygiene