hotfix

Creates an emergency hotfix branch from main and triggers a fast-track patch release to production.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Evolutionary-Leadership/harness --skill hotfix-evolutionary-leadership
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/Evolutionary-Leadership/harness/tree/main/.claude/setup/railway/.claude/skills/hotfix
Command: npx skills add https://github.com/Evolutionary-Leadership/harness --skill hotfix-evolutionary-leadership

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When production breaks, the normal feature → preprod → release flow is too slow. This Skill provides a controlled fast path: branch directly from main, apply a minimal fix, open a PR to main, and auto-tag a patch release, while still enforcing an authority check so unapproved sessions cannot ship to production. ## Core Features & Use Cases - Authority gating: Before any work begins, the Skill checks the agent-authority list in .harness-version or requires an explicit in-turn user request, and stands down cleanly if neither holds. - Fast-track release flow: Creates a hotfix/<name> branch from origin/main, writes a .pr-description.md signal file with hotfix: true and the next patch version, then pushes so GitHub Actions opens the PR, tags the release, and back-merges main into preprod. - Lightweight docs discipline: Runs scripts/check-docs.mjs if present, updates docs/SECURITY.md when the fix touches auth or secrets, and records follow-ups (runbook, ADR, regression test) in the PR body. - Use Case: A production outage is traced to a bad input validation check. You invoke the hotfix flow, apply the one-line fix, and the harness ships v1.2.4 to production with Railway redeploying automatically. ## Quick Start Ask the assistant to run the hotfix skill with a short description of the production issue, for example: "/hotfix fix null pointer in checkout handler".

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I ship an emergency fix to production with GitHub Actions?

Create a hotfix branch from origin/main, apply the minimal fix, and push with a .pr-description.md signal file containing hotfix: true and the next patch version. The workflow opens a PR to main, tags the release on merge, and back-merges main into preprod.

How does the hotfix skill decide who is allowed to release?

It reads the agent-authority list from .harness-version and checks whether hotfix is granted there, or whether the user explicitly asked for the hotfix in the current turn. If neither holds, the session stands down without pushing anything.

Can I perform the hotfix steps manually instead of invoking the skill?

No. Writing the signal file, committing, and pushing it by hand is treated as the same act and is refused under the same authority rules. The guard applies to the procedure itself, not just the literal skill invocation.

Does a hotfix skip documentation updates entirely?

No. It runs scripts/check-docs.mjs if present, updates docs/SECURITY.md when the fix touches auth, secrets, limits, or validation, and updates any documented surface row it changes. Larger items like runbooks and ADRs become PR checklist follow-ups.

How is the hotfix version number determined?

The skill reads the latest tag on origin/main with git describe and bumps the patch component, so v1.2.3 becomes v1.2.4. If no tag exists, it starts from v0.0.0.

What happens after the hotfix PR merges to main?

The workflow tags the new patch version, creates a GitHub Release marked as a hotfix, redeploys the production Railway environment automatically, and back-merges main into preprod to prevent branch drift.