csummary

You can generate a one-page workflow findings summary by running the csummary skill after QA findings are available. It reads comprehensive workflow artifacts like spec changes, test audits, and verification results to produce a structured, readable report with categorized issues and impact classification.

The best way to create a feature summary for a handoff is to use mid-feature or post-feature reporting. This compiles spec changes, new rules, QA issues, and verification gaps into a shareable artifact with clear impact assessment, making it ideal for PR descriptions and team transitions.

Yes, you can summarize audit trails and git logs alongside test audit results. The workflow findings summary reads comprehensive workflow artifacts, including git logs and audit trails, to compile a complete feature summary with categorized issues, totals, and impact classifications.

A workflow summary handles spec changes and verification gaps by reading comprehensive workflow artifacts and producing a structured artifact. It highlights new rules, test changes, QA issues, and verification gaps with clear impact assessment to show exactly what was caught during the feature lifecycle.

You need to compile a workflow findings summary when you want to generate a look what I saved you report after a feature's QA cycle. It applies to QA findings, spec changes, test audits, and verification results, producing a structured artifact saved to your artifacts directory.

Workflow summary reports are saved as markdown files to the .correctless/artifacts/ directory using a task-slug naming convention. This structured artifact contains categorized issues, totals, and impact classifications from the workflow findings for easy sharing and reference.