coding-loop-finaliser

Validate chain artifacts and repository state before creating PRs or MRs.

6|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/luispabon/ai-bits-and-pieces --skill coding-loop-finaliser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-loop-finaliser
Source: https://github.com/luispabon/ai-bits-and-pieces/tree/main/skills/coding_loop/finaliser
Command: npx skills add https://github.com/luispabon/ai-bits-and-pieces --skill coding-loop-finaliser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of inconsistent repository closeout by enforcing a standardized, multi-phase validation process for coding loops, ensuring that all work is reviewed, verified, and safely merged.

Core Features & Use Cases

  • Chain Validation: Automatically verifies that the coding loop reached a finaliser-ready state by checking required artifacts like overview.md, execution.md, and review.md.
  • Repository Hygiene: Inspects for leftover worktrees, temporary branches, and uncommitted changes, providing a safe resolution path before finalization.
  • Automated PR/MR Creation: Integrates with GitHub, GitLab, and Azure DevOps to push branches and create pull or merge requests using standardized, synthesized summaries.

Quick Start

Use the coding-loop-finaliser skill to close out the current project by providing the path to your planning folder.

Frequently Asked Questions about coding-loop-finaliser

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

FAQPage Schema
How do I automate pull request creation and repository cleanup when finalizing a coding loop?

Automating pull request creation during coding loop finalization involves validating chain artifacts and checking repository state before pushing branches and generating standardized PR summaries. This skill enforces that process across GitHub, GitLab, and Azure DevOps.

What is the best way to ensure repository hygiene before creating a merge request?

Ensuring repository hygiene before creating a merge request requires inspecting the repository for leftover worktrees, temporary branches, and uncommitted changes. This skill identifies these leftover states and provides a safe resolution path before finalization.

Does this coding loop finalisation workflow support GitLab and Azure DevOps?

Yes, coding loop finalisation supports GitLab and Azure DevOps alongside GitHub. The workflow integrates with all three platforms to push branches and create pull or merge requests using synthesized, standardized documentation of implementation and review findings.

How do I validate required artifacts like overview.md and review.md before finalizing a branch?

Validating required artifacts before finalizing a branch requires verifying that the coding loop reached a finaliser-ready state. This skill automatically checks for necessary chain artifacts like overview.md, execution.md, and review.md to ensure all work is reviewed.

What happens if there are uncommitted changes or temporary branches when closing out a coding loop?

If uncommitted changes or temporary branches exist when closing out a coding loop, the repository hygiene inspection identifies them. The skill then provides a safe resolution path to clean up leftover state before proceeding with PR creation.

Can I use this skill to generate standardized summaries for pull requests across different platforms?

Yes, you can use this skill to generate standardized summaries for pull requests. It synthesizes documentation from implementation and review findings to create consistent PR or MR descriptions across GitHub, GitLab, and Azure DevOps.