Prowler Ci

Debug and fix GitHub Actions CI failures on your PRs

✨ The solution you've been looking for

Verified
Tested and verified by our team
12565 Stars

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.

github-actions ci-cd pr-gates workflow-debugging secret-scanning conventional-commits changelog codeowners
Repository

See It In Action

Interactive preview & real-world examples

Live Demo
Skill Demo Animation

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

1

Install

claude-code skill install prowler-ci

claude-code skill install prowler-ci
2

Config

3

First Trigger

@prowler-ci help

Commands

CommandDescriptionRequired Args
@prowler-ci pr-check-failure-investigationQuickly identify and resolve failing CI checks blocking your pull requestNone
@prowler-ci changelog-gate-troubleshootingUnderstand when changelog updates are required and how to bypass them appropriatelyNone
@prowler-ci secret-scanning-false-positivesResolve TruffleHog secret scanning alerts in test files and mock dataNone

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.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 the right CHANGELOG.md is updated 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:

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:

  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.

What Users Are Saying

Real feedback from the community

Environment Matrix

Dependencies

GitHub Actions environment
TruffleHog secret scanner

Context Window

Token Usage ~3K-8K tokens for typical workflow debugging sessions

Security & Privacy

Information

Author
prowler-cloud
Updated
2026-01-30
Category
automation-tools