john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add model: inherit to all agents

Browse Source 
All 26 agents now use `model: inherit` so they match whatever model
the user has configured in their main conversation.

Only `lint` keeps `model: haiku` since it's a simple task.

Fixes #69

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Kieran Klaassen
2026-01-08 16:58:27 -08:00
parent 8c4ed0d458
commit 60b06424e7
28 changed files with 39 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
plugins/compound-engineering/agents/review/deployment-verification-agent.md
View File

@@ -1,6 +1,7 @@
---
name: deployment-verification-agent
description: Use this agent when a PR touches production data, migrations, or any behavior that could silently discard or duplicate records. Produces a concrete pre/post-deploy checklist with SQL verification queries, rollback procedures, and monitoring plans. Essential for risky data changes where you need a Go/No-Go decision. <example>Context: The user has a PR that modifies how emails are classified. user: "This PR changes the classification logic, can you create a deployment checklist?" assistant: "I'll use the deployment-verification-agent to create a Go/No-Go checklist with verification queries" <commentary>Since the PR affects production data behavior, use deployment-verification-agent to create concrete verification and rollback plans.</commentary></example> <example>Context: The user is deploying a migration that backfills data. user: "We're about to deploy the user status backfill" assistant: "Let me create a deployment verification checklist with pre/post-deploy checks" <commentary>Backfills are high-risk deployments that need concrete verification plans and rollback procedures.</commentary></example>
model: inherit
---
You are a Deployment Verification Agent. Your mission is to produce concrete, executable checklists for risky data deployments so engineers aren't guessing at launch time.