skills.rest
notque
notqueCOMMUNITY
Explore all skills by this author →
GitHub

feature-release

Merge validated feature branches into main via pull requests with optional release tagging.

415|44|Updated Mar 18, 2026
Search Tags:#git#workflow#validation#pr#feature-release
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill feature-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-release
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/feature-release
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill feature-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the release workflow by merging a validated feature into the main branch via a pull request, optionally tagging the release, and cleaning up the feature worktree after merge.

Core Features & Use Cases

  • Create pull requests from feature branches and link to design decisions and validation artifacts.
  • Generate PR descriptions from design, plan, and validation artifacts to capture decisions and evidence.
  • Clean up worktrees and archive completed feature state after a successful merge.
  • Enforce gating: do not release without successful validation; always merge via PR.

Quick Start

Initiate the feature-release process after validation to merge the feature into main via PR and optionally tag the release.

Frequently Asked Questions about feature-release

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

FAQPage Schema
How do I merge a validated feature branch into main via a pull request?▼

To merge a validated feature branch into main, this Skill automates creating a pull request, enforces validation gating, and optionally tags the release before cleaning up the feature worktree.

Can I generate a pull request description from design and validation artifacts?▼

Yes, you can generate PR descriptions automatically from design, plan, and validation artifacts to capture development decisions and evidence directly within the pull request.

Does the feature release workflow enforce validation before merging?▼

The feature release workflow enforces strict gating to ensure validation passes successfully before allowing a merge to main, preventing unvalidated code from being released.

What is the best way to clean up git worktrees after merging a feature?▼

The best way to clean up git worktrees after a merge is to automate the cleanup process, which archives the completed feature state and removes the worktree following a successful pull request.

How do I tag a release automatically when merging a feature branch?▼

You can tag a release automatically during the merge process by enabling optional release tagging, which applies conventional commits and tags the main branch after the pull request succeeds.

What happens if feature validation fails before a release?▼

If feature validation fails before a release, the gating mechanism halts the pull request merge to main, ensuring only validated features are merged and tagged.

Related Skills

Explore More Software Engineering Skills→
cpfcoachingcpfcoaching

Finishing a Development Branch

Merge, create pull requests, or discard feature branches with test verification.

Community
Intermediate
lehalpaullehalpaul

merge-pr

Merge GitHub pull requests via squash and clean up worktrees.

Community
Advanced
mindspore-aimindspore-ai
258

akg-pr

Generate AKG PR descriptions and validation artifacts from branch diffs.

Official
Intermediate
SufficientDaikonSufficientDaikon
8

finishing-a-development-branch

Complete Git development branches with merge, PR, deferral, or discard options.

Community
Intermediate