القائمة
Use when changing Maestro runtime, hosted runner, event contracts, migration packaging, or internal-to-public mirror behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Triage production incidents by building a timeline, scoping blast radius, identifying mitigations, and preserving evidence. Use when the user asks about an outage, regression, alert, Sentry issue, or incident follow-up.
Install automated Maestro code review in a GitHub repository's CI — add a pull_request workflow that runs `maestro exec` and posts a merge-readiness review as a PR comment. Use when the user wants to set up automated PR review, wire Maestro into CI/CD, or "install code review".
Correctness-first, depth-first security audit of a single repository using STRIDE, OWASP Top 10, the OWASP LLM Top 10, and supply-chain analysis. Use when the user asks for a security review, a vulnerability audit, a threat model, or a pre-release security pass.
Review GitHub pull requests for correctness, regressions, missing tests, and merge readiness. Use when the user asks for PR review, review feedback, or a pre-merge risk pass.
Verify release readiness and post-release health from PRs, CI, tags, deploy evidence, rollback notes, and operator artifacts. Use when the user asks whether a release can ship, has shipped, or is safe to promote.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
| name | maestro-mirror-and-runtime-pr |
| description | Use when changing Maestro runtime, hosted runner, event contracts, migration packaging, or internal-to-public mirror behavior. |
Use this workflow for Maestro changes that may affect the public mirror, Platform integration, hosted runtime, or release packaging.
gh pr list --repo evalops/maestro-internal --limit 20gh pr list --repo evalops/maestro --limit 20evalops/maestro-internal unless explicitly asked to edit the public mirror.AGENTS.md, root README.md, and the package README files before making broad changes.evalops/maestro for normal mirrored code changes; let the mirror/release automation handle public sync.Use narrow checks for the touched surface, then broaden if the change crosses package boundaries:
npm run check
cargo test --workspace --locked
Rust runtime changes:
cargo check -p maestro-tui
cargo check -p maestro-control-plane
Protocol or packaging changes:
cargo test --workspace --locked
npm run release:check