sdlc-merge-results

sdlc-merge-results is a command for Claude Code from SteveGJones/ai-first-sdlc-practices. It costs 0 tokens per session (2,408 once invoked), scanned A, original, MIT.

A command for combining code changes from several worker branches into one codebase. It checks the merged result and reports its final state.

In plain words
What is it for?
Use it after parallel implementation work to merge branches in order, resolve conflicts, run required checks, and summarize the result.
Why use it?
It reduces the risk of inconsistent merges, especially when workers changed shared files such as configuration or import lists.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions CLAUDE.md.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python tools/validation/local-validation.py --syntax 2>/dev/null || echo "SDLC validation not available".

Good fit Use it after parallel implementation work to merge branches in order, resolve conflicts, run required checks, and summarize the result.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/SteveGJones/ai-first-sdlc-practices
agentmods
npx agentmods add commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-results

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sdlc-merge-results

README.md
[![agentmods](https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-results/github.svg)](https://agentmods.dev/commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-results)
Your own site
<a href="https://agentmods.dev/commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-results"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-results/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sdlc-merge-results

Your own site · 80×15
<a href="https://agentmods.dev/commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-results"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/sdlc-merge-results.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,408 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02408
Opus 5 $0.00000 $0.01204
Sonnet 5 $0.00000 $0.00482
Haiku 4.5 $0.00000 $0.00241

Measured 11d ago against content hash f66b47c0324b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

sdlc-merge-results scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.archon/commands/sdlc-merge-results.md · 259 lines

How it starts

The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Merge Coordinator

Your Role

You are a merge coordinator responsible for integrating the results of parallel implementation agents into a single coherent codebase. Each agent worked on a separate task with non-overlapping file assignments, but their branches must be merged sequentially to ensure consistency. You merge, validate, and report the final state.

Context

You are merging worker branches after a parallel implementation phase. Each worker branch contains the commits from one implementation agent's task. The branches were created from the same base commit and should theoretically have non-overlapping file changes — but conflicts may still occur if:

  • The plan had an oversight and two tasks touched the same file
  • A shared configuration file (e.g., package.json, __init__.py, router registration) was modified by multiple tasks
  • Import statements or re-export files were updated by multiple tasks

Before starting, load project context:

  1. Read CLAUDE.md for project rules and validation requirements
  2. Identify the base branch (typically main or the feature branch the workers were created from)
  3. List all worker branches to merge

What To Do

Phase 1: Discover Worker Branches

List all branches that need to be merged. Worker branches follow a naming convention — detect it from the inputs or the branch list:

# List branches matching the expected pattern
git branch --list "worker-*" 2>/dev/null || git branch --list "task-*" 2>/dev/null
# Or list all branches that diverged from the base
git log --oneline --all --graph | head -40

For each worker branch, inspect what it contains:

git log base-branch..worker-branch --oneline
git diff base-branch..worker-branch --stat

Order the branches by their task dependency order (from the plan). Tasks with no dependencies should be merged first. Tasks that depend on other tasks should be merged after their dependencies.

Phase 2: Sequential Merge Strategy

Merge branches one at a time, validating after each merge. This sequential approach ensures each merge is clean before attempting the next.

Read the full file on GitHub · 259 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 259 lines · 0 tokens per session scan A f66b47c0324b

Subscribe to this mod's changes

sdlc-merge-results is a command published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,408 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.