documenter

You can automatically generate PR descriptions and RESOLUTION.md files by processing completed research, plan, and review artifacts through the documenter workflow. Run 'documenter generate <slug>' to produce standardized documentation for resolved bugs and features.

To document resolved bugs in a CI/CD pipeline, apply automated documentation generation to your continuous integration and delivery workflows. This creates RESOLUTION.md files and PR descriptions directly from completed development artifacts, ensuring future engineers have necessary context.

Yes, you can collect and report metrics on the development process alongside automated documentation generation. The skill captures process data from bug tracking and feature development artifacts to produce both documentation and metrics reporting.

Automated documentation generation works without external dependencies, but requires processing and formatting capabilities within your environment. The skill operates standalone to transform research, plan, and review artifacts into structured RESOLUTION.md files and PR descriptions.

You need to generate RESOLUTION.md files after a bug fix or feature implementation is completed and approved. This ensures future engineers have all necessary resolution information by automatically capturing details from research, plan, and review artifacts.

Automated bug tracking documentation generation requires completed research, plan, and review artifacts as input, and depends on processing and formatting capabilities. It cannot generate documentation from incomplete or missing development artifacts in your workflow.