How do I install the Sdlc Merge Queue skill?

Run npx skillmds@latest add jlave-dev/sdlc-merge-queue in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sdlc Merge Queue safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sdlc Merge Queue?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sdlc Merge Queue free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sdlc Merge Queue?

jlave-dev (@jlave-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sdlc Merge Queue by jlave-dev — Agent Skill

Name: Sdlc Merge Queue
Author: jlave-dev

Sdlc Merge Queue

Use when Agent SDLC PRs are approved and marked merge-ready, and an orchestrator should merge one or more PRs in dependency order while verifying current-head checks, issue Agent State, review verdicts, and handing conflicts or failed checks back to workers instead of fixing inline.

jlave-dev a9c6c2a 2 files · 2.0 KB Updated Sep 17, 2026

File contents

SDLC Merge Queue

Merge approved Agent SDLC PRs without doing implementation fixes in the orchestrator lane.

Workflow

Refresh live state:
- git status --short --branch
- git fetch origin --prune
- gh pr view <number> --json number,title,url,state,isDraft,headRefOid,mergeStateStatus,statusCheckRollup,reviewDecision
- linked issue ## Agent State
Confirm the issue says Status: merge_ready, has a PR, has current-head evidence, and records an approved review or explicit accepted needs_human verdict.
Inspect the actual PR diff before merging:
- gh pr diff <number> --name-only
- gh pr diff <number> --patch for the highest-risk touched files.
Confirm required checks are green on the current PR head. Pending checks may be polled; failed checks stop the queue.
Mark ready if the PR is still draft and all gates pass.
Merge with the repo's merge helper when one exists; otherwise use the repo's normal GitHub merge path.
Verify the PR merged and the linked issue closed or explain why it remains open.

Hand Back Instead Of Fixing

For failed checks, send the failure links and a concise fix request to the original worker thread.
For conflicts or stale branches, ask the worker to rebase/merge onto the required base, resolve only conflict files, verify, push, refresh evidence, and rerun review.
If the worker thread is unavailable, update the issue as blocked and ask the user whether to spawn a replacement worker.

Frequently asked questions