Rebuild design-contract documentation from code with a validation gate.
npx skills add https://github.com/VincentJiang06/skills --skill reorganize-logic
Please help me install this Agent Skill. Skill: reorganize-logic Source: https://github.com/VincentJiang06/skills/tree/main/skills/reorganize-logic Command: npx skills add https://github.com/VincentJiang06/skills --skill reorganize-logic
When a project's design documentation (architecture diagrams, structure maps, interface contracts) has rotted so severely that incremental syncing is no longer effective, stale docs create a risk of inaccurate documentation that appears correct but does not match the actual code, leading to development errors and bugs. This Skill solves that by rebuilding the entire design-contract layer directly from the codebase, with code as the single source of truth.
Use the reorganize-logic skill to rebuild your project's design contract layer from the current codebase, replacing all stale architecture, structure, and interface documentation with accurate, code-verified versions.
High-intent search queries and answers about installing and using this skill.
Rebuilding stale design contracts from code involves re-deriving architecture diagrams, structure maps, and interface definitions directly from the current codebase, treating code as the single source of truth to replace rotted documentation.
Incremental syncing fails when documentation has rotted severely, creating inaccurate docs that look correct but mismatch the actual code, leading to development errors; a full contract rebuild from code eliminates this green-but-wrong doc risk.
A deterministic validation gate is a language-agnostic script that cross-references every documented interface to a real code file:line, flags ambiguous near-name matches, and blocks on inconsistencies to eliminate incorrect documentation.
You cannot auto-delete legacy docs during a rebuild; the process generates a deletion manifest for stale docs but requires explicit human approval for all deletions to avoid data loss and ensure review-gated legacy cleanup.
Yes, the design contract rebuild applies to codebases of any size, supporting scoped runs for individual modules or full-project rebuilds to enforce end-to-end traceability across the entire architecture.
You should avoid incremental updates and do a full contract rebuild when existing design documentation has rotted past the point where syncing is effective, risking inaccurate documentation that appears correct but does not match the actual code.
galz10Document codebase architecture and data flows with file:line references.
Anders-planckStandardize technical documentation creation, review, and publishing with templates and validation.
nesihaver-ILUpdate README, API, architecture docs, and changelogs after code changes.
markmhendricksonAutomates software release process including merging branches, versioning tagging commits, deploying to production.
