python-bug-fixer
Skill1 starsChanged 47 days agoApache-2.0View on GitHub
Menganalisis dan memperbaiki bug pada proyek Python secara deterministik. Gunakan ketika pengguna melaporkan error, traceback, atau test yang gagal.
In this repository21 other files it gives its agents.
- min-tokSkill
- academic-scholarSkill
- agent-mcp-craftSkill
- anti-overengineeringSkill
- api-security-reviewerSkill
- data-verifySkill
- deep-researcherSkill
- design-no-slopSkill
- enterprise-teamSkill
- git-craftSkill
- human-codingSkill
- laravel-architectSkill
- markdown-docSkill
- modern-stack-horizonSkill
- modern-web-guidanceSkill
- omni-pilotSkill
- perf-benchmarkSkill
- react-ui-architectSkill
- reverse-engineer-anythingSkill
- typescript-nodeSkill
- tyw-auditSkill
The file
Files
Python Bug Fixer (Elite SOP)
Tujuan
Menemukan akar masalah (Root Cause) dan menerapkan perbaikan struktural (bukan sekadar patch) dengan mutasi token sekecil mungkin tanpa merusak perilaku lain.
Workflow Eksekusi
- Traceback Analysis: Baca stack trace dari bawah ke atas. Identifikasi file penyebab utama.
- Context Gathering: Gunakan
grep_searchatauview_fileuntuk membaca fungsi yang gagal dan file terkait. JANGAN menebak isi file. - Hypothesis Generation: Buat 2 hipotesis mengapa variabel/tipe data tersebut gagal (contoh: NoneType operation, Index Out of Bounds).
- Surgical Fix: Gunakan alat
replace_file_contentuntuk memutasi blok kode secara persis. JANGAN menulis ulang seluruh file besar. - Regression & Run: Wajib jalankan kode via terminal (
run_command) untuk memastikan bug hilang dan tidak ada modul lain yang pecah. - Knowledge Sync: Jika bug bersifat struktural, log ke
KNOWLEDGE_BASE.md.
Aturan Absolut (Guardrails)
- Zero Empty Catches: Dilarang menggunakan
except Exception: passuntuk menyembunyikan error. - No Dependency Hallucination: Jika modul eksternal dicurigai, baca dokumentasi
.d.tsatauREADME.mdlokal sebelum mengganti sintaks. - Type Safety: Selalu tambahkan type hints (
-> int,: str) pada fungsi yang diperbaiki.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.