work-integrate

Merge completed user story or work item branches after quality gates and progress verification.

Updated May 8, 2026
One-click install
npx skills add https://github.com/juanca202/sdd-devkit --skill work-integrate-juanca202
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-integrate
Source: https://github.com/juanca202/sdd-devkit/tree/main/skills/work-integrate
Command: npx skills add https://github.com/juanca202/sdd-devkit --skill work-integrate-juanca202

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Closing out a finished user story or maintenance task involves many error-prone manual steps: checking that every task is marked Done, running quality gates, resolving the correct base branch, and performing a clean merge without leaking audit artifacts. This Skill automates that entire closing workflow so nothing is merged prematurely or left half-integrated. ## Core Features & Use Cases - Pre-merge validation: Verifies the branch naming convention (feature/US-XXX, fix/WI-XXX, test/FT-XXX), a clean working tree (auto-invoking git-commit for pending changes), and that every unit in progress.md is in Done status before any git operation. - Quality gate orchestration: Runs quality-check, code-review, and coverage-verify in order, honoring per-gate enablement policies, and blocks the merge on any REJECTED or INCOMPLETE verdict. - Controlled merge and archiving: Performs a three-step --no-ff merge that strips gate reports from the base branch, then optionally archives the work folder to docs/specs/archived/ based on the archiveMode policy. - Use Case: After finishing all tasks of US-042 on branch feature/US-042-exportacion-csv, ask the agent to close the work; it validates progress, runs the gates, merges into develop, and archives the spec folder after your confirmation. ## Quick Start Ask the agent to close and integrate the work on the current branch, for example by saying: merge and close the user story on this branch once all quality gates pass.

Frequently Asked Questions about work-integrate

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

FAQPage Schema
How do I merge a user story branch after all tasks are done?▼

Run the work-integrate skill from the feature branch. It verifies every task in progress.md is Done, runs the quality-check, code-review, and coverage-verify gates, then performs a --no-ff merge into the base branch resolved from reflog or your confirmation.

What happens if some tasks are not Done when I try to merge?▼

The merge is blocked and no git operation runs. The skill lists every unit with its current status (Pending, In Progress) so you can complete the work in work-implement or correct progress.md before retrying.

Does work-integrate push the merge or delete the branch?▼

No. The merge is strictly local: it never pushes, never deletes branches, and never creates pull requests. Publishing to the remote and branch cleanup remain manual steps under your control.

Can I use work-integrate together with a pull request workflow?▼

They are alternative integration routes, not sequential phases. If the base branch has a pull_request commit policy, the skill stops and offers pr-create instead. Running both on the same work would integrate it twice.

Why does the merge commit exclude the quality-check and code-review reports?▼

Those audit reports are snapshots of the work branch and would falsely claim a verdict on the base branch. The skill removes them from the index between --no-commit and the merge commit, while keeping them in the work branch as evidence.

When does work-integrate archive the specification folder?▼

Only after the merge succeeds, all gates pass, and the work is a US or WI on a functional branch. With archiveMode set to ask it requests your confirmation first; test/ branches and already-archived work are never archived.