ci cd review

DevOps Community

Skill notes

Review focus

overbroad token permission unsafe shell missing gate cache poisoning non-reproducible build

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 grep or editor search before opening files. Use git, grep, and gh CLI. These are universally available and sufficient for all review tasks. Do not depend on tools beyond git, grep, cat, head, wc, and gh. Source: aydabd/github-bootstrap — distributed by TomeVault.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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 explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

## 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

1. Inspect changed files and diff hunks relevant to this skill.
2. Use repository-native tools when available.
3. Prefer exact evidence from changed code.
4. Emit findings using the shared JSONL finding contract.
5. Avoid style-only comments unless they create maintainability or correctness risk.

## Tooling hints

- Use `grep` or editor search before opening files.
- Use `git`, `grep`, and `gh` CLI. These are universally available and sufficient for all review tasks.
- Do not depend on tools beyond `git`, `grep`, `cat`, `head`, `wc`, and `gh`.

---
> Source: [aydabd/github-bootstrap](https://github.com/aydabd/github-bootstrap) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.