Trace git diffs to regenerate affected .workflow documentation entries.
npx skills add https://github.com/catlog22/Maestro-Flow --skill quality-sync
Please help me install this Agent Skill. Skill: quality-sync Source: https://github.com/catlog22/Maestro-Flow/tree/main/.codex/skills/quality-sync Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill quality-sync
This Skill prevents documentation drift by automatically detecting code changes and synchronizing related documentation entries through file, component, feature, and requirement mappings so docs remain accurate and up to date.
Run quality-sync with --dry-run to preview which documentation entries would be regenerated based on changes since the last synced commit.
High-intent search queries and answers about installing and using this skill.
To keep documentation aligned with code changes automatically, you can use a synchronization tool that traces git diffs through file, component, feature, and requirement layers to detect and regenerate impacted documentation entries.
Git diff documentation synchronization works by comparing tracked files against a baseline commit or last_synced timestamp, mapping those changes through doc-index.json to identify affected entries, and regenerating the impacted documentation.
Yes, you can preview documentation updates by running the synchronization process in --dry-run mode, which identifies and lists affected .workflow/codebase documentation entries without modifying any files.
Yes, you need an initialized .workflow directory and git availability to sync documentation, as the tool relies on doc-index.json for impact tracing and state.json for tracking the last_synced timestamp and commit.
The best way to update architecture docs after a refactor is to run a full resync or baseline sync that automatically maps moved or renamed source files to their corresponding feature and requirement layers to regenerate impacted docs.
When a full resync is performed, content hashes in doc-index.json are updated and state.json records the last_synced timestamp and last_synced_commit, maintaining an auditable sync history for future change detection.
catlog22Refresh documentation entries for files changed in Git.
AstrumonAudit git history and map changed files to Notion documentation zones.
hatch3rConfigure CI/CD agentic workflows across GitHub Actions, Azure Pipelines, and GitLab CI.
dt418Build documentation platforms with versioned docs, search, navigation, code highlighting, and API reference generation.
