finalize

Automate staging, testing, code simplification, AI review, and pull request generation.

399|31|Updated Mar 11, 2026

Search Tags:#automation #git #testing #code review #pull request #commit

Ready to run

npx skills add https://github.com/tobihagemann/turbo --skill finalize-tobihagemann

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: finalize
Source: https://github.com/tobihagemann/turbo/tree/main/skills/finalize
Command: npx skills add https://github.com/tobihagemann/turbo --skill finalize-tobihagemann

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of finalizing code changes by automating essential quality assurance steps, ensuring code is tested, simplified, reviewed, and ready for commit and deployment.

Core Features & Use Cases

Automated QA Workflow: Executes a sequence of tests, code simplification, and AI-driven reviews.
Commit and PR Management: Handles staging, committing, pushing, and optionally creating or updating pull requests.
Use Case: After completing a feature implementation, use this skill to automatically run all necessary checks, fix formatting issues, ensure code quality, and prepare a pull request for review.

Quick Start

Use the finalize skill to run the post-implementation quality assurance workflow.

Frequently Asked Questions about finalize

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

FAQPage Schema

How do I automate code review and pull request generation after finishing a feature?▼

Automating code review and pull request generation requires a post-implementation workflow that stages changes, runs tests, simplifies code, and creates commits. This skill executes that sequence to ensure code quality and readiness for integration.

What is the best way to run a QA workflow before committing code with git?▼

The best way to run a QA workflow before committing is to automate staging, testing, and AI-driven review sequentially. This skill handles that process, ensuring formatting is fixed and code is simplified before generating a commit.

Does this automated testing and commit workflow require the gh CLI?▼

Yes, this automated testing and commit workflow requires the gh CLI and git. These dependencies are necessary to handle staging, pushing, and creating or updating pull requests directly from the command line.

Can I use this to update an existing pull request instead of creating a new one?▼

Yes, you can use this to update an existing pull request. The workflow handles staging, committing, and pushing changes, and will optionally create or update pull requests to prepare your code for review.

How does AI-driven code simplification work during the commit process?▼

AI-driven code simplification during the commit process works by automatically analyzing staged changes to reduce complexity and fix formatting. This skill integrates simplification into the quality assurance workflow before finalizing the commit.

When should I avoid using an automated post-implementation workflow for pull requests?▼

You should avoid using an automated post-implementation workflow for pull requests when manual intervention or highly specific review criteria are required. This skill standardizes the process, which may limit granular control over complex code simplification.