Synchronize Confluence documentation with codebase changes from git history.
npx skills add https://github.com/digimap2000/auracle_now_moved --skill auracle-docs
Please help me install this Agent Skill. Skill: auracle-docs Source: https://github.com/digimap2000/auracle_now_moved/tree/main/.skills/auracle-docs Command: npx skills add https://github.com/digimap2000/auracle_now_moved --skill auracle-docs
This Skill ensures that the external-facing Confluence documentation for the Auracle project remains accurate and up-to-date with the latest codebase changes, preventing documentation drift and maintaining a reliable source of truth for developers and management.
Use the auracle-docs skill to update the Confluence documentation after a batch of commits has landed.
High-intent search queries and answers about installing and using this skill.
To sync Confluence documentation with codebase changes, review git history to identify recent commits, compare them against existing Confluence pages to find discrepancies, and update content to accurately reflect the current code state.
Documentation drift occurs when technical documentation becomes outdated relative to the codebase. You can identify drift by comparing the current code state against existing Confluence pages to pinpoint discrepancies in features, status markers, or architectural changes.
You should update Confluence pages after a development sprint concludes or after significant development milestones. Triggering the documentation synchronization process at these points ensures all new features and architectural adjustments are accurately reflected.
To manage machine-readable metadata in a Confluence knowledge base, update an AI Appendix with document history and image descriptions. This maintains a reliable source of truth for developers and management while tracking content updates.
Yes, the documentation sync process works without external dependencies. It relies on internal references and scripts to review git history, identify discrepancies, and update Confluence pages without requiring additional external libraries or tools.
hhk7734Analyze git diffs and commits between two references for code quality and security.
leolionartPublish Markdown content to Confluence with synchronized metadata and formatting.
tkstangEvaluate OAT project progress and recommend the next skill to execute.
alvazoneCompare spec nodes against codebase implementation to identify drift.
