skills.rest
saitoco
saitocoOFFICIAL
Explore all skills by this author →
GitHub

audit

Detect drift and fragility between steering documents and codebases.

Updated Apr 6, 2026
Search Tags:#automation#github#code-quality#drift#issue-generation#fragility
One-click install
npx skills add https://github.com/saitoco/wholework --skill audit-saitoco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/saitoco/wholework/tree/main/skills/audit
Command: npx skills add https://github.com/saitoco/wholework --skill audit-saitoco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drift between Steering Documents, Project Documents, and code is detected and translated into actionable issues for code-side fixes.

Core Features & Use Cases

  • Drift detection between Steering Documents and the codebase, producing Issues for code fixes.
  • Fragility detection to identify risk hotspots and propose improvements via Issues.
  • Integrated analytics and reporting (via /audit stats and /audit recoveries) to surface project health.

Quick Start

Run /audit to detect drift and fragility across your project in a single integrated run.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I detect drift between project documentation and my codebase?▼

Detect drift between project documents and code by running an integrated audit that compares steering documents to the codebase, classifies discrepancies, and auto-creates GitHub issues with audit labels for code-side fixes.

What is code fragility detection and how does it identify risk hotspots?▼

Code fragility detection analyzes your codebase against project documents to identify risk hotspots, proposing improvements by automatically generating GitHub issues tagged with audit/fragility labels for necessary fixes.

Can I generate project health statistics from steering documents and code?▼

Yes, generate project health statistics by running targeted audit commands that analyze steering documents, project documents, and code to surface integrated analytics and recovery reports recorded in docs/reports.

What's the best way to automate GitHub issue generation for code drift?▼

Automate GitHub issue generation for code drift by executing a single integrated audit run that uses git and gh to classify issues, assign audit/drift labels, and record metadata for code-side fixes.

Do I need steering and project documents to run drift and fragility analyses?▼

Yes, drift and fragility detection requires software projects to maintain both steering documents and project documents alongside the codebase to accurately compare specifications and auto-create issues.

Related Skills

Explore More Software Engineering Skills→
notta50notta50

kiro-steering

Bootstrap and synchronize .kiro/steering files with template-based generation and drift detection.

Community
Intermediate
jeremylongshorejeremylongshore
2.6k

detecting-infrastructure-drift

Detect infrastructure drift between current state and desired configuration.

Community
Advanced
jacobcyjacobcy
6

vibe-roadmap

Assign GitHub issues to milestones and roadmap labels via gh.

Community
Intermediate
yun520-1yun520-1
38

code-analyzer

Analyze codebases for architectural patterns, code quality, and DDD elements.

Community
Advanced