Detect engineering drift by comparing codebases against specifications and enforcing quality gates.
npx skills add https://github.com/Sharper-Flow/Advance --skill adv-audit
Please help me install this Agent Skill. Skill: adv-audit Source: https://github.com/Sharper-Flow/Advance/tree/main/skills/adv-audit Command: npx skills add https://github.com/Sharper-Flow/Advance --skill adv-audit
This skill solves the problem of engineering drift, where the implementation of a project diverges from its original specifications, leading to hidden bugs, orphaned code, and technical debt.
Execute the adv-audit skill to perform a full project conformance check and generate a quality report.
High-intent search queries and answers about installing and using this skill.
Spec-to-code drift detection identifies discrepancies between engineering specifications and codebase implementation. It scans project worktrees to map requirements, automatically finding orphaned code and normative language violations where implementation diverges from defined specs.
To automate conformance checks, execute an automated drift scan across project worktrees. This validates that all MUST and SHALL requirements are implemented and enforces quality gates based on predefined thresholds for coverage, ambiguity, and architectural alignment.
Yes, you can enforce quality gates automatically by validating project health against strict predefined thresholds. This process checks for requirement coverage, ambiguity, and architectural alignment to ensure codebase implementation meets defined spec conformance standards.
Automated requirement mapping works across project worktrees to identify missing requirements and constraint violations. It operates across the codebase implementation to detect orphaned code, normative language violations, and conflicting specs.
The best way to find conflicting specs is through automated drift scanning. This process compares codebase implementation against defined engineering specifications to identify normative language violations and spec conflicts.
You should run a spec-to-code audit before a release to prevent engineering drift. This ensures all normative requirements are implemented, validates project health against quality gates, and confirms no orphaned code remains in the repository.
AustinZ21Generate standardized feature specifications from natural language descriptions.
krzemienskiDetect architectural drift from ADRs and compute alignment scores.
jmaglyMaps requirements to code and tests, computes coverage gaps and generates a traceability report.
ajsai47Analyze git diffs for SQL injection, race conditions, and shell injection risks.
