resolve-review

Automating code review findings involves validating the issue, creating a GitHub issue, setting up a dedicated worktree, and executing the fix implementation workflow. This Skill resolves findings by parsing finding IDs and mapping prefixes to extract detailed file paths and recommended fixes.

Mapping code review finding IDs involves parsing the ID, mapping its prefix to the corresponding review file, and extracting detailed finding information including title, severity, file paths, descriptions, and recommended fixes. This structured parsing ensures accurate identification of the code issue to address.

Creating GitHub issues from code review findings automatically requires integrating with the GitHub API. This Skill validates that a finding still exists, extracts its title and severity, and uses the GitHub API to create a corresponding issue before setting up a worktree to implement the fix.

No manual worktree setup is required. The workflow integrates with project-specific scripts to automatically set up a dedicated worktree for implementing the fix after creating a GitHub issue, ensuring the development environment is prepared systematically without manual intervention.

Yes, you can use this automation to fix security vulnerabilities flagged in code reviews. When a critical security finding like SEC-C2 is flagged, the Skill creates a GitHub issue, prepares a development environment via worktree setup, and guides the developer through applying the necessary security patch.

The workflow relies on parsing specific finding IDs and mapping prefixes to review files, meaning findings must follow a structured format to be extracted correctly. It also depends on GitHub API integration and project-specific scripts for worktree setup and fix implementation to function properly.