Enterprise Release Engineering

Use when the user asks about integration hell, long-lived branches across teams, trunk-based development at scale, release trains, branch by abstraction, dark launches or CODEOWNERS. Produces a multi- team integration and release model. Not for single-team git basics (use dev-loop-git-workflow) or canary rollouts (use devops-progressive-delivery).

45 stars 6 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill enterprise-release-engineering
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/enterprise/release-engineering ~/.claude/skills/enterprise-release-engineering

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Release Engineering & Multi-Team Integration

## Purpose
Keep many teams integrating continuously into a shared mainline so that integration cost stays small and releases are routine. Separate deployment (code in production) from release (users see it), and make risky changes incrementally rather than on long-lived branches.

## Agent Protocol

### Trigger
"integration hell", "merge conflicts", "long-lived branch", "trunk-based", "release train", "branch by abstraction", "feature toggle", "dark launch", "flyway version conflict", "expand/contract", "codeowners", "gitflow vs trunk".

### Input Context
- Number of teams/repos, current branching model, release cadence.
- Deployment model (continuous deploy, scheduled, versioned/on-prem).
- Database migration tool (Flyway, Liquibase, Prisma, Alembic, Rails).

### Output Artifact
Integration and release strategy with concrete repo/CI rules.

### Response Format
```
Current pain: {symptom}
Branching: {trunk-based|short-lived feature branches|release branches} (max branch age {N days})
Incomplete work hidden by: {flags|branch by abstraction|dark launch}
Release cadence: {continuous|train every N weeks}
Migrations: {expand/contract, versioning scheme}
Ownership: {CODEOWNERS paths}
```

## Branching Model Decision

| Context | Model |
|---------|-------|
| SaaS with continuous delivery | Trunk-based; short-lived branches (<1–2 days) merged via PR with required CI |
Read the full skill on GitHub

Details

Skill name
enterprise-release-engineering
Path
skills/enterprise/release-engineering/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Enterprise Release Engineering skill do?

Use when the user asks about integration hell, long-lived branches across teams, trunk-based development at scale, release trains, branch by abstraction, dark launches or CODEOWNERS. Produces a multi- team integration and release model. Not for single-team git basics (use dev-loop-git-workflow) or canary rollouts (use devops-progressive-delivery).

How do I install the Enterprise Release Engineering skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill enterprise-release-engineering. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Enterprise Release Engineering popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Orchestrate

23

nathanonn/agent-skills

Run the main Claude Code session as an orchestrator for a non-trivial, multi-step request in a git repo. Builds a task list, routes each task to a sub-agent with an explicit model and effort (sonnet, opus or haiku; fable only with the user's say-so), runs up to 5 read-only agents at once and file-editing agents one at a time in the main checkout (git worktrees only when the user asks for them), then verifies and commits each checkpoint locally on the current branch, never pushing unless asked. Use it when the user asks to orchestrate, delegate, use sub-agents, fan out, or work in parallel, inc

Git & Code Review

Ecmwf Weather Feedback

23

ecmwf/ecmwf-weather-skills

Turns what a task taught about the ECMWF weather skills into one anonymised, privacy-scanned issue for ecmwf/ecmwf-weather-skills — load this skill first, before running any `gh issue` command or filing, drafting or reporting any issue about these skills. The issue goes to GitHub, or to ECMWF JIRA project AS with the user's own token, or is given as text to paste — shown in full and filed only after an explicit yes, file it. Use when the user wants to send feedback about the ECMWF weather skills, report a problem with a skill or its instructions, suggest an improvement, file an issue for ecmwf

Git & Code Review

Git Commit Helper

33

dvcrn/openclaw-skills-marketplace

Generate standardized git commit messages following Conventional Commits format. Use this skill when the user asks to commit code, write a commit message, or create a git commit. Enforces team conventions for type prefixes, scope naming, message length, and breaking change documentation.

Git & Code Review17

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.