Think before typing. Root cause first, two candidate fixes, pick one, ask if still unclear, then change only the files the request needs. Edit the confidence bar and scope rules to fit the project. Use when a bug report comes in, when a previous fix did not work, or when the request is vague.
71
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Slow down for thirty seconds before the first edit. It saves an hour later.
Never assume. A wrong assumption costs more than a question.
Do not write code below [98]% confidence in what needs to change. Below that: read more, ask, or propose a plan instead of a diff.
Promise.all for independent writes.convex-* skill for anything deeper.Change:
changelog.md, files.md, task.md after the change lands. Dates from git log --date=short, never invented.Do not change:
Do not create README, CONTRIBUTING, SUMMARY, or USAGE files unless asked. A short summary in the reply is enough.
Load git-safety before any git command that could discard work. Short version: git status first, git diff before discarding, edit files by hand to undo, never reset --hard / checkout -- . / clean -fd / stash drop without the user saying yes to that exact command.
Before the first edit:
Before saying done:
waynesutton/convexskills
82d1ce2
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.