codeloop_generate_dev_report
MANDATORY at task end. Produce docs/DEVELOPMENT_LOG.md summarising the verify → diagnose → fix → gate evidence.
When to use codeloop_generate_dev_report
Use `codeloop_generate_dev_report` when your AI agent needs to mandatory at task end. produce docs/development_log.md summarising the verify → diagnose → fix → gate evidence.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| project_name | string | yes | Display name for the report. |
| project_description | string | no | Brief description of what was built. |
| project_dir | string | no | Project root. |
What you get back
Path to generated report + a summary table.
FAQ
What does codeloop_generate_dev_report do?
MANDATORY at task end. Produce docs/DEVELOPMENT_LOG.md summarising the verify → diagnose → fix → gate evidence.
When should an AI agent call codeloop_generate_dev_report?
Use `codeloop_generate_dev_report` when your AI agent needs to mandatory at task end. produce docs/development_log.md summarising the verify → diagnose → fix → gate evidence.
What does codeloop_generate_dev_report return?
Path to generated report + a summary table.
Is codeloop_generate_dev_report part of the CodeLoop MCP server?
Yes. CodeLoop ships as an MCP server installed via `npx codeloop init`. Cursor and Claude Code call it automatically once the User Rule (Cursor) or CLAUDE.md (Claude Code) is in place.