finish

Run tests, linting, formatting, and CI checks across polyglot repositories.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/SAZO-KR/sazo-toolkit --skill finish-sazo-kr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish
Source: https://github.com/SAZO-KR/sazo-toolkit/tree/main/packages/ai-harness/skills/finish
Command: npx skills add https://github.com/SAZO-KR/sazo-toolkit --skill finish-sazo-kr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers to finalize a PR-ready state by running tests, formatting, linting, type checks, and CI gate validations across a polyglot repository.

Core Features & Use Cases

  • Orchestrates language-specific test execution across Node, Python, Go, Rust, and other ecosystems to verify PR readiness.
  • Runs formatters and linters to ensure codebase consistency and style conformance.
  • Aggregates results and reports gating criteria to guide PR review decisions.

Quick Start

Run the finish skill to validate tests, formatting, linting, and CI readiness across the repository before creating a PR.

Frequently Asked Questions about finish

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

FAQPage Schema
How do I run PR readiness checks across a polyglot codebase with Node, Python, Go, and Rust?

PR readiness checks across a polyglot codebase are automated by coordinating language-specific test commands, linters, and formatters to ensure consistent PR gates. It runs tests, formatting, linting, and type checks across Node, Python, Go, and Rust ecosystems.

What is the best way to automate linting and formatting checks before creating a pull request?

Automating linting and formatting checks before a pull request is handled by running language-specific formatters and linters to verify codebase consistency and style conformance. It aggregates results to provide a consolidated report guiding PR review decisions.

Does this CI validation tool support type checks and basic CI configuration readiness for multiple languages?

CI validation supports type checks where applicable and verifies basic CI configuration readiness for multiple languages. It orchestrates language-specific test execution across Node, Python, Go, Rust, and other ecosystems to confirm PR gating criteria.

How do I validate test success and lint status across different programming languages in one run?

Validating test success and lint status across different programming languages in one run is achieved by orchestrating language-specific test execution and linters. It aggregates test, lint, format, and type check results into a consolidated report for PR gating.

Can I use this to consolidate PR gating criteria for a multi-language repository?

Consolidating PR gating criteria for a multi-language repository is exactly what this does by aggregating test, lint, format, and type check results. It coordinates language-specific commands across ecosystems to ensure consistent PR gates and reports gating criteria.

When do I need to run final PR readiness checks and CI validations?

Final PR readiness checks and CI validations are needed before creating a PR to verify test success, lint and format status, and type checks. Running the finish skill validates CI readiness across the repository to guide PR review decisions.