Menu
Trigger deployment workflow for a feature. Invokes the SRE agent to handle deployment configuration, staging rollout, and production promotion.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Covers GitHub conventions for pull requests, issues, and comments including linking, language style, formatting, and callout syntax. Use when creating PRs, writing issues, or posting comments on Datum Cloud repositories.
Turn raw engineering notes, PR/issue links, commit messages, or a one-line feature description into a changelog entry for Datum Cloud's GitHub Discussions Changelog category: a benefit-led title plus a markdown body, drafted for users and ready to hand off for final capture and publish. Use when someone says "write a changelog entry", "announce this in the changelog", or "post this to the changelog discussions" — this is the community-facing changelog POST, not the Keep a Changelog release file (that lives in `gtm-templates`).
Provides templates for go-to-market communications including blog posts, changelogs, social media, and enablement briefs. Use when writing launch announcements or marketing content.
Create a new GitHub release. Verifies CI is green on the release commit and refreshes the third-party NOTICE file before tagging, determines the next version from the latest tag, summarizes merged PRs since the last release, drafts release notes in the established style, and publishes via gh release create. Works for any datum-cloud service repository.
Scan a project repository for strict AGPL-3.0 license compliance across Go, Rust, and JavaScript/React codebases. Use this skill whenever the user asks to check, audit, verify, or enforce AGPL license compliance on a project, repo, or codebase. Triggers on phrases like "check agpl compliance", "audit license headers", "is this project agpl compliant", "scan for license headers", "check my license files", "agpl audit", or any request involving ensuring a project is properly licensed under AGPL. Always use this skill — don't wing AGPL compliance checks from general knowledge.
Covers producing weekly operational reports for the Datum AI Edge. Use when asked for an ops review, traffic report, latency analysis, provisioning report, or edge performance summary. Guides metric queries, anomaly detection, and publishing to datum-cloud/engineering.
| name | deploy |
| description | Trigger deployment workflow for a feature. Invokes the SRE agent to handle deployment configuration, staging rollout, and production promotion. |
| tools | Read, Grep, Glob, Bash |
| model | sonnet |
| disable-model-invocation | true |
| context | fork |
| agent | general-purpose |
| argument-hint | <feature-id> [--promote|--hotfix] |
Orchestrate deployment through the pipeline with proper gates and validation.
/deploy <feature-id> Deploy feature to staging
/deploy <feature-id> --promote Promote from staging to production
/deploy <feature-id> --hotfix Abbreviated pipeline for urgent fixes
Feature ID: $ARGUMENTS
Before deployment:
/pipeline approve <id> review/deploy <feature-id>Validate prerequisites
Load deployment context
Invoke SRE agent
Update pipeline state
/deploy <feature-id> --promoteValidate staging success
Invoke SRE agent for production
Trigger document and announce stages
/deploy <feature-id> --hotfixAbbreviated path for urgent fixes:
## Deployment Context
**Feature**: {id} - {name}
**Target**: {staging|production}
**Review Status**: Approved on {date}
### Infrastructure Requirements
{From design artifact}
### Deployment Configuration
{From service profile and kustomize patterns}
### Rollout Strategy
- Canary: {percentage}
- Rollout duration: {time}
- Rollback trigger: {conditions}
### Monitoring
- Key metrics to watch
- Alert thresholds
- Dashboard links
Deployment initiated: feat-042-vm-snapshot-management
Target: staging
Review gate: Approved (2025-01-15)
[Invokes SRE agent]
Deployment configured.
Kustomize overlay: config/overlays/staging/feat-042/
FluxCD will reconcile within 5 minutes.
Monitor: /deploy status feat-042
Promote to production: /deploy feat-042 --promote
Review not approved:
Cannot deploy feat-042: review gate not approved.
Action: Run /pipeline approve feat-042 review after resolving findings.
Blocking findings exist:
Cannot deploy feat-042: 2 blocking findings unresolved.
Findings:
- missing-status-condition in pkg/apis/snapshots/v1alpha1/types.go
- unvalidated-input in pkg/registry/snapshot/strategy.go
Action: Resolve blocking findings and request re-review.
Tests failing:
Cannot deploy feat-042: CI tests failing.
Failed jobs: unit-tests, integration-tests
Action: Fix failing tests before deployment.