Menu
Invoke code review on the current branch or a specific feature. Runs the code-reviewer agent with appropriate context from the pipeline.
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 | review |
| description | Invoke code review on the current branch or a specific feature. Runs the code-reviewer agent with appropriate context from the pipeline. |
| tools | Read, Grep, Glob, Bash |
| model | sonnet |
| disable-model-invocation | true |
| context | fork |
| agent | general-purpose |
| argument-hint | [feature-id|--diff <base>] |
Quick-start code review with automatic context loading from the pipeline.
/review Review current branch changes
/review <feature-id> Review changes for a specific feature
/review --diff <base> Review diff against a specific base branch
Feature ID or diff options: $ARGUMENTS
/review (current branch)Detect context
git branch --show-current to get branch namefeat-042-vm-snapshots)Load pipeline context (if feature ID found)
.claude/pipeline/designs/{id}.md.claude/pipeline/specs/{id}.md.claude/service-profile.mdInvoke code-reviewer agent
.claude/review-findings.jsonl/review <feature-id>Load pipeline context
Determine review scope
Invoke code-reviewer agent
/review --diff <base>Generate diff
git diff <base>...HEADInvoke code-reviewer agent
When invoking code-reviewer, provide this context:
## Review Context
**Feature**: {id} - {name}
**Branch**: {branch-name}
**Design**: .claude/pipeline/designs/{id}.md
**Spec**: .claude/pipeline/specs/{id}.md
### Expected Changes (from design)
{Summary of expected changes from design artifact}
### Actual Changes
{Git diff or changed file list}
### Platform Integrations Expected
{From service profile: quota, insights, telemetry, activity requirements}
Review started for: feat-042-vm-snapshot-management
Branch: feat-042-vm-snapshots
Design context loaded: .claude/pipeline/designs/feat-042-vm-snapshot-management.md
[Invokes code-reviewer agent]
Review complete.
Findings logged to: .claude/review-findings.jsonl
Summary:
- Blocking: 0
- Warning: 2
- Nit: 5
To approve: /pipeline approve feat-042 review
After review completes:
/pipeline approve <id> reviewNo changes to review:
No changes detected on current branch.
Use /review --diff <base> to specify a comparison base.
Feature not found:
Feature feat-042 not found in pipeline.
Proceeding with general code review (no design context).