evo-build-diagnosis
De la autor
Analyzes a Python repository to identify the root causes of build failures, including syntax errors, import errors, test failures, and build configuration issues. Use when diagnosing why a Python project fails to build or pass tests. Scans repository files for syntax errors via ast.parse/compile, parses pytest output and CI logs, checks build configuration files (pyproject.toml, setup.py, setup.cfg), identifies missing dependencies, and produces a structured diagnosis report.
Instalare
npx skills add OpenLAIR/OpenSkill --skill evo-build-diagnosis -a claude-code
Se instalează în .claude/skills/evo-build-diagnosis/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
- Include scripturi pe care nu le-am verificatScăzut
De ce 75
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- evo-maven-build-diagnosisOpenLAIR/OpenSkillExecutes Maven builds, captures output, and parses error logs to identify root causes of build failures. Handles compilation errors, dependency resolution failures, POM configuration issues, and JDK version incompatibilities.Altele★ 97
- evo-python-library-discoveryOpenLAIR/OpenSkillDetects Python libraries/packages in a directory by checking for pyproject.toml, setup.py, setup.cfg, or other standard Python project markers. Provides utilities to list library paths and analyze their structure, entry points, and key functions for testing.Inginerie★ 97
- error-explanation-generatorArabelaTso/Skills-4-SEExplains test failures and provides actionable debugging guidance. Use when tests fail (unit, integration, E2E), builds fail, or code throws errors. Analyzes error messages, stack traces, and test output to identify root causes and suggest concrete fixes. Handles pytest, jest, junit, mocha, vitest, selenium, cypress, playwright, and other testing frameworks across Python, JavaScript/TypeScript, Java, Go, and other languages.Testare★ 259
- diagnoseKerberosClaw/kc_ai_skillsUse when the user reports misbehaving software to investigate — a bug, crash, wrong output, flaky behavior, or '為什麼壞掉/不會動/查一下' — and the root cause is not yet established. Enforces building a red-capable reproduction command BEFORE any hypothesis is allowed, then 3-5 ranked falsifiable hypotheses before testing any single one. NOT for conceptual questions, code reading requests, or feature work. When a failing command already exists, Step 1 is pre-satisfied — still apply, jumping straight to the hypothesis discipline.Testare★ 79
- testing-pyericrisco/rsc-harnessUse when writing or fixing Python tests with pytest — especially when the suite is green but bugs still ship, when you must decide where to patch a mocked dependency, when coverage is high but catches nothing, when fixture scope leaks state, or when adding property-based tests for parsers and invariants. NOT browser end-to-end flows (that is `e2e-testing`), NOT JS/TS unit tests (that is `testing-web`), NOT Go tests (that is `testing-go`).Testare★ 272
- test-guided-bug-detectorArabelaTso/Skills-4-SEAnalyze failing tests to detect functional bugs in code. Takes repository and failing test output as input, analyzes execution behavior, assertions, and stack traces to identify suspicious code regions and root causes. Use when debugging test failures, investigating regression bugs, or understanding why tests fail. Explains the bug mechanism, identifies affected code, and suggests fixes based on test expectations vs actual behavior.Testare★ 259
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te