deliver

Merge feature branches, tag releases, and clean up sprint deliveries.

4|1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/nicolasguelfi/gensem --skill deliver-nicolasguelfi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deliver
Source: https://github.com/nicolasguelfi/gensem/tree/main/gse-one/plugin/skills/deliver
Command: npx skills add https://github.com/nicolasguelfi/gensem --skill deliver-nicolasguelfi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivers sprint-ready software by coordinating feature-branch merging, release tagging, and post-delivery cleanup to ensure a repeatable, auditable delivery process.

Core Features & Use Cases

  • Pre-flight checks: verifies sprint backlog readiness, test evidence status, and absence of uncommitted changes before delivery.
  • Merge strategy flexibility: supports squash, merge, or rebase options to control history.
  • Release tagging and backups: assigns semantic versioning tags when configured and creates backup tags to enable rollback.
  • Cleanup and traceability: deletes merged branches, removes worktrees, updates backlog statuses, and generates release notes.
  • Release automation: can generate a detailed sprint release note and refresh dashboards post-delivery.

Quick Start

Run the deliver command when your sprint tasks are ready for deployment to merge, tag, and clean up the integration branch.

Frequently Asked Questions about deliver

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

FAQPage Schema
How do I automate sprint release merging and git tagging for feature branches?

Automate sprint release merging and git tagging by running a delivery command that merges feature branches, applies semantic versioning tags, and cleans up worktrees. It reads config.yaml and backlog.yaml to enforce test evidence guardrails before executing the merge.

What is the best way to enforce test evidence checks before merging a git release branch?

The best way to enforce test evidence checks before merging a git release branch is using pre-flight guardrails that verify sprint backlog readiness and test status. The delivery process blocks merging if test evidence is absent or uncommitted changes exist in the repository.

Can I use squash, merge, or rebase strategies for sprint feature branch delivery?

You can use squash, merge, or rebase strategies for sprint feature branch delivery. The process supports flexible merge strategy selection driven by configuration rules, allowing you to control commit history while applying backup tags for rollback safety.

How does sprint release cleanup work after merging feature branches?

Sprint release cleanup works by deleting merged branches, removing git worktrees, and updating backlog task statuses to reflect completion. It also generates detailed release notes to maintain traceability after the delivery process finishes.

Does the delivery process support automated semantic versioning and rollback tags?

The delivery process supports automated semantic versioning and rollback backup tags based on config-driven rules. It assigns version tags during the release and creates backup tags simultaneously, enabling safe rollback if the deployed sprint features fail.