TRIP-3-release

Automates versioning, changelogs, code review promotion, tagging, and fast-forward merging for releases.

614|89|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/PiLastDigit/TRIP-workflow --skill trip-3-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: TRIP-3-release
Source: https://github.com/PiLastDigit/TRIP-workflow/tree/main/skills/TRIP-3-release
Command: npx skills add https://github.com/PiLastDigit/TRIP-workflow --skill trip-3-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finalizing a feature release involves many error-prone manual steps: bumping versions, writing changelogs, promoting code reviews, updating docs, committing, tagging, merging, and pushing. This Skill orchestrates that entire release sequence so nothing is forgotten.

Core Features & Use Cases

  • Structured Release Pipeline: Runs a 13-step sequence covering SemVer version bumps, changelog files and tables, architecture doc updates, README sync, commit, tag, fast-forward merge, and push.
  • Code Review Promotion: Promotes the converged Codex code review state into a versioned CR document, with a fallback template when review was skipped.
  • Documentation Sync: Compares the plan's Documentation Impact against the actual git diff and applies factual corrections to affected docs before committing.
  • Use Case: After TRIP-2-implement converges with green tests and an approved review, invoke this Skill to produce release v1.4.0 with changelog, CR doc, tag, and a clean linear merge into main.

Quick Start

Run the TRIP-3-release skill with the plan file or feature label to finalize and ship the completed implementation as a tagged release.

Frequently Asked Questions about TRIP-3-release

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

FAQPage Schema
How do I release a completed feature with version bump and changelog?▼

Invoke the release skill with the plan file or feature label after implementation is confirmed. It updates the SemVer version, generates changelog files and table entries, commits, tags vx.y.z, fast-forward merges into the main branch, and optionally pushes.

How to promote an automated code review into release documentation?▼

The skill computes the review state file path via a key script, strips sentinel markers, fills version placeholders, and saves the result as a versioned CR document. If review was skipped, it writes a fallback CR from a template with an approved-with-observations verdict.

Can I run a release in a fresh session without the implementation context?▼

Yes, standalone invocation is supported. The skill first verifies lint, type-check, and tests are green, and checks the review state file exists; missing state is treated as the skipped-review fallback before any release step proceeds.

What happens if the fast-forward merge fails during release?▼

A failed --ff-only merge means the main branch moved during implementation. The skill instructs rebasing the feature branch onto main and retrying, and it never creates a merge commit, keeping a single linear history.

Does the release skill push to the remote automatically?▼

No. After committing, tagging, and merging, the skill asks for explicit user confirmation before running git push and git push --tags. You can decline and push manually later.