Draft, refresh, and audit architecture documentation against actual codebase state.
npx skills add https://github.com/wildlily1021/XW_Software --skill cs-arch-wildlily1021
Please help me install this Agent Skill. Skill: cs-arch Source: https://github.com/wildlily1021/XW_Software/tree/main/.agents/skills/cs-arch Command: npx skills add https://github.com/wildlily1021/XW_Software --skill cs-arch-wildlily1021
codestable/architecture/ through three disciplined modes: backfill, update, and check. ## Core Features & Use Cases - Backfill: Write a new architecture doc for a module that exists in code but was never documented, with every structural claim anchored to file:line evidence. - Update: Refresh an existing doc based on recent code changes, updating last_reviewed and the ARCHITECTURE.md index. - Check: Run consistency audits across three sub-targets (design-internal, design-vs-code, architecture-folder-internal) and produce a severity-graded report without modifying anything. - Use Case: After merging a feature, ask for an architecture check to verify the design doc matches the implemented code, receiving a report listing each inconsistency with location, impact, and suggested fix. ## Quick Start Ask the assistant to check whether the current feature design document matches the actual code implementation.High-intent search queries and answers about installing and using this skill.
Use the update mode to refresh an existing architecture doc based on recent code changes since its last_reviewed date. Every structural claim must anchor to a file:line location, and unverifiable statements are marked TODO rather than invented.
Run the check mode with the design-vs-code sub-target. It verifies type consistency, behavior, write paths, boundary handling, and change scope across six categories, then outputs a report with severity levels and fix suggestions without modifying anything.
Backfill writes a new doc for code that exists but was never documented. Update refreshes an existing doc against current code. Check only audits consistency and produces a report without writing or fixing anything.
No. It only records the current state of the system. Future plans, target architectures, and refactoring proposals belong to a separate roadmap skill, keeping architecture docs free of unimplemented speculation.
Separating detection from repair lets users review the complete inconsistency list and decide priorities holistically. The report includes concrete fix suggestions with locations, but applying them is a deliberate follow-up action.
liuzhengdongfortestAutomate repository onboarding into the CodeStable framework with scaffolding or migration mapping.
tmcfarlaneCreate technical implementation plans and architecture designs with risk considerations.
dhruvb14Retrieve historical Plenum HVAC failure analyses and established fixes.
Jet-labsGenerate API docs, Mermaid diagrams, and Markdown guides from codebases.