The tool stack developers share with their agents.

---
name: code-review
description: Reads the changed diff and reports correctness issues with file:line evidence.
---

# Code Review

1. Check the scope of the change with git diff.
2. Read the callers of every changed function.
3. For each finding, write down file:line and how to reproduce it.

---
name: release-checker
description: Reruns tests and lint before a release and decides pass or fail.
tools: Read, Grep, Bash
---

You are the independent grader of the release gate.
You do not fix code. You run the gate commands yourself
and report pass or fail from their output alone.

# Domain interview

Role: You are an analyst who organizes the requirements of the {{domain}} domain.
Input: {{meeting_notes}}

Output:
- Glossary (term · definition)
- Event flow (in the order things happen)
- Open questions

# Deployment rollback runbook

## Symptom
The 5xx rate goes above 1% right after a deploy.

## Actions
1. Find the previous release tag.
2. Check first whether the migrations can be rolled back.
3. After rolling back, confirm the health check passes.

name: saas-starter
inputs:
  - product_name
  - billing: [one_time, recurring]
steps:
  - scaffold: laravel-app
  - add: [auth, billing, admin]
  - verify: composer test