skill-crewforth-crewforth-ci-pipeline · by Install
$ agentstack add skill-crewforth-crewforth-ci-pipeline ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-crewforth-crewforth-ci-pipeline) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
CI Pipeline
Trigger phrases: "ci", "pipeline", "github actions", "jenkins", "build pipeline", "pr gate", "pr check", "build fail", "build broke", "ci is failing", "workflow"
Stages (fail-fast — stop if it breaks early)
- Lint / format — style and static analysis
- Build — 0 warnings / 0 errors
- Test — unit + integration, coverage collected
- Quality —
sonarqube-checkquality gate - Security —
dependency-audit+security-scan(where applicable) - Artifact / packaging — (deployment is separate,
deploy)
Principles
- Deterministic: dependencies pinned, cache keyed correctly; no "it worked on my machine".
- Secret management: CI secret store; NO plaintext secrets in the repo/logs (overlaps with trace scan).
- PR gate: quality gate + tests must pass; a red build is not merged.
- Branch protection: direct push to main is disabled; PR + review required.
When a stage fails
- Fetch the failing job's log first —
gh run view --log-failed,glab ci trace,jenkins-cli console,
whichever this project's host provides — and quote the failing lines: a status icon names which job broke, never why. Log unreachable (no access, retention expired, the job never started) → report exactly that; never infer the cause.
- Reproduce with the exact command the pipeline runs, copied out of the CI config — same flags, same env, same
versions. Green locally is not a pass: the environment difference is now the defect, so take it to systematic-debugging.
- A re-run is not a fix. Re-running until it passes hides the cause; re-run only to establish that a failure is
intermittent — and an intermittent failure in this repo's own suite is a bug (testing), not a retry.
- Say which failures aren't yours. A required check owned by another change, or an external service that was
down, is reported out of scope with the job named — silence about it reads as a clean run.
DoD
- All stages green; PR gates enforced; no secret leakage; build reproducible.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: crewforth
- Source: crewforth/crewforth
- License: MIT
- Homepage: https://crewforth.com/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.