doc-updater

To keep project documentation up-to-date with code changes, you can invoke this skill after implementing a ticket. It applies a rubric-based approach to automatically update four key documentation files, ensuring conventions remain accurate and relevant.

You need to update coding conventions after modifying files when changes affect file placement, workflows, or testing rules. This skill modifies only prescriptive rules and conventions in your documentation to reflect those specific code changes.

The best way to track workflow changes in project documentation is using a defined rubric. This skill tracks and applies updates based on a rubric, handling changes in multi-file workflows to improve code quality and maintainability.

Yes, you can use a rule-based approach to update only prescriptive rules in documentation. This skill ensures that only prescriptive rules and conventions are modified, preventing unintended changes to other parts of your project documentation.

Yes, doc-updater works without external dependencies. It operates as a standalone skill using internal scripts to analyze code changes and apply rubric-based updates to your project's documentation files.

A limitation to expect when automating documentation updates is that this skill focuses strictly on prescriptive rules, file placement, and testing conventions. It does not modify general descriptive documentation outside of its defined rubric-based scope.