Menü
Infiquetra deployment state and tag-promotion guidance. Use for /deploy, /deploy-status, /deploy-notes, /deploy-hotfix, rollback planning, hotfix promotion, and deployment evidence.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Route proposed Team Mimir profile behavior changes to target-owned Hermes dialogue.
Native Antigravity multi-agent consensus workflow. Spawns parallel workers and reviewers with a 0-10 scoring loop and automatic fix routing.
Deep-dive one chosen Infiquetra idea into a right-sized requirements document before planning.
Run a structured Infiquetra code-quality review at the work-to-PR boundary. Reads the merge-base diff, runs a built-vs-planned audit plus judgment-selected review lenses, validates findings, writes a durable review artifact, appends to the work-thread saga, and routes — without mutating code. Triggers on "review this PR", "code review", "check my diff", "pre-PR review", or a /work hand-in before shipping.
Review Infiquetra plans, requirements, and SDLC documents for implementation readiness.
Route durable Infiquetra lifecycle artifacts into mission-control prepared issue drafts.
| name | deploy-state |
| description | Infiquetra deployment state and tag-promotion guidance. Use for /deploy, /deploy-status, /deploy-notes, /deploy-hotfix, rollback planning, hotfix promotion, and deployment evidence. |
Use this skill for Infiquetra repository deployment work. It is intentionally separate from
saga because deployment mutation deserves a hard boundary.
.github/workflows/.github.com/infiquetra/*, stop before mutation.Infiquetra tag-promotion environments:
| Environment | Tag Prefix | Purpose |
|---|---|---|
nonprod | nonprod-v | First automated integration environment. |
staging | staging-v | Candidate validation before production. |
production | production-v | Customer-facing production promotion. |
Rollback tags use rollback-<environment>-v<version>. Hotfix tags use the same environment
prefix with an explicit hotfix version such as production-v1.2.3.1.
.github/workflows/ and classify whether tag-promotion is full, partial, or absent.unhealthy-v<version> exists unless the user explicitly chooses
an audited override after manual verification.Durable evidence belongs in the repository:
mission-control when an SDLC issue exists.Runtime scratch belongs under ignored local state such as .gemini/saga/ or a
deployment-specific cache. Do not commit raw API responses or validator JSON.
plugins/deploy/scripts/mint_tag.py: build and optionally push policy tags.plugins/deploy/scripts/query_deployments.py: show status and drift.plugins/deploy/scripts/preview_release_notes.py: summarize candidate changes.