finalize

Coordinate multi-round code-quality passes between implement and acceptance phases.

23|2|Updated Mar 7, 2026

Search Tags:#automation #code-quality #developer-workflow #code-review #finalize #multi-round #pr-toolkit

Ready to run

npx skills add https://github.com/kirich1409/krozov-ai-tools --skill finalize-kirich1409

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: finalize
Source: https://github.com/kirich1409/krozov-ai-tools/tree/main/plugins/developer-workflow/skills/finalize
Command: npx skills add https://github.com/kirich1409/krozov-ai-tools --skill finalize-kirich1409

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The finalize skill provides a structured, multi-round code-quality pass that polishes how code is written between implement and acceptance, reducing defects before review and integration.

Core Features & Use Cases

Orchestrates a full workflow including code-reviewer, /simplify, optional pr-review-toolkit trio, and conditional expert reviews with /check between rounds.
Manages matching findings (BLOCK, WARN, NIT) across phases and enforces max-round escalation to PASS or ESCALATE.
Ideal for feature branches and bugfix flows where code quality and readability matter before acceptance.

Quick Start

Start a finalize round on the current branch to run the quality pass and trigger the integrated review workflow.

Frequently Asked Questions about finalize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate multi-round code review passes before merging a feature branch?▼

Automated multi-round code review passes coordinate iterative quality checks between implementation and acceptance, applying reviewer findings and simplification rules until code meets quality standards or escalates unresolved blocks.

What is the best way to polish code quality on a bugfix branch before acceptance?▼

Polishing code quality on a bugfix branch involves running structured code-reviewer loops and simplification phases, matching findings like BLOCK or WARN across rounds to ensure readability and reduce defects before integration.

How does a multi-round code-quality workflow handle unresolved blocking issues?▼

A multi-round code-quality workflow enforces maximum round limits and escalates unresolved BLOCK findings, exiting with an ESCALATE status instead of forcing a merge when critical code issues remain unresolved.

Can I integrate pr-review-toolkit and expert reviews into my developer workflow?▼

You can integrate the pr-review-toolkit trio and conditional expert reviews into your developer workflow, orchestrating them alongside code-reviewer and simplification phases with checks between each round.

When do I need a structured code-quality pass for my pull requests?▼

You need a structured code-quality pass for pull requests when feature or bugfix branches require iterative readability and defect reduction loops before final acceptance, ensuring code style is polished independently of functionality.

Does the finalize code review process support categorizing findings by severity?▼

The code review process supports matching findings by severity, categorizing issues into BLOCK, WARN, and NIT levels across phases to prioritize resolution and determine whether the workflow exits with PASS or ESCALATE.