w-errors — Claude Code skill: error handling
w-errors — a Claude Code skill that adds error handling in line with a repository’s conventions. Invoke it explicitly while changing code.
MIT 647 installs ★ 1 updated 2026-10-02
npx skills add blockmatic-icebox/basilic-skills --skill w-errors -a claude-codeWhat w-errors does
The skill finds failure points along the changed code path and adds handling that follows the repository’s conventions. It uses existing error types, logging packages, and user-facing error patterns; the relevant guidance comes from the error-handling page named in AGENTS.md.
A write can be retried only when replaying it is safe. If a retry is already required but replay safety does not hold, the skill keeps an explicit no-retry path with a bounded deadline. Cover the new path with a test or a named manual scenario, then run the smallest existing check.
The agent does not invoke the skill automatically because disable-model-invocation is enabled. If behavior or commands change, it also points to /w-docs for documentation updates.
What it helps with
- find failure points in changed code
- match error handling to repository types and logging
- cover a new path with a test or manual scenario
- run the smallest existing check
Example prompts for the agent
- Add error handling to the changed code using this repository’s conventions.
- Find failure points along this path and use the existing logger.
- Test the new error path and run the smallest existing check.
How to install w-errors
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-errors -a claude-code2Manually: put the files in place
~/.claude/skills/w-errors/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/w-errors/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-errors -a codex2Manually: put the files in place
.agents/skills/w-errors/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-errors -a cursor2Manually: put the files in place
.cursor/skills/w-errors/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install blockmatic-icebox/basilic-skills skills/workflow/w-errors2Manually: put the files in place
.github/skills/w-errors/SKILL.md1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-errors -a gemini-cli2Platform CLI
gemini skills install https://github.com/blockmatic-icebox/basilic-skills --path skills/workflow/w-errorsManually: put the files in place
.devin/skills/w-errors/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-errors -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about w-errors
How do I install w-errors in Claude Code?
Run npx skills add blockmatic-icebox/basilic-skills --skill w-errors -a claude-code. The skill file is at ~/.claude/skills/w-errors/SKILL.md.
What does w-errors do?
It adds failure handling to changed code using the repository’s existing error types, logger, and user-facing patterns. It also calls for a test or manual scenario and the smallest existing check.
When does w-errors allow a retry?
Only when replaying a write is safe. Otherwise, if a retry is already required, it keeps an explicit no-retry path with a bounded deadline.
Source text
SKILL.md · MIT
--- name: w-errors description: Add error handling that matches existing repo error and logging packages. disable-model-invocation: true --- Harden the current code's failure paths. Follow the error-handling page named from `AGENTS.md` and existing error/logger packages. Do not hide the owning failure with retries. 1. Identify failure points on the changed path: validation, I/O, authz, empty/invalid input. 2. Use the repo error type and logger. Return or render existing user-facing error patterns. 3. Retry only when the write is replay-safe. Otherwise keep an explicit no-retry path with a bounded deadline if a retry is already required. 4. Cover the new path with a test or a named manual scenario. Run the smallest existing check. 5. Docs: `/w-docs` if behavior or commands changed.
© blockmatic-icebox · MIT · blockmatic-icebox/basilic-skills