retrocheck

Run structural conformance scripts and semantic audits to detect code drift.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Pyl-Tech/stream-coding --skill retrocheck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrocheck
Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/retrocheck
Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill retrocheck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents drift by checking that existing code still matches the current specs, methodology rules, and required test coverage after changes or completed work.

Core Features & Use Cases

  • Retroactive spec conformance: Scans code against the full set of spec requirements, anti-patterns, and error-handling expectations.
  • Deterministic structural gates: Runs fast, deterministic scripts to catch spec-code drift, missing TDD coverage, and UI/design-token inconsistencies.
  • Learning and methodology alignment: Verifies that fixes recorded in learnings are actually reflected in the targeted modules.
  • Gate readiness assessment: Assesses whether each module would pass current Spec/TDD/Verify gates if rebuilt today.

Quick Start

Run retrocheck after your build finishes or after a methodology update to ensure earlier modules did not skip gates that are now enforced.

Frequently Asked Questions about retrocheck

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

FAQPage Schema
How do I check if existing code still aligns with current specs after changes?

To check spec conformance, run structural scripts and perform semantic module-by-module audits to detect drift across full projects, ensuring existing code matches current methodology rules and test requirements.

What is methodology drift detection and when do I need it?

Methodology drift detection scans code against current specs, anti-patterns, and error-handling expectations. You need it after methodology changes, major builds, or when resuming work to catch spec-code drift.

How do I audit code for anti-patterns and missing TDD coverage retroactively?

Retroactive code audits run deterministic structural gates to catch spec-code drift, missing TDD coverage, and UI design-token inconsistencies, while verifying that fixes recorded in learnings are reflected in targeted modules.

Can I assess whether my modules would pass quality gates if rebuilt today?

Gate readiness assessment evaluates whether each module would pass current Spec, TDD, and Verify gates if rebuilt today, producing a non-negotiable actionable divergence report for full projects or selected modules.

Do I need any external dependencies to run spec conformance scripts?

No external dependencies are required. The spec conformance scripts run autonomously to perform structural checks and semantic audits without needing additional packages or external tools.

What's the best way to verify learnings conformance across targeted modules?

Learnings conformance is verified by performing semantic module-by-module audits with full file reads, checking that previously recorded fixes are actually reflected in the targeted code modules.