Skip to content
Back to skills

Git Review Pipeline

ASecurity

Execute an automatic-delivery or user-selected SDD exact-head review round with headless parallel reviewers, exact-head CI when planned, canonical triage, and separate FIX.

  • 25 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 18, 2026
ai-agentsrustbashgit

Works with

  • terminal

Security analysis

A100/100

Scanned October 18, 2026

npx -y skills add nikolanovoselec/codeflare --skill git-review-pipeline --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Git Review Pipeline?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Git Review Pipeline
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nikolanovoselec-git-review-pipeline/badge)](https://www.skillsdirectory.com/skills/nikolanovoselec-git-review-pipeline)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: git-review-pipeline
description: Execute an automatic-delivery or user-selected SDD exact-head review round with headless parallel reviewers, exact-head CI when planned, canonical triage, and separate FIX.
version: 2.0.0
---

# SDD Review Pipeline

Use this skill for a hook-emitted automatic delivery plan or after the user selects `Launch review` from a non-delivery marker-miss question.

## Eligibility and consent

Advanced SDD projects are eligible when the active normal checkout exactly matches an open PR targeting `main`, `master`, or `develop`. SessionStart, clone, switch, branch checkout, PR checkout, pull, checked-out-branch push, checked-out-branch PR creation, and checked-out-branch PR reopen may expose that identity.

A valid user-scoped marker stays silent. Successful checked-out-branch push, PR creation, and PR reopen automatically emit one review-and-CI plan. Other misses offer exactly `Mark review complete` and `Launch review`; never choose for the user. Cancellation writes nothing.

Fetch, inspection, local mutation, merge, detached or path checkout, tag, unrelated-ref push, failed commands, child sessions, GitHub failure, and unsynchronized heads remain inert.

## Fresh plan and headless transport

Every automatic or selected launch uses current GitHub and repository facts. A retained same-PR ancestor selects an incremental range; otherwise the planner uses the full protected-base diff. Prior lane output, CI evidence, and consent are discarded after interruption.

Run every emitted `run-review-lane.sh` Bash command unchanged and in the background. Issue all required lane calls together. Each command carries its validated `--range` or `--base`, PR number, and deterministic `/tmp/codeflare-pr-...` output. The runner trusts caller scope and never reads review state.

When the directive includes CI, launch its exact background `ci-monitor` Agent immediately after reviewer calls. Do not wait first. End the turn after the final launch. Never poll or duplicate in-flight work.

## Joint triage and FIX

Wait for every required headless lane and required exact-head CI result. Publish one tool-free canonical table after terminal evidence:

| FINDING | VALIDITY | PROPOSED FIX | PROPORTIONALITY | MINIMAL DECISION |
|---|---|---|---|---|

CI failure or timeout requires FINDING `Exact-head CI` and PROPOSED FIX `CI_RESULT failure` or `CI_RESULT timeout`. A clean successful round may keep the table empty. Judge findings independently from proposed fixes and reject unsupported or oversized changes.

Make no mutation in the triage turn. The Stop hook inspects only transcript bytes after the current SessionStart offset, revalidates the exact identity, writes completion, and emits the separate FIX reminder. Root applies accepted changes only in FIX.

Stopped or failed work advances the ephemeral offset and emits no missing-work directive. Reload clears active coordination. The next delivery emits a fresh plan; the next non-delivery exposure asks again and replans. Never read, write, migrate, or delete legacy `.git/sdd-review-*` state.

## Branch protection

The expected route is `feature -> develop -> main`. Protect `main` with PR and required-CI checks. Ask before changing repository protection.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.