Git Workflow For Agents
Use when the user says 提交代码, 创建PR, 分支管理, 推到远程, commit, pull request, or any full-cycle git operation. Use when an agent has completed a feature and needs to commit, branch, and submit a PR following project conventions.
Agent Config Reference
Use when the user asks about config.yaml, CLAUDE.md, .cursor/rules, .codex config, agent setup, or skill installation. Use when the user says 配置agent, 安装skill, 迁移skill, or needs to understand platform-specific config differences across Hermes Agent, Claude Code, Codex CLI, and Cursor.
Planning Workflow
Use when the user asks to plan a project, roadmap, migration, refactor, release, investigation, multi-step implementation, risky change, or execution sequence and needs phases, dependencies, risks, validation gates, rollback, owners, or next actions.
Third Party Example Skill
Use this template when proposing a portable third-party skill with documented triggers, safe execution rules, examples, and verification evidence.
Cross Model Verification
Use when correctness matters more than speed, when working on high-stakes changes (production, security, data migration), or any time the first model's confidence feels unverified. Use when the user says "换个模型检查", "cross-model", "cross-validation", "second opinion", or "verify with another model".
Agent Security Guard
Use when about to execute risky operations that could cause irreversible damage, data loss, or security incidents. Use before rm, git push --force, database migrations, or production deploys. Use when reviewing code that touches API keys, credentials, or secrets. Use when the agent detects a pattern that could trigger a safety incident.
Skill Pipeline Orchestrator
Use when the user says "一键发布 skill", "走完整 pipeline", "发布这个 skill", or "skill 上线". Use when a new skill has passed review and is ready for release across one or more agent platforms.
Javascript Library Review
Review a JavaScript library for ESM compatibility, tests, public API changes, and release safety.
Skill Review Workflow
Use when the user says "审查这个skill""review skill""检查skill质量""这个skill写得怎么样". Use when a new SKILL.md is ready for pre-commit quality validation. Use when the user wants an objective quality score for an existing skill. Do NOT use during drafting stage, for reviewing non-SKILL.md code, or when the user asks how to use a skill (load and explain directly).
Requirements Clarifier
Use when the user gives a vague product, feature, bug, workflow, automation, refactor, migration, UI, API, integration, or policy request and needs scope, acceptance criteria, constraints, non-goals, assumptions, tradeoffs, open questions, or a build-ready contract.
Incident Retro Workflow
Use when the user asks to write, review, analyze, or improve an incident retro, postmortem, outage review, rollback review, timeline, impact summary, RCA, factor analysis, or corrective action plan after an incident, customer-impacting bug, deploy failure, data issue, or security-adjacent event.
Systematic Debugging
Use when the user asks to debug a failing test, runtime error, crash, flaky behavior, regression, misconfiguration, build failure, deployment failure, performance anomaly, or wrong output. Use when the task says "debug this", "why does this fail", "find root cause", "fix this bug", or "this used to work".
Release Notes Review
Review release-note behavior, regression evidence, and package readiness for this repository before a release.
Observability Workflow
Use when the user asks to add, design, review, or troubleshoot observability for a service, job, API, UI flow, pipeline, release, incident gap, or system and needs logs, metrics, traces, alerts, dashboards, SLOs, health checks, instrumentation, or runbooks.
Code Review Workflow
Use when the user asks to review code, a diff, pull request, patch, branch, implementation, or change set for bugs, regressions, security risks, data loss, concurrency issues, performance problems, maintainability risks, API contract drift, or missing tests. Do NOT use for reviewing SKILL.md quality; use skill-review-workflow for skill files.
Test Design Workflow
Use when the user asks to design, add, improve, or review tests for a feature, bug fix, API, CLI, UI, integration, migration, or security boundary. Use when test scope, success/failure/boundary cases, fixtures, mocks, automation level, or regression confidence must be chosen.
Python Library Review
Review changes to this Python library for API compatibility, behavioral regressions, missing tests, and release readiness.
Documentation Release Review
Review documentation releases for navigation, command accuracy, evidence links, and compatibility notes.
Skill Authoring Workflow
Use when the user says "写个 skill""创建 SKILL.md""这个流程变成 skill" or any new skill creation request. Use when the user provides a design document and asks to implement it as a skill. Do NOT use for small edits to existing skills or questions about skill format — answer those directly.