Skill code-foundation-stinger
scriptsRealiza una auditoría de salud de solo lectura en un repositorio para evaluar su preparación para la colaboración entre humanos y agentes de IA.
- Estrellas en GitHub
- 95
- Archivos
- 22
- Último commit
- 18 oct 2026
- Licencia
- AGPL-3.0-or-later
- Herramientas permitidas
- —
¿Qué hace la skill code-foundation-stinger?
Realiza una auditoría de salud de solo lectura en un repositorio para evaluar su preparación para la colaboración entre humanos y agentes de IA.
Resumen generado a partir del SKILL.md de la skill.
Sobre la skill code-foundation-stinger
La función principal de esta herramienta es evaluar si un repositorio está preparado para una colaboración segura entre humanos y agentes de IA. Realiza una auditoría de salud de solo lectura para determinar si una base de código cumple con los estándares esenciales de foundation, como tener archivos lock consistentes, pruebas que pasen y configuraciones de linting adecuadas. Los desarrolladores utilizan esto para evaluar la preparación del repositorio antes de iniciar auditorías de seguridad o calidad más profundas.
Un agente debe cargar este SKILL cuando se le asigne responder preguntas sobre la salud del repositorio, la presencia de CI o la compatibilidad con agentes de IA. El proceso depende de Python 3.11 y git, utilizando scripts como foundation_scan.py para realizar escaneos deterministas y run_in_copy.py para ejecutar comandos del proyecto dentro de una copia temporal para asegurar que el repositorio original permanezca intacto. A diferencia de las herramientas de configuración, este SKILL nunca modifica archivos; en su lugar, produce findings.jsonl, metrics.json y notes.md para documentar brechas y mediciones específicas de acuerdo con el contrato Audit My Code.
Lo que un agente puede hacer con ella
- 1Evaluar la preparación para agentes de IADeterminar si un repositorio contiene la documentación y estructura necesarias para que un agente de IA trabaje de manera efectiva.
- 2Auditar la línea base de salud del repositorioComprobar la presencia de archivos esenciales como configuraciones de CI, pruebas y archivos lock.
- 3Evaluación previa a la auditoría del repositorioVerificar que los sistemas de construcción y las pruebas sean sólidos antes de comenzar una auditoría formal de seguridad o calidad.
Escrito a partir del SKILL.md de la skill. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar la skill code-foundation-stinger
Cada comando copia la carpeta de la skill al directorio de skills del cliente. Reinicia el cliente o inicia una nueva sesión para cargarla.Instalar la skill code-foundation-stinger en Plugin
/plugin marketplace add legioncodeinc/vibe-coding-tools /plugin install code-audit-tools@wasp-nest
Instalar la skill code-foundation-stinger en Claude Code
~/.claude/skills/code-foundation-stinger/SKILL.md
$ npx degit legioncodeinc/vibe-coding-tools/plugins/code-audit-tools/skills/code-foundation-stinger ~/.claude/skills/code-foundation-stingerInstalar la skill code-foundation-stinger en Claude Code (project)
.claude/skills/code-foundation-stinger/SKILL.md
$ npx degit legioncodeinc/vibe-coding-tools/plugins/code-audit-tools/skills/code-foundation-stinger .claude/skills/code-foundation-stingerInstalar la skill code-foundation-stinger en Codex
~/.agents/skills/code-foundation-stinger/SKILL.md
$ npx degit legioncodeinc/vibe-coding-tools/plugins/code-audit-tools/skills/code-foundation-stinger ~/.agents/skills/code-foundation-stingerInstalar la skill code-foundation-stinger en Gemini CLI
~/.gemini/skills/code-foundation-stinger/SKILL.md
$ npx degit legioncodeinc/vibe-coding-tools/plugins/code-audit-tools/skills/code-foundation-stinger ~/.gemini/skills/code-foundation-stingerInstalar la skill code-foundation-stinger en Claude.ai
npx degit legioncodeinc/vibe-coding-tools/plugins/code-audit-tools/skills/code-foundation-stinger code-foundation-stinger && zip -r code-foundation-stinger.zip code-foundation-stinger # claude.ai → Customize → Skills → + → Create skill → Upload a skill → code-foundation-stinger.zip
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Aún sin verificar. Una skill necesita 80 puntos, ningún hallazgo grave y datos suficientes para comprobarla. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblelegioncodeinc/vibe-coding-tools/plugins/code-audit-tools/skills/code-foundation-stinger is public and reachablegithub.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins ↗Aprobado
- Licencia de código abierto (OSI)AGPL-3.0-or-later is not OSI-approvedspdx.org/licenses/AGPL-3.0-or-later.html ↗Hallazgo
- Commit o lanzamiento en el último añoLast commit 2026-10-18github.com/legioncodeinc/vibe-coding-tools/commits ↗Aprobado
- Sin descargar y ejecutar ni robo de credenciales en los scripts4 scripts read; no download-and-run, remote eval, base64 execution or credential uploadAprobado
- Sin instrucciones ocultas en SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/legioncodeinc/vibe-coding-tools/blob/HEAD/plugins ↗Aprobado
- Las herramientas preaprobadas están acotadasNo pre-approved tools; the agent asks before using onegithub.com/legioncodeinc/vibe-coding-tools/blob/HEAD/plugins ↗Aprobado
- SKILL.md sigue el formato de Agent Skillsthe description does not say when to use the skillgithub.com/legioncodeinc/vibe-coding-tools/blob/HEAD/plugins ↗Hallazgo
SKILL.md
Ver en GitHubCode Foundation Stinger
Purpose
Answer one question for the /audit-my-code run: is this repository set up so humans and AI agents can work in it safely? This is the Foundation dimension every audit tier runs first. It measures the repository against the baseline that get-started-stinger establishes (Library Schema v2 tree, wasp-nest.lock, CI, dependency automation, CODEOWNERS, README and policy files, .gitignore and .env.example) and extends it with current repository health practice: OpenSSF Scorecard style checks, whether tests exist and pass, lint and typecheck configuration, lockfile consistency, runtime pins, committed secrets, branch protection, and AI agent readiness (AGENTS.md or CLAUDE.md, size and accuracy). It runs get-started-stinger in assess-only mode: where get-started would create something, a finding names the exact step that would fix it. It produces findings.jsonl, metrics.json and notes.md for 00-foundation/ under the Audit My Code contract 1.0 and changes nothing in the audited repository.
When to use
- The orchestrator dispatches the Foundation dimension for any tier (
foundation,vibe,basic,full,mario) - "Is this repo healthy?", "do we have CI and tests?", "will an AI agent be able to work in this repo?"
- Before a security or quality audit, to learn whether the build, tests and lockfile are sound enough to audit
When not to use
- Setting the repository up or fixing what the audit finds: that is
get-started-stinger(writes files) or themariotier's remediation step - Vulnerability analysis, exploitability, secret rotation:
security-stingerandsecurity-wasp-drone - Duplicate, dead or bloated code:
code-bloat-wasp-drone - Implementation versus PRD checks:
quality-stinger - CI pipeline design depth:
ci-release-stinger; detailed GitHub settings scoring across eight dimensions:github-repo-health-stinger - README authorship:
readme-writing-stinger
Procedure
- Read guides/00-scoping-and-read-only-rules.md first. It fixes the hard rules: never modify the audited repository, run project code only in the throwaway copy, GitHub access read-only, secrets redacted.
- Read
<workspace>/intake.json. Check tools (python3,git,gh auth status) and record caps. - Run
scripts/foundation_scan.py --repo <repo> --gh --out <workspace>/00-foundation/raw/foundation_scan.json(drop--ghif gh is unavailable). It makes the file-presence and API checks and emits contract-shaped findings and measures. - Follow guides 01 to 04 in order, reading only what the scanner cannot judge and resolving every finding tagged
needs-drone-read: 01 Wasp Nest readiness, 02 CI, tests, lint and typecheck (run commands withscripts/run_in_copy.py), 03 dependencies, lockfiles and secrets, 04 repository governance. - Follow 05 writing metrics and findings: write
judgment.jsonlandmeasures-extra.json, runscripts/assemble_foundation.pyuntil it validates, writenotes.md, index the raw artifacts. - Return a short report: verdict, counts by severity, measures in
at-riskorcritical, caps, output paths.
References map
| Path | Load when |
|---|---|
guides/00-scoping-and-read-only-rules.md |
Every run, first |
guides/01-wasp-nest-readiness.md |
Library, lock, agent file checks |
guides/02-ci-tests-lint-typecheck.md |
Workflow review and running tests, lint, typecheck in the copy |
guides/03-dependencies-lockfiles-secrets.md |
Lockfiles, update automation, runtime pins, env files, secret-shaped strings |
guides/04-repository-governance.md |
README, license, CODEOWNERS, branch protection, Scorecard view |
guides/05-writing-metrics-and-findings.md |
Producing and validating the output files |
references/REFERENCE.md |
Map of every reference file |
references/foundation-checklist.md |
Every check id, default severity, owner, get-started step |
references/get-started-assess-map.md |
Naming the get-started step; what a healthy initialized repo has |
references/measures-and-bands.md |
Bands for every metrics.json measure |
references/scorecard-mapping.md |
Which Scorecard checks are approximated and how |
references/gh-readonly-calls.md |
Before any gh call |
references/detection-patterns.md |
Manual workflow, secrets, lockfile and agent-file checks |
references/runtime-eol-table.md |
End-of-life Node and Python pins |
references/finding-templates.md |
Writing judgment findings |
references/research/distilled-foundation.md |
Verifying a claim or resolving a conflict |
| Source research archive (not shipped with the plugin) | Source-repository only; the shipped distillation summarizes it, do not require it |
scripts/foundation_scan.py |
Step 3: deterministic scan, read-only |
scripts/run_in_copy.py |
Running project commands in the throwaway copy only |
scripts/assemble_foundation.py |
Step 5: validate and write the three output files |
scripts/test_foundation.py |
After any script edit: python3 scripts/test_foundation.py |
Related drones and stingers
- code-foundation-wasp-drone - The paired Drone that runs this Stinger and writes
00-foundation/. - audit-my-code-stinger - Owns the run contract, tiers and workspace this Stinger writes into.
get-started-stinger- Defines the baseline in assess mode; this Stinger never runs its write steps. Ships with the core Wasp Nest plugin, not this pack.github-repo-health-stinger- Source of the read-only branch protection and settings checks; use it for the full eight-dimension GitHub hygiene report.security-stinger- Receives handoffs for committed secrets and workflow injection.dependency-audit-stinger- Deeper supply-chain triage beyond lockfile and update-tool presence.
Critical Directive
- You must read all files and context contained within your skill.
- In the event your core knowledge does not provide sufficient guidance you must make every attempt to search the internet, related knowledge base documentation files, and other available resources to supplement your knowledge prior to proceeding with your task.
- Additional related skills can be found here:
get-started-stinger- Baseline for a correctly initialized repository; read in full before the first run.github-repo-health-stinger- Read-only GitHub hygiene checks to borrow.security-stinger- Where committed-secret and workflow findings go next.
Archivos de esta skill
22Preguntas sobre la skill code-foundation-stinger
¿Cómo instalo la skill code-foundation-stinger en Claude Code?
Ejecuta npx degit legioncodeinc/vibe-coding-tools/plugins/code-audit-tools/skills/code-foundation-stinger ~/.claude/skills/code-foundation-stinger. Claude Code carga las skills desde ~/.claude/skills (todos los proyectos) o .claude/skills (un proyecto) y usa una skill cuando su descripción coincide con la tarea.
¿Qué clientes pueden usar la skill code-foundation-stinger?
Cualquier cliente que lea el formato Agent Skills: Claude Code, Codex, Gemini CLI y claude.ai (subir como ZIP). Los scripts de la skill se ejecutan solo donde el cliente permite la ejecución de código.
¿Qué audita la herramienta?
Verifica la configuración de Wasp Nest, la preparación para agentes, CI, pruebas, linting, archivos lock, secretos y la gobernanza del repositorio.
¿Qué archivos de salida genera la auditoría?
La herramienta genera findings.jsonl, metrics.json y notes.md para el directorio foundation.