prowler-ci — Claude Code skill: what it does, how to install
prowler-ci is a Claude Code skill that helps investigate GitHub Actions failures and PR validation gates in the Prowler repository.
Apache-2.0 ★ 15,302 updated 2026-10-25
npx skills add prowler-cloud/prowler --skill prowler-ci -a claude-codeWhat prowler-ci does
This skill targets the internal CI setup of the Prowler repository. It maps automated checks under .github/workflows/, covering Conventional Commits PR title validation, merge conflict markers, label automation via CODEOWNERS, and changelog tracking.
It provides a concrete triage routine for failing Actions jobs, detailing path filters and common TruffleHog false alarms on synthetic credentials like AWS tokens or OpenAI keys in test suites. The skill operates using Read, Edit, Write, Glob, Grep, and Bash.
The changelog gate will fail PR builds unless a changelog entry exists under the matching <component>/changelog.d/ path or the no-changelog label is explicitly applied.
What it helps with
- diagnose failing GitHub Actions checks on a Prowler PR
- resolve Conventional Commits PR title validation errors
- fix TruffleHog secret scanning alerts triggered by test fixtures
- verify changelog fragment placement across repository components
Example prompts for the agent
- Help me figure out why the changelog gate failed on my PR
- Check why TruffleHog flagged my unit test credentials
- Inspect the path filters for UI workflows in .github/workflows
How to install prowler-ci
1Skills CLI (Vercel)
npx skills add prowler-cloud/prowler --skill prowler-ci -a claude-code2Manually: put the files in place
~/.claude/skills/prowler-ci/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/prowler-ci/
1Skills CLI (Vercel)
npx skills add prowler-cloud/prowler --skill prowler-ci -a codex2Manually: put the files in place
.agents/skills/prowler-ci/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add prowler-cloud/prowler --skill prowler-ci -a cursor2Manually: put the files in place
.cursor/skills/prowler-ci/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install prowler-cloud/prowler skills/prowler-ci2Manually: put the files in place
.github/skills/prowler-ci/SKILL.md1Skills CLI (Vercel)
npx skills add prowler-cloud/prowler --skill prowler-ci -a gemini-cli2Platform CLI
gemini skills install https://github.com/prowler-cloud/prowler --path skills/prowler-ciManually: put the files in place
.devin/skills/prowler-ci/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add prowler-cloud/prowler --skill prowler-ci -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about prowler-ci
How to install prowler-ci in Claude Code?
Run npx skills add prowler-cloud/prowler --skill prowler-ci -a claude-code. The file will be placed at ~/.claude/skills/prowler-ci/SKILL.md.
What does prowler-ci do?
It guides agents through Prowler-specific CI checks, path filters, secret scanning rules, and PR formatting requirements in GitHub Actions.
How does prowler-ci differ from prowler-pr?
The prowler-pr tool handles PR drafting and template completion, whereas prowler-ci focuses strictly on CI enforcement gates and failing workflow jobs.
Source text
SKILL.md · Apache-2.0
---
name: prowler-ci
description: >
Helps with Prowler repository CI and PR gates (GitHub Actions workflows).
Trigger: When investigating CI checks failing on a PR, PR title validation, changelog gate/no-changelog label,
conflict marker checks, secret scanning, CODEOWNERS/labeler automation, or anything under .github/workflows.
license: Apache-2.0
metadata:
author: prowler-cloud
version: "1.0"
scope: [root]
auto_invoke:
- "Inspect PR CI checks and gates (.github/workflows/*)"
- "Debug why a GitHub Actions job is failing"
- "Understand changelog gate and no-changelog label behavior"
- "Understand PR title conventional-commit validation"
- "Understand CODEOWNERS/labeler-based automation"
allowed-tools: Read, Edit, Write, Glob, Grep, Bash
---
## What this skill covers
Use this skill whenever you are:
- Reading or changing GitHub Actions workflows under `.github/workflows/`
- Explaining why a PR fails checks (title, changelog, conflict markers, secret scanning)
- Figuring out which workflows run for UI/API/SDK changes and why
- Diagnosing path-filtering behavior (why a workflow did/didn't run)
## Quick map (where to look)
- PR template: `.github/pull_request_template.md`
- PR title validation: `.github/workflows/conventional-commit.yml`
- Changelog gate: `.github/workflows/pr-check-changelog.yml` (requires a fragment under `<component>/changelog.d/`)
- Changelog compile (release time): `.github/workflows/compile-changelogs.yml`
- Conflict markers check: `.github/workflows/pr-conflict-checker.yml`
- Secret scanning: `.github/workflows/find-secrets.yml`
- Auto labels: `.github/workflows/labeler.yml` and `.github/labeler.yml`
- Review ownership: `.github/CODEOWNERS`
## Debug checklist (PR failing checks)
1. Identify which workflow/job is failing (name + file under `.github/workflows/`).
2. Check path filters: is the workflow supposed to run for your changed files?
3. If it's a title check: verify PR title matches Conventional Commits.
4. If it's changelog: verify a valid fragment exists under the right `<component>/changelog.d/` OR apply `no-changelog` label.
5. If it's conflict checker: remove `<<<<<<<`, `=======`, `>>>>>>>` markers.
6. If it's secrets (TruffleHog): see section below.
## TruffleHog Secret Scanning
TruffleHog scans for leaked secrets. Common false positives in test files:
**Patterns that trigger TruffleHog:**
- `sk-*T3BlbkFJ*` - OpenAI API keys
- `AKIA[A-Z0-9]{16}` - AWS Access Keys
- `ghp_*` / `gho_*` - GitHub tokens
- Base64-encoded strings that look like credentials
**Fix for test files:**
```python
# BAD - looks like real OpenAI key
api_key = "sk-test1234567890T3BlbkFJtest1234567890"
# GOOD - obviously fake
api_key = "sk-fake-test-key-for-unit-testing-only"
```
**If TruffleHog flags a real secret:**
1. Remove the secret from the code immediately
2. Rotate the credential (it's now in git history)
3. Consider using `.trufflehog-ignore` for known false positives (rarely needed)
## Notes
- Keep `prowler-pr` focused on *creating* PRs and filling the template.
- Use `prowler-ci` for *CI policies and gates* that apply to PRs.
© prowler-cloud · Apache-2.0 · prowler-cloud/prowler