prowler-ci
prowler-ci guides you through Prowler's CI and PR gate system, helping diagnose why GitHub Actions workflows fail. It covers PR title validation, changelog requirements, conflict marker detection, and secret scanning—with a quick reference map to key workflow files and a practical debug checklist.
prowler-ci helps you debug and resolve failing GitHub Actions CI checks, including PR title validation, changelog gates, and secret scanning.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
prowler-ci helps you debug and resolve failing GitHub Actions CI checks, including PR title validation, changelog gates, and secret scanning. prowler-ci guides you through Prowler's CI and PR gate system, helping diagnose why GitHub Actions workflows fail. It covers PR title validation, changelog requirements, conflict marker detection, and secret scanning—with a quick reference map to key workflow files and a practical debug checklist.
Use it when
- prowler-ci integrates TruffleHog for secret detection in workflows.
- prowler-ci enforces multiple PR gates: (1) Conventional Commit validation on PR titles.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
prowler-cloud/prowler/prowler-ci · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
Why is my PR check failing in prowler-ci?
prowler-ci helps you diagnose GitHub Actions workflow failures on pull requests. Common causes include: PR title not following conventional commit format, missing changelog fragment, unresolved conflict markers in code, or TruffleHog detecting secrets. Use the debug checklist to verify each gate: check your commit message format, confirm changelog files are in `.changelog/` with proper naming, scan for `<<<<<<<` markers, and review TruffleHog logs for false positives that may need allowlisting.
How do I fix TruffleHog secret scanning false positives?
prowler-ci integrates TruffleHog for secret detection in workflows. False positives often occur with test AWS keys or API key examples. Review the TruffleHog job output to identify the flagged content and file. If it's a legitimate test value or placeholder, you can add an allowlist entry in your repository's TruffleHog configuration to exclude that pattern. For OpenAI API keys in test files, verify the key is non-production before allowlisting.
What are the PR validation rules and gates in prowler-ci?
prowler-ci enforces multiple PR gates: (1) Conventional Commit validation on PR titles, (2) Changelog requirement—add a fragment to `.changelog/` unless labeled `no-changelog`, (3) Conflict marker detection to catch unresolved merges, (4) TruffleHog secret scanning, and (5) CODEOWNERS and labeler automation. Each gate must pass before merge. The system also validates path filtering in GitHub Actions workflows to ensure jobs run only when relevant files change.
How do I resolve conflict markers in my PR?
prowler-ci detects unresolved conflict markers (`<<<<<<<`, `=======`, `>>>>>>>`) that Git leaves when merges fail. To fix: open the flagged files, locate the conflict sections, manually choose which code to keep or merge both versions, then remove all marker lines. After resolving, stage and commit the changes. Re-push to trigger CI again. The conflict marker gate will pass once all markers are removed from the repository.
Where should I place changelog fragments in prowler-ci?
prowler-ci requires changelog fragments in the `.changelog/` directory at your repository root. Name files using the pattern `<PR-number>.<type>.md` (e.g., `123.feature.md`). Each fragment should contain a brief description of your change. If your PR has no user-facing changes, apply the `no-changelog` label to skip this gate. The changelog gate validates both file location and naming convention before allowing merge.
How does CODEOWNERS and labeler automation work in prowler-ci?
prowler-ci automates PR labeling and code owner assignment through GitHub Actions workflows. The labeler workflow applies labels based on file paths modified in your PR, while CODEOWNERS automation ensures relevant maintainers are notified. These automations run on PR open and update events. Review your repository's `.github/CODEOWNERS` file to see ownership rules and `.github/labeler.yml` to understand label-to-path mappings that trigger automatic labeling.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
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:
(truncated - see the full file via the links below)
File tree — 1 file
skills/prowler-ci/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Debug and resolve failing GitHub Actions CI checks on pull requests”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Prowler-changelog automates changelog management across UI, API, MCP Server, and SDK components using a fragment-based system that prevents merge conflicts on concurrent PRs. Each change gets its own fragment file under `changelog.d/` directories, which compile into versioned `CHANGELOG.md` files at release time. The skill enforces semantic versioning rules, validates fragment format, and requires explicit confirmation before any changelog edits.
This skill streamlines pull request reviews for compliance framework updates by validating JSON syntax, checking for duplicate requirement IDs, and ensuring framework metadata completeness. It applies a structured checklist covering file location, changelog fragments, and dashboard patterns to catch issues before merge.
This skill equips you with battle-tested patterns for writing Prowler API tests, covering JSON:API request formatting, cross-tenant isolation via row-level security, role-based access control, and Celery task mocking. It includes a fixture dependency chain, response status code reference, and explicit rules for avoiding common pitfalls like TruffleHog false positives and incorrect content-type headers.
Prowler-docs provides the authoring standards and formatting conventions for creating consistent Prowler documentation. It covers brand voice principles, markdown formatting, SEO best practices, and MDX component usage across feature docs, tutorials, API references, and compliance guides.
gate-check automates the verification step in the change governance process by selecting the correct approval gate based on affected layers, running its entry criteria and error checks, and populating the approval form for human sign-off. It verifies but never approves—all signature and decision fields remain blank for the designated approvers.
tdd guides you through mandatory test-driven development across all Prowler components using the red-green-refactor cycle. Learn to write failing tests first, implement minimum code to pass, triangulate with edge cases, and refactor with confidence. Covers TypeScript/React, Python SDK, and Django API stacks with practical examples.
More skills prowler-commit (Apache-2.0)