lov-fix-until-no-error
From the author
围绕明确验证命令持续定位和修复失败项直到通过或遇到真实阻塞。支持明确输入与结果回读。Use to fix errors until the specified checks pass.
Install
npx skills add lovstudio/skills --skill lov-fix-until-no-error -a claude-code
Installs to .claude/skills/lov-fix-until-no-error/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 76
Security85
Provenance62
Maintenance100
Licence100
Adoption33
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- lov-fix-generallovstudio/skills根据报错和复现证据定位根因、实施修复并验证原路径。支持明确输入与结果回读。Use to diagnose and fix a software error.Other★ 72
- lov-agent-instructionslovstudio/skills诊断或完善项目 Agent 指令文件，适配不同宿主并保留真实工程约定。支持明确输入与结果回读。Use to review or improve project agent instructions.Engineering★ 72
- lov-code-reviewlovstudio/skills审查实际差异中的正确性、安全和维护风险并给出可定位意见。支持明确输入与结果回读。Use to review a code change for actionable defects.Engineering★ 72
- agentsop-test-fix-loopagentsope/SkillAlchemyDecision protocol for wiring a verify-then-fix loop around a code-editing LLM agent. The agent edits → runs lint/test → reads the output → fixes → re-runs, bounded by an iteration cap and an escalation rule. Activates whenever a coder agent has a verifiable success criterion (exit code, type-checker output, failing assertion) and the user wants the agent to converge to "green" on its own. Framework-agnostic — wraps Aider's `--auto-lint`/`--auto-test`, an OpenHands SWE-Bench loop, a manual LangGraph cycle, or Claude Code's bash tool just the same.Testing★ 449
- lov-fix-broken-linkslovstudio/skills核对项目路由及页面链接，修复失效目标并保留有效导航。支持明确输入与结果回读。Use to find and fix broken links in a project.Other★ 72
- correctmichael-denyer/pstack-claudeFind the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.Testing★ 3.4K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in