system-audit-report

Produce code-grounded audit reports for subsystems from the latest codebase.

34|1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/earayu/treadstone --skill system-audit-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-audit-report
Source: https://github.com/earayu/treadstone/tree/main/.agents/skills/system-audit-report
Command: npx skills add https://github.com/earayu/treadstone --skill system-audit-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Subsystems often lack a grounded, current-view audit. This skill provides a thorough, code-based assessment that ties findings to the actual repository state.

Core Features & Use Cases

  • Generate code-grounded audit reports aligned with the latest codebase.
  • Validate architecture, data flow, and implementation against documentation.
  • Produce a structured, evidence-backed narrative suitable for launch-readiness reviews.

Quick Start

Invoke this skill to generate a comprehensive, code-grounded audit report for a specified subsystem using the latest repository state.

Frequently Asked Questions about system-audit-report

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

FAQPage Schema
How do I generate a code-grounded audit report for a subsystem?

To generate a code-grounded audit report, invoke the skill against a specified subsystem to assess the latest repository state, tying findings directly to concrete evidence like files, functions, and tests.

What is the best way to validate architecture and data flow against existing documentation?

Validating architecture and data flow requires tracing implementation against existing docs using a code-based assessment, ensuring launch readiness by clearly distinguishing verified facts from inferences.

Can I use this for deep architectural reviews and production readiness checks?

Yes, you can use this for deep architectural reviews and production readiness checks, as it produces structured, evidence-backed narratives grounded in the actual current codebase.

How does the audit process distinguish between verified codebase facts and inferences?

The audit process distinguishes facts from inferences by grounding conclusions in concrete evidence extracted from the latest codebase, ensuring every finding references actual files, functions, or APIs.

What limitations exist when validating implementation alignment with this approach?

A key limitation is dependency on the latest repository state; if the codebase is outdated or incomplete, the audit cannot validate implementation alignment accurately against existing documentation.