skills.rest
Evolutionary-Leadership
Evolutionary-LeadershipOFFICIAL
Explore all skills by this author →
GitHub

rollback

Revert production main branch to a previous release tag and create a tracking issue.

Updated Aug 13, 2026
Search Tags:#ci/cd#rollback#github#git revert#production deploy#incident tracking#release tag
One-click install
npx skills add https://github.com/Evolutionary-Leadership/harness --skill rollback-evolutionary-leadership
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rollback
Source: https://github.com/Evolutionary-Leadership/harness/tree/main/.claude/skills/rollback
Command: npx skills add https://github.com/Evolutionary-Leadership/harness --skill rollback-evolutionary-leadership

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a production deploy breaks, you need a fast, auditable way to restore the last working release without losing git history or bypassing your team's authorization rules. ## Core Features & Use Cases - Authority Gating: Refuses to run unless rollback is pre-granted in the repository's agent-authority list or explicitly requested by the user in the current turn. - Safe Git Revert: Reverts all commits between the target tag and HEAD on main using git revert, preserving full history with no force push. - Incident Tracking: Automatically creates a GitHub issue documenting the rollback, reverted changes, and follow-up action items. - Use Case: A broken release goes live on main. Run the rollback command to revert production to the previous tag (e.g., v1.2.3), file a tracking issue, and let Railway redeploy automatically from the updated main. ## Quick Start Ask the assistant to roll back production to the previous release tag, optionally specifying a target tag like v1.2.3.

Frequently Asked Questions about rollback

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

FAQPage Schema
How do I roll back a production release to a previous git tag?▼

Fetch tags from origin, identify the target tag (defaulting to the second-most-recent), then run git revert --no-commit from that tag to HEAD on main and push. This undoes the release while keeping full history, with no force push required.

How to revert a broken deploy without losing git history?▼

Use git revert instead of git reset or force push. Reverting the range between the previous tag and HEAD creates a new commit that undoes the changes, so the original commits remain in history for later investigation.

Can an AI agent roll back production without explicit approval?▼

No. The rollback requires either a pre-existing grant in the repository's agent-authority list or a direct user request in the current session. Without one of these, the procedure stops immediately and performs no git operations.

Does git revert trigger a production redeploy on Railway?▼

Yes. Once the revert commit is pushed to main, Railway automatically redeploys production from the updated branch, restoring the previous release without any manual deployment step.

What happens after a production rollback completes?▼

A GitHub tracking issue is created documenting the rollback, the reverted commits, and action items. The recommended next steps are investigating the root cause, fixing it on preprod, and cutting a new release.

Related Skills

Explore More Software Engineering Skills→
tubtrbtubtrb

release-tagging

Automate release tagging, merged-branch cleanup, and codex/next synchronization from main.

Community
Intermediate
styrene-labstyrene-lab
47

git

Standardize git workflow metadata across commits, branches, tags, and changelogs.

Official
Intermediate
wednesday-solutionswednesday-solutions
165

deploy-checklist

Verify pre-deploy prerequisites and post-deploy health for production deployments.

Official
Intermediate
GongYuanCaiJiGongYuanCaiJi

skill-rollback

Restores project files to a previous git checkpoint tag with confirmation and safety backup.

Community
Intermediate