Compare code changes against project documentation to surface inconsistencies.
npx skills add https://github.com/nexu-io/nexu --skill sync-specs-nexu-io
Please help me install this Agent Skill. Skill: sync-specs Source: https://github.com/nexu-io/nexu/tree/main/skills/localdev/sync-specs Command: npx skills add https://github.com/nexu-io/nexu --skill sync-specs-nexu-io
Review code changes and ensure documentation stays up-to-date across the project.
Run the sync-specs skill to audit and align docs with the latest code changes.
High-intent search queries and answers about installing and using this skill.
You can keep docs aligned with code changes by running a delta audit that compares modified code against project documentation. This surfaces inconsistencies and guides targeted updates across affected files and specs without reviewing the entire project.
A delta audit focuses on comparing recently modified code against existing docs to surface drift, while a full audit aligns all project documentation with the current codebase. Delta is faster for targeted updates; full is comprehensive across files, packages, and specs.
Scope documentation checks by configuring Mode and Scope keywords to target specific areas like API docs or architecture specs. This focuses the audit on relevant files and packages, guiding precise documentation updates without scanning the entire project.
Yes, a full audit aligns all project documentation, including product specs and architecture docs, with the latest codebase updates. It comprehensively reviews files and packages to ensure every spec reflects current code changes.
The best way to review documentation for code changes is running a delta audit by default, which compares modified code against project docs and surfaces inconsistencies. This guides targeted updates across files, packages, and specs to keep documentation aligned.
Yes, sync-specs runs with no external dependencies or plugins. It uses an internal change-mapping workflow to compare code changes against documentation and surface inconsistencies across files, packages, and specs.
J-PsterValidate and create mandatory project documentation baseline files before implementation.
Andamio-PlatformScan MDX docs against the v2 transaction tracker and surface coverage gaps.
SJTU-IPADSAutomate compliant quality documentation for medical devices with version control and audit trails.
openharmonyinsightCheck OpenHarmony API documentation for template compliance and consistency against d.ts declarations.
