Prowler Ci
Debug and fix GitHub Actions CI failures on your PRs
✨ The solution you've been looking for
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.
See It In Action
Interactive preview & real-world examples
AI Conversation Simulator
See how users interact with this skill
User Prompt
My PR is failing the conventional-commit check. Can you help me understand what's wrong with my title?
Skill Processing
Analyzing request...
Agent Response
Clear explanation of PR title validation rules and how to fix the title to match Conventional Commits format
Quick Start (3 Steps)
Get up and running in minutes
Install
claude-code skill install prowler-ci
claude-code skill install prowler-ciConfig
First Trigger
@prowler-ci helpCommands
| Command | Description | Required Args |
|---|---|---|
| @prowler-ci pr-check-failure-investigation | Quickly identify and resolve failing CI checks blocking your pull request | None |
| @prowler-ci changelog-gate-troubleshooting | Understand when changelog updates are required and how to bypass them appropriately | None |
| @prowler-ci secret-scanning-false-positives | Resolve TruffleHog secret scanning alerts in test files and mock data | None |
Typical Use Cases
PR Check Failure Investigation
Quickly identify and resolve failing CI checks blocking your pull request
Changelog Gate Troubleshooting
Understand when changelog updates are required and how to bypass them appropriately
Secret Scanning False Positives
Resolve TruffleHog secret scanning alerts in test files and mock data
Overview
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 - 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 the right
CHANGELOG.mdis updated 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:
1# BAD - looks like real OpenAI key
2api_key = "sk-test1234567890T3BlbkFJtest1234567890"
3
4# GOOD - obviously fake
5api_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.
What Users Are Saying
Real feedback from the community
Environment Matrix
Dependencies
Context Window
Security & Privacy
Information
- Author
- prowler-cloud
- Updated
- 2026-01-30
- Category
- automation-tools
Related Skills
Prowler Ci
Helps with Prowler repository CI and PR gates (GitHub Actions workflows). Trigger: When …
View Details →Changelog Automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use …
View Details →Changelog Automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use …
View Details →