describe-changes

To generate a summary of code changes needed, invoke the describe-changes skill after discussing the feature. It reads relevant files to validate understanding, then produces a concise, high-level list of functional, test, and documentation modifications required.

Summarizing code modifications across functional, test, and documentation files is best handled by validating that the relevant files have been read first. This ensures the generated description accurately reflects the actual scope of required updates before changes are implemented.

Checking if an AI agent has read files before describing required code changes is enforced by mandating file reading prior to inclusion. The agent validates its understanding by reading relevant files, preventing inaccurate or hallucinated summaries of code modifications.

Confirming the scope of code updates for feature implementation involves articulating specific modifications needed across files. The skill generates a clear, concise list of all functional, test, and documentation files that will be modified to implement the discussed functionality.

You need a high-level description of required code changes after discussing a new feature or fix. It helps confirm the AI agent's understanding of the modifications required, ensuring scope alignment before actual development and testing work begins.

Yes, this code change summarizer works without external dependencies. It operates independently to compose a concise, high-level description of required code modifications, relying solely on its internal logic to read files and validate agent understanding.