Prowler Ci

Name: Prowler Ci
Author: prowler-cloud

prowler-cloud/prowler

68 installs
14.5k repo stars
Updated August 4, 2026
prowler-cloud/prowler

prowler-ci is a Claude Code skill for ai & agent building.

About

prowler-ci is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

prowler-ci
AI & Agent Building
AI-coding skill

Prowler Ci by the numbers

68 all-time installs (skills.sh)
Ranked #5,858 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
Data as of Aug 5, 2026 (Skillselion catalog sync)

npx skills add https://github.com/prowler-cloud/prowler --skill prowler-ci

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/prowler-cloud/prowler/prowler-ci.svg)](https://skillselion.com/skills/prowler-cloud/prowler/prowler-ci)

Installs	68
repo stars	★ 14.5k
Last updated	August 4, 2026
Repository	prowler-cloud/prowler ↗

How do I helps with ai & agent building tasks.?

Helps with ai & agent building tasks.

Who is it for?

Best when you're working on ai & agent building and need structured help with prowler ci.

Skip if: Teams with no ai & agent building needs, or anyone wanting a generic chat assistant without this specific workflow.

When should I use this skill?

When you need to helps with ai & agent building tasks., or when prowler-ci is a claude code skill for ai & agent building.

What you get

Structured output aligned to prowler-ci: prowler-ci, AI & Agent Building.

Files

SKILL.mdMarkdownGitHub ↗

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:

# 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)