Skip to content
Back to skills

Merge Ready

ASecurity

Run all quality gates before merge — git hygiene, documentation completeness, code review, security audit, build, E2E, goal-backward verification, doc accuracy and UI/UX — then write the changelog entry.

  • 52 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 3, 2026
ai-agentsgobashgitsecuritydocumentation

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add Koroqe/claude-code-sdlc --skill merge-ready --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Merge Ready?

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

Security grade badge for Merge Ready
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/koroqe-merge-ready-e72df3f6/badge)](https://www.skillsdirectory.com/skills/koroqe-merge-ready-e72df3f6)

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
---
description: Run all quality gates before merge — git hygiene, documentation completeness, code review, security audit, build, E2E, goal-backward verification, doc accuracy and UI/UX — then write the changelog entry.
argument-hint: "[gate name to rerun]"
arguments: [gate]
allowed-tools: Read, Glob, Grep, Edit, Write, Bash, Agent, TodoWrite
---

# Command: Merge Ready (seeded CI fixture — trimmed mirror, NOT the real file)

> This is a trimmed, structurally-identical mirror of `skills/merge-ready/SKILL.md`'s "Post-Gate
> Instinct Capture" step, committed only so `scripts/ci/validate-instinct-discipline.js`'s falsify step
> has a tree to run against. This file carries the C3/FR-1.5a dedup clause UNCHANGED, and the Merge
> Reconciliation preamble below names all five classes (a)-(e) UNCHANGED — the deliberate defect in
> this fixture lives only in `agents/planner.md`, isolating the failure to the FR-6.2a assertion.

## Post-Gate Instinct Capture

**What fires it.** For every gate, across this entire `/merge-ready` run, whose Auto-Fix Protocol needed
at least one fix, capture exactly **one** instinct entry.

**FR-1.5a pre-capture dedup scan — MANDATORY, restated here because capture fires in this file too, not
only in `/implement-slice`.** Before minting a new `### <slug>` heading, scan every existing entry in
BOTH `## Prevention Rules` and `## Instincts Log` for one whose `Pattern:` and `Category:` both match
the pattern about to be captured. On a match, this is a recapture of that existing entry: update it in
place — this feature's slug is added to `(features: ...)` only if not already present there. Only when
no existing entry's `Pattern:` and `Category:` both match may a new slug be minted. Skipping this scan
is exactly what fragments occurrence counts across near-duplicate headings until nothing ever elevates
or retires.

## Consolidate Instincts

**Merge Reconciliation preamble — runs whenever the store shows merge artifacts** (a union merge
kept both branches' lines). Repair the five canonical classes, (e) first:

- **(a)** duplicate `Feature counter:` lines → keep the max. Safe direction: max undercounts by
  one per concurrent feature, so it only ever delays retirement, never triggers it early; a
  sum-of-deltas is not computable without the merge base and must never replace it.
- **(b)** duplicate `### <slug>` entries → union their `(features: ...)` lists; `Occurrences:` is
  the max of the two sides, floored at the union length; `Confidence:` is min(formula ceiling at
  the repaired count, max of the two confidences) — the formula is an upper bound, never an
  equality. Section placement: a cross-section duplicate repairs to a single entry, placed in
  `## Prevention Rules` only when the repaired count meets its category threshold, else
  `## Instincts Log`, deleting the other copy.
- **(c)** `Last confirmed at` above the counter → clamp it to the counter and recompute
  `Retires at`.
- **(d)** duplicate field lines within one entry → keep the repaired value, drop the duplicates.
- **(e)** duplicated section headings → fold each section's blocks into one before the other
  repair classes are applied — the store parser silently appends a duplicate heading's lines into
  the first, so the earlier repairs would mis-read an unfolded store.

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.