Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

brewedops-scanloop

Étoiles0

Forks0

Mis à jour10 juillet 2026 à 01:34

Emulates the scanloop process by reviewing diffs and code for secrets, security holes, and structural risks before claiming a fix is complete.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

butterkookies

butterkookies/Skills-Collection

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	brewedops-scanloop
description	Emulates the scanloop process by reviewing diffs and code for secrets, security holes, and structural risks before claiming a fix is complete.

BrewedOps Scanloop

Trigger: Use this skill after completing a build chunk or a fix, before finalizing it.

Overview

The scanloop is a required static analysis pass on your work to ensure no security vulnerabilities, leaked secrets, or glaring structural issues are introduced.

Process

Self-Review: Look at the changes you just made.
Secret Check: Did you hardcode any API keys, tokens, or passwords? If so, remove them and replace them with environment variables or configuration lookups. (Emulating gitleaks)
Security Check: Are there any obvious injection vulnerabilities or missing validations? (Emulating semgrep)
Dependency Check: Did you add new dependencies? Are they reputable and up to date? (Emulating osv-scanner)

Outcome

Do not proceed to greploop or mark a task as complete until you have explicitly confirmed in your thought process that the code passes the scanloop checks.

Plus depuis ce dépôt

même dépôt

brewedops-augustine-save

butterkookies/Skills-Collection

Emulates Augustine, handling the "save progress" ritual, long-term memory, and deployments (Lane I & J).

2026-07-100

brewedops-confucius-hygiene

butterkookies/Skills-Collection

Emulates Confucius, managing CRM hygiene, deduplication, and contact normalization.

2026-07-100

brewedops-content-drafter

butterkookies/Skills-Collection

Emulates Voltaire / Cicero, handling drafting of content, emails, proposals, and social posts.

2026-07-100

brewedops-diogenes-monitor

butterkookies/Skills-Collection

Emulates Diogenes, a read-only watchdog for monitoring changes, competitors, and live sites.

2026-07-100

brewedops-e2e-developer

butterkookies/Skills-Collection

Orchestrates the complete BrewedOps End-to-End workflow to develop, update, or implement a feature for an app. It takes your prompt and forces the agent through the strict pipeline: Knowledge Check -> Plan -> Build -> Clarity Pass -> Scan -> Greploop -> Verify -> Save.

2026-07-100

brewedops-ghl-auditor

butterkookies/Skills-Collection

Emulates Socrates, the read-only auditor for GoHighLevel and other live platforms.

2026-07-100

name	brewedops-scanloop
description	Emulates the scanloop process by reviewing diffs and code for secrets, security holes, and structural risks before claiming a fix is complete.

BrewedOps Scanloop

Trigger: Use this skill after completing a build chunk or a fix, before finalizing it.

Overview

The scanloop is a required static analysis pass on your work to ensure no security vulnerabilities, leaked secrets, or glaring structural issues are introduced.

Process

Self-Review: Look at the changes you just made.
Secret Check: Did you hardcode any API keys, tokens, or passwords? If so, remove them and replace them with environment variables or configuration lookups. (Emulating gitleaks)
Security Check: Are there any obvious injection vulnerabilities or missing validations? (Emulating semgrep)
Dependency Check: Did you add new dependencies? Are they reputable and up to date? (Emulating osv-scanner)

Outcome

Do not proceed to greploop or mark a task as complete until you have explicitly confirmed in your thought process that the code passes the scanloop checks.