Fix YAML parsing errors in agent description fields (#74)
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
---
|
||||
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>
|
||||
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
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user