harness:deploy

Clean up artifacts, tag releases, and push to version control.

43|5|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/raphaelchristi/harness-evolver --skill harness-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness:deploy
Source: https://github.com/raphaelchristi/harness-evolver/tree/main/skills/deploy
Command: npx skills add https://github.com/raphaelchristi/harness-evolver --skill harness-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It automates the finalization of evolution results, including cleanup, tagging, and pushing releases to version control.

Core Features & Use Cases

  • Clean up temporary artifacts produced during evolution.
  • Tag and publish the best performing iteration to the main branch.
  • Provide a reproducible handoff by pushing release notes and diffs to the repository.

Quick Start

Run the deploy workflow to finalize, tag the best result, and push to the main branch.

Frequently Asked Questions about harness:deploy

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

FAQPage Schema
How do I automate git tagging and release finalization for end-of-run deployment workflows?

Automate git tagging and release finalization by running a guarded deployment workflow that cleans up artifacts, tags the best performing iteration, and pushes release notes to version control. This provides reproducible release artifacts and traceable history.

What is the best way to clean up temporary artifacts before pushing a release to the main branch?

The best way to clean up temporary artifacts before pushing a release is to run an automated finalization workflow that removes leftover evolution results, tags the release, and pushes the clean state to the main branch.

Can I use interactive prompts during the deployment and git tagging process?

Yes, you can use interactive prompts during the deployment and git tagging process. The workflow supports optional interactive prompts defined in the frontmatter to guard the deployment flow and ensure safe handoff to production.

How does release tagging work for reproducible evolution results in version control?

Release tagging for reproducible evolution results works by tagging the best performing iteration and pushing release notes along with diffs to the repository. This creates traceable history and a quick, reproducible handoff to production.

Do I need environment setup to automate git tagging and artifact cleanup?

Yes, environment setup is required to automate git tagging and artifact cleanup. The deployment flow satisfies guarded deployment requirements by ensuring the environment is configured before finalizing evolution results and pushing to version control.