Skill code-foundation-stinger
scriptsMelakukan audit kesehatan read-only pada sebuah repository untuk menilai kesiapan kolaborasi antara manusia dan AI agent.
- Bintang GitHub
- 95
- File
- 22
- Commit terakhir
- 18 Okt 2026
- Lisensi
- AGPL-3.0-or-later
- Tool yang diizinkan
- —
Apa fungsi skill code-foundation-stinger?
Melakukan audit kesehatan read-only pada sebuah repository untuk menilai kesiapan kolaborasi antara manusia dan AI agent.
Ringkasan dibuat dari SKILL.md skill ini.
Tentang skill code-foundation-stinger
Fungsi utama dari tool ini adalah untuk menilai apakah sebuah repository sudah siap untuk kolaborasi yang aman antara manusia dan AI agent. Tool ini melakukan audit kesehatan secara read-only untuk menentukan apakah sebuah codebase memenuhi standar fondasi esensial, seperti memiliki lockfiles yang konsisten, lulus tests, dan konfigurasi linting yang tepat. Developer menggunakan ini untuk mengevaluasi kesiapan repository sebelum memulai audit keamanan atau kualitas yang lebih mendalam.
Seorang agent harus memuat SKILL ini saat ditugaskan untuk menjawab pertanyaan tentang kesehatan repository, keberadaan CI, atau kompatibilitas AI agent. Proses ini bergantung pada Python 3.11 dan git, menggunakan script seperti foundation_scan.py untuk melakukan scan deterministik dan run_in_copy.py untuk mengeksekusi perintah project di dalam salinan sementara guna memastikan repository asli tetap tidak tersentuh. Berbeda dengan tool setup, SKILL ini tidak pernah memodifikasi file; sebaliknya, ia menghasilkan findings.jsonl, metrics.json, dan notes.md untuk mendokumentasikan celah dan pengukuran spesifik sesuai dengan kontrak Audit My Code.
Apa yang bisa dilakukan agent dengannya
- 1Evaluasi kesiapan AI agentMenentukan apakah sebuah repository memiliki dokumentasi dan struktur yang diperlukan agar AI agent dapat bekerja secara efektif.
- 2Audit baseline kesehatan repositoryMemeriksa keberadaan file esensial seperti konfigurasi CI, tests, dan lockfiles.
- 3Asesmen repository pra-auditMemverifikasi bahwa build systems dan tests sudah solid sebelum memulai audit keamanan atau kualitas secara formal.
Ditulis dari SKILL.md milik skill tersebut. Setiap use case diverifikasi dengan kutipan darinya.
Cara install skill code-foundation-stinger
Setiap perintah menyalin folder skill ke direktori skills client. Restart client atau mulai sesi baru untuk memuatnya.Install skill code-foundation-stinger di Plugin
/plugin marketplace add legioncodeinc/vibe-coding-tools /plugin install code-audit-tools@wasp-nest
Install skill code-foundation-stinger di 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-stingerInstall skill code-foundation-stinger di 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-stingerInstall skill code-foundation-stinger di 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-stingerInstall skill code-foundation-stinger di 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-stingerInstall skill code-foundation-stinger di 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
Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Belum terverifikasi. Skill perlu skor 80, tanpa temuan serius, dan data yang cukup untuk kami cek. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkaulegioncodeinc/vibe-coding-tools/plugins/code-audit-tools/skills/code-foundation-stinger is public and reachablegithub.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins ↗Lolos
- Lisensi open source (OSI)AGPL-3.0-or-later is not OSI-approvedspdx.org/licenses/AGPL-3.0-or-later.html ↗Temuan
- Ada commit atau release dalam satu tahun terakhirLast commit 2026-10-18github.com/legioncodeinc/vibe-coding-tools/commits ↗Lolos
- Skrip tanpa unduh-lalu-jalankan atau pencurian kredensial4 scripts read; no download-and-run, remote eval, base64 execution or credential uploadLolos
- Tidak ada instruksi tersembunyi di SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/legioncodeinc/vibe-coding-tools/blob/HEAD/plugins ↗Lolos
- Tool yang diizinkan otomatis dibatasiNo pre-approved tools; the agent asks before using onegithub.com/legioncodeinc/vibe-coding-tools/blob/HEAD/plugins ↗Lolos
- SKILL.md mengikuti format Agent Skillsthe description does not say when to use the skillgithub.com/legioncodeinc/vibe-coding-tools/blob/HEAD/plugins ↗Temuan
SKILL.md
Lihat di 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.
Berkas dalam skill ini
22Pertanyaan seputar skill code-foundation-stinger
Bagaimana cara install skill code-foundation-stinger di Claude Code?
Jalankan npx degit legioncodeinc/vibe-coding-tools/plugins/code-audit-tools/skills/code-foundation-stinger ~/.claude/skills/code-foundation-stinger. Claude Code memuat skill dari ~/.claude/skills (semua proyek) atau .claude/skills (satu proyek) dan menggunakan skill saat deskripsinya cocok dengan tugas.
Client mana saja yang bisa menggunakan skill code-foundation-stinger?
Client apa pun yang membaca format Agent Skills: Claude Code, Codex, Gemini CLI, dan claude.ai (unggah sebagai ZIP). Script dalam skill hanya berjalan di client yang mengizinkan eksekusi kode.
Apa yang diaudit oleh tool ini?
Tool ini memeriksa setup Wasp Nest, kesiapan agent, CI, tests, linting, lockfiles, secrets, dan tata kelola repository.
File output apa saja yang dihasilkan oleh audit ini?
Tool ini menghasilkan findings.jsonl, metrics.json, dan notes.md untuk direktori foundation.