w-errors
Add error handling that matches existing repo error and logging packages.
Install
npx skills add https://github.com/blockmatic/basilic-skills --skill w-errorsSKILL.md
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.
- Identify failure points on the changed path: validation, I/O, authz, empty/invalid input.
- Use the repo error type and logger. Return or render existing user-facing error patterns.
- 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.
- Cover the new path with a test or a named manual scenario. Run the smallest existing check.
- Docs:
/w-docsif behavior or commands changed.
Related skills
improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".