OffLine Documentation Standards
This skill defines how to maintain project documentation.
1. CHANGELOG.md
We follow Keep a Changelog format.
Rules
- •Header: Always use
## [Unreleased]for new changes. - •Categories: Group changes under:
- •
### Addedfor new features. - •
### Changedfor changes in existing functionality. - •
### Deprecatedfor soon-to-be removed features. - •
### Removedfor now removed features. - •
### Fixedfor any bug fixes. - •
### Securityin case of vulnerabilities.
- •
- •Content: Descriptions should be concise and user-focused.
Example
markdown
## [Unreleased] ### Added - Auto-scroll to bottom when loading chat files. ### Fixed - Memory parsing issue on Safari.
2. README.md
The README is the landing page for the project.
Rules
- •Features Section: Must be kept up-to-date with new major capabilities.
- •Tech Stack: Update if new libraries are added.
- •Consistency: Ensure the "How to use" steps remain accurate.
3. Workflow
- •Synchronous Update: Documentation should be updated in the same PR/Commit as the code change.
- •Verification: Check rendered markdown for formatting errors.