prowler-ci
Automates and debugs GitHub Actions CI workflows and PR gate policies for Prowler.
Install
mkdir -p .claude/skills/prowler-ci && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7400" && unzip -o skill.zip -d .claude/skills/prowler-ci && rm skill.zipInstalls to .claude/skills/prowler-ci
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Read or change GitHub Actions workflows
- →Explain why a PR fails checks
- →Figure out which workflows run for UI/API/SDK changes
- →Diagnose path-filtering behavior
- →Check PR title validation against Conventional Commits
- →Verify changelog fragments or `no-changelog` label
How it works
This skill analyzes GitHub Actions workflows and PR details to explain CI check failures, diagnose path-filtering, and validate PR titles and changelog requirements.
Inputs & outputs
When to use prowler-ci
- →Debug failing GitHub Actions CI jobs
- →Validate PR titles against conventional commits
- →Enforce changelog requirements on pull requests
- →Configure CODEOWNERS and labeler automation
About this skill
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.ymland.github/labeler.yml - Review ownership:
.github/CODEOWNERS
Debug checklist (PR failing checks)
- Identify which workflow/job is failing (name + file under
.github/workflows/). - Check path filters: is the workflow supposed to run for your changed files?
- If it's a title check: verify PR title matches Conventional Commits.
- If it's changelog: verify a valid fragment exists under the right
<component>/changelog.d/OR applyno-changeloglabel. - If it's conflict checker: remove
<<<<<<<,=======,>>>>>>>markers. - 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 keysAKIA[A-Z0-9]{16}- AWS Access Keysghp_*/gho_*- GitHub tokens- Base64-encoded strings that look like credentials
Fix for test files:
# 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:
- Remove the secret from the code immediately
- Rotate the credential (it's now in git history)
- Consider using
.trufflehog-ignorefor known false positives (rarely needed)
Notes
- Keep
prowler-prfocused on creating PRs and filling the template. - Use
prowler-cifor CI policies and gates that apply to PRs.
How it compares
This skill provides targeted debugging and validation for GitHub Actions CI/CD, unlike general CI troubleshooting.
Compared to similar skills
prowler-ci side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| prowler-ci (this skill) | 1 | 6mo | No flags | Intermediate |
| github-actions-templates | 7 | 3mo | No flags | Intermediate |
| security-automation | 1 | 6mo | Review | Advanced |
| bazel-build-optimization | 14 | 2mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by prowler-cloud
View all by prowler-cloud →You might also like
github-actions-templates
wshobson
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
security-automation
Ed1s0nZ
安全自动化的专业技能和方法论
bazel-build-optimization
wshobson
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
linux-production-shell-scripts
davila7
This skill should be used when the user asks to "create bash scripts", "automate Linux tasks", "monitor system resources", "backup files", "manage users", or "write production shell scripts". It provides ready-to-use shell script templates for system administration.
gitlab-ci-patterns
wshobson
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
monitor-ci
nrwl
Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", wants to track CI status, or needs help with self-healing CI fixes