Toolverse
All skills
Security

prowler-ci

by prowler-cloud

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

Installation

Pick a client and clone the repository into its skills directory.

Installation

Quick info

Author
prowler-cloud
Category
Security
GitHub repo

About this skill

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.

How to use

  1. Zidentyfikuj, który workflow lub job się nie powiódł, szukając nazwy w komunikacie błędu CI oraz odpowiadającego mu pliku w katalogu .github/workflows/.
  2. Sprawdź filtry ścieżek w pliku workflow — czy workflow powinien uruchomić się dla plików, które zmieniłeś? Jeśli zmienione pliki nie pasują do warunku paths, workflow nie uruchomi się.
  3. Jeśli błąd dotyczy walidacji tytułu PR, otwórz .github/workflows/conventional-commit.yml i sprawdź, czy Twój tytuł PR zgodny jest ze standardem Conventional Commits (np. feat:, fix:, docs:).
  4. Jeśli błąd dotyczy changelog, sprawdź .github/workflows/pr-check-changelog.yml — upewnij się, że zaktualizowałeś odpowiedni plik CHANGELOG.md lub dodaj etykietę no-changelog do PR, jeśli zmiana jej nie wymaga.
  5. Dla innych błędów (conflict markers, secret scanning, labeler) skonsultuj się z mapą plików w README: .github/workflows/pr-conflict-checker.yml, .github/workflows/find-secrets.yml, .github/workflows/labeler.yml.
  6. Użyj skill do wyjaśnienia, które workflow powinny uruchomić się dla Twoich zmian (UI, API, SDK) i dlaczego niektóre mogą być pominięte ze względu na filtry ścieżek.

Related skills

typescript-review

by metabase

Review TypeScript and JavaScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs containing TypeScript/JavaScript code.

Security
17133

academic-researcher

by Shubhamsaboo

Academic research assistant for literature reviews, paper analysis, and scholarly writing.\nUse when: reviewing academic papers, conducting literature reviews, writing research summaries,\nanalyzing methodologies, formatting citations, or when user mentions academic research,

Security
1260

backend-security-coder

by sickn33

Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.

Security
1133

content-creator

by alirezarezvani

Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content

Security
25124

senior-security

by davila7

Comprehensive security engineering skill for application security, penetration testing, security architecture, and compliance auditing. Includes security assessment tools, threat modeling, crypto implementation, and security automation. Use when designing security architecture,

Security
2482

architect-review

by sickn33

Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural

Security
2773