Finalize is a skill published by agensi that acts as an automated quality assurance step for a software repository. When invoked, it systematically scans the working directory to identify and remove temporary artifacts, detect debug leftovers such as console logs and hardcoded paths, update relevant documentation, and execute the project’s native validation suites — including tests, linters, and type-checkers.

The skill follows a multi-step workflow: it inventories the current repository state, classifies files to avoid accidental deletion, searches for sensitive data leaks, and infers the correct test and build commands by reading the project’s own configuration files. Supported configuration formats include package.json for Node.js projects, Cargo.toml for Rust, and Makefiles for Make-based builds. It also integrates with Git to perform status and diff analysis.

Supported languages and runtimes include Node.js, Python, Go, Rust, Java, Kotlin, and Ruby. Task runners Make and Just are supported, as are package managers npm, pip, cargo, and maven.

This skill is suited for the moment just before a commit, pull-request submission, or handoff to another team member, when manual verification of repository cleanliness would otherwise be tedious and error-prone. It does not provide ongoing CI/CD pipeline orchestration, and it requires the agent to have filesystem and Git access to the working directory.

Use cases

Clean up temporary log files and scratch files before opening a pull request

Detect and flag console.log statements or hardcoded paths left in source code

Automatically run the correct test suite by inspecting package.json, Cargo.toml, or Makefiles

Scan for accidentally committed sensitive data or credentials before a handoff

Update README or other documentation to reflect the current state of the repository

Run linters and type-checkers across a multi-language project as a pre-commit gate

When to use it

Before committing or pushing code when a clean, validated state is required

Before handing a repository off to another developer or team

When working across Node.js, Python, Go, Rust, Java, Kotlin, or Ruby projects that need consistent QA

When the project uses Make, Just, npm, pip, cargo, or maven as its task runner or package manager

When Git integration is available and diff-based analysis of changed files is needed

When not to use it

When the agent does not have filesystem access to the working directory

For languages or runtimes not listed in the supported set, such as PHP or Swift

As a replacement for a full CI/CD pipeline with remote build environments

When no Git repository is present and version-control-based analysis is required

When only cloud-hosted or containerized environments are accessible without local file access