Automatically generates and maintains a project's CHANGELOG.md file by analyzing code changes, commits, or version control history to produce structured release notes.
Produce release notes
Run this loop to automatically generate and validate release notes in your project's CHANGELOG.md file.
Initiate Loop
Start the loop by requesting the agent to generate the changelog.
Audit Changes
The agent will analyze changes and update the changelog file.
Verify Completion
Run the check command to ensure the changelog meets quality standards and contains all necessary information.
Collect Changes
Gather all changes from the current development cycle using git history or change files.
Categorize Changes
Sort changes into appropriate categories like Added, Changed, Fixed, etc.
Format Entries
Write formatted changelog entries following the standard structure.
Docs
Automatically identifies areas in your codebase lacking usage examples and iteratively adds them to improve documentation coverage. The agent focuses on generating practical, copy-paste-friendly examples for functions, methods, and components that currently lack adequate documentation.
Docs
Automatically synchronizes API documentation with the codebase to ensure no drift occurs between implementation and documented interfaces. This loop detects discrepancies, generates necessary updates, and applies them while respecting guardrails to maintain consistency and quality.
Docs
This loop identifies and documents all missing features in a codebase to achieve full documentation coverage. It systematically audits the existing documentation, finds gaps, and fills them with appropriate documentation until the audit passes.
Update Changelog File
Append new entries to CHANGELOG.md under the correct version header.
Audit Changelog
Run the check command to verify completeness and formatting.
Start the "Changelog Generator" loop. Goal: Produce release notes Max iterations: 10 Between iterations run: changelog audit Exit when: Changelog complete Please generate the next set of release notes for the upcoming version. Analyze recent commits, changes, and updates to create a properly formatted changelog entry following the Keep a Changelog format. Self-pace this loop. After each iteration, run `changelog audit` and evaluate the output, and only continue if the exit condition is not met (Changelog complete). Stop when the exit condition passes or 10 iterations are reached. Give a short status update each pass.
