fabric-close

Merge completed task branches into main and run quality gates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/adaw/skills --skill fabric-close
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fabric-close
Source: https://github.com/adaw/skills/tree/main/fabric-close
Command: npx skills add https://github.com/adaw/skills --skill fabric-close

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of closing a development sprint, ensuring all completed work is merged, quality gates are passed, and the project state is accurately updated.

Core Features & Use Cases

  • Automated Merging: Safely squash-merges approved task branches into the main branch.
  • Quality Gates: Runs automated tests, linting, and formatting checks post-merge.
  • Backlog & State Updates: Updates task statuses to DONE, records merge commits, and regenerates backlog indices.
  • Reporting: Generates detailed per-task and sprint summary reports.
  • Use Case: At the end of a two-week sprint, run this Skill to automatically merge 15 completed tasks, verify their quality, and produce a report summarizing the sprint's progress and any carry-over items.

Quick Start

Use the fabric-close skill to finalize the current sprint by merging completed tasks and updating the backlog.

Frequently Asked Questions about fabric-close

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

FAQPage Schema
How do I automate sprint closure and merge multiple completed task branches safely?

Automating sprint closure involves safely squash-merging approved task branches into the main branch, running quality gates like automated tests and linting, and updating project state. This ensures deterministic and safe code integration without manual merge conflicts.

What is the best way to handle merge conflicts during end-of-sprint code integration?

Handling merge conflicts during end-of-sprint integration is managed by automating the merge process with deterministic checks. The system safely squash-merges approved branches and handles conflicts to ensure safe code integration before running quality gates.

Does automated sprint merging run security scans and linting checks post-merge?

Yes, automated sprint merging runs quality gates post-merge that include automated tests, linting, formatting checks, and security scans. This ensures that all integrated code meets project quality standards before the sprint is finalized.

Can I use this automated merge process for a two-week sprint with many completed tasks?

Yes, you can use this automated merge process for a two-week sprint with many tasks. It safely squash-merges approved branches, updates task statuses to DONE, and generates detailed per-task and sprint summary reports for progress tracking.

How do I generate sprint summary reports and update backlog indices after merging?

Generating sprint summary reports and updating backlog indices is handled automatically during sprint closure. The process records merge commits, regenerates backlog indices, and produces detailed reports summarizing sprint progress and any carry-over items.

Why should I automate quality gates instead of manually testing merged branches?

Automating quality gates ensures deterministic and safe code integration by consistently running tests, linting, and security scans post-merge. This eliminates manual testing errors, verifies code quality systematically, and accurately updates the project state for sprint closure.