boring-loop-implement

To automate Kanzen issue implementation and pull request review, you can use this Skill to execute code changes, manage the PR lifecycle, and run visual review checks while adhering to trunk-based development rules. It streamlines the entire workflow from branching to owner-ready handoff.

Trunk-based development proof-of-work documentation involves capturing visual review evidence and code analysis results during software implementation. This Skill automates gathering that proof, ensuring structured coding workflows meet strict review requirements before final owner approval.

Yes, you can automate code review and PR management for approved plan slices. This Skill executes the specific code changes required, creates the pull request, and performs thermo-nuclear code analysis to prepare the handoff for final owner approval.

This automated software development workflow supports GitHub issue tracking by processing the currently selected issue. It takes the GitHub issue or approved plan, automatically branches the code, implements the required changes, and prepares the pull request for review.

A limitation of automating software issue implementation is that it requires adherence to strict Kanzen framework rules, including trunk-based development and visual review. It is designed for structured coding workflows and still requires final owner approval before merging.