author-rules

To update documentation after completing a feature without touching source code, revise README sections and docstrings to reflect behavior changes, then append short changelog entries in the required table format, leaving the codebase untouched.

The best way to maintain changelog hygiene is to append short, timestamped changelog entries in the required table format after a feature is complete, ensuring records are concise and consistent without requiring session context.

You need to update CLAUDE.md conventions only when new cross-cutting rules are introduced, keeping post-feature maintenance aligned with repository standards and avoiding unnecessary edits to the file.

No, author-rules does not modify source code during post-feature documentation maintenance; it focuses exclusively on updating README sections, docstrings, and changelog entries while preserving the codebase exactly as it is.

You should use plain present-tense writing for README documentation and docstring revisions, ensuring concise public-facing notes that allow the next developer to understand changes without needing session context.