What it does

Reads a code file or function and returns a concise explanation of its purpose, main logic, dependencies, and important side effects. The summary helps developers understand unfamiliar code without replacing direct inspection or testing.

How it works

Provide the code, programming language, relevant repository context, and the audience for the summary. Ask for emphasis on areas such as public interfaces, data flow, error handling, or known risks. A developer should verify the result against the source before it becomes documentation.

Example workflows

• Summarize changed code for a pull request review.

• Create onboarding notes for an unfamiliar service or module.

• Draft reference documentation from selected functions and interfaces.