ci-cd-review
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- DevOps
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: ci-cd-review
description: CI/CD review for workflows, artifact safety, caching, deployment gates, secrets, permissions, an…
category: devops
runtime: no special runtime
---
# ci-cd-review output preview
## PART A: Task fit
- Use case: CI/CD review for workflows, artifact safety, caching, deployment gates, secrets, permissions, and reproducibility. Use when this capability is needed. <!-- tomevault:4.0:skill_md:2026-05-22 --> runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Purpose / Review focus / Method” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “CI/CD review for workflows, artifact safety, caching, deployment gates, secrets, permissions, and reproducibility. Use when this capability is needed. <!-- tomevault:4.0:skill_md:2026-05-22 --> runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Purpose / Review focus / Method” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Purpose / Review focus / Method”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: ci-cd-review
description: CI/CD review for workflows, artifact safety, caching, deployment gates, secrets, permissions, an…
category: devops
source: tomevault-io/skills-registry
---
# ci-cd-review
## When to use
- CI/CD review for workflows, artifact safety, caching, deployment gates, secrets, permissions, and reproducibility. Use…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Purpose / Review focus / Method” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "ci-cd-review" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Purpose / Review focus / Method
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Purpose
CI/CD review for workflows, artifact safety, caching, deployment gates, secrets, permissions, and reproducibility.
Review focus
- overbroad token permission
- unsafe shell
- missing gate
- cache poisoning
- non-reproducible build
- artifact leak
Method
- Inspect changed files and diff hunks relevant to this skill.
- Use repository-native tools when available.
- Prefer exact evidence from changed code.
- Emit findings using the shared JSONL finding contract.
- Avoid style-only comments unless they create maintainability or correctness risk.
Tooling hints
- Use
grepor editor search before opening files. - Use
git,grep, andghCLI. These are universally available and sufficient for all review tasks. - Do not depend on tools beyond
git,grep,cat,head,wc, andgh.
Source: aydabd/github-bootstrap — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review