help
/help
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.
- Author
- waynesutton ↗
- Repository
- builder-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 27.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 27.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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.
Original author description
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.
How it works
- Reflect before acting
- Confidence bar
- Convex rules
- Scope
- UI
- Docs policy
- Git
- Checklist
SKILL.md preview
--- name: help description: 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. --- # Help Slow down for thirty seconds before the first edit. It saves an hour later. ## Reflect before acting 1. Why does the current code not do what the user wants? Read it. Do not guess. 2. What is missing, wrong, or incomplete relative to the request? 3. List two or three candidate causes. 4. Pick the most likely one and say why. 5. If the answer to "what is unclear" is not empty, ask one question and stop. Never assume. A wrong assumption costs more than a question. ## Confidence bar 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. ## Convex rules - Mutations map form fields to document fields one to one. Field names match. - Patch without reading when possible. Indexed queries for ownership. Idempotent with early returns. `Promise.all` for independent writes. - Load the matching `convex-*` skill for anything deeper. ## Scope Change: - Files the request needs. - The schema, if the request needs it. - `changelog.md`, `files.md`, `task.md` after the change lands. Dates from `git log --date=short`, never invented. Do not change: - UI, layout, colors, or copy that the request did not mention. - Existing sections, features, or components. Nothing gets removed without being asked. - [Add project specific protected areas: admin dashboard, billing flow, etc.] ## UI - Site design system for every popup, alert, modal, toast, confirmation. Never the browser default. - Vercel Web Interface Guidelines: https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/refs/heads/main/AGENTS.md ## Docs policy Do not create README, CONTRIBUTING, SUMMARY, or USAGE files unless asked. A short summary in the reply is enough. ## Git 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. ## Checklist Before the first edit: - [ ] I can name the root cause - [ ] I considered at least two fixes and picked one for a reason - [ ] I am at or above the confidence bar - [ ] I know which files change and which do not - [ ] Anything unclear has been asked Before saying done: - [ ] The fix was verified, not just written - [ ] Nothing outside the request changed - [ ] Docs synced if the change was non trivial
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · waynesutton/builder-skills | 90 | Apache-2.0 |
| Ovich/charrette | 100 | MIT |
| davepoon/buildwithclaude | 100 | MIT |
| crisandrews/clawcode | 100 | MIT |
| lamngockhuong/aiteamkit | 100 | MIT |
| The01Geek/prflow | 100 | MIT |
| Cruna-Noise-To-Signal/cruna-plugins | 100 | Apache-2.0 |
| wookiya1364/scv-claude-code | 100 | MIT |
| oliver-kriska/claude-elixir-phoenix | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 3089bc2d83f2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100root-cause-debugging
Debug by finding the root cause before changing code: reproduce, read the full error, check what changed, form one hypothesis at a time and test it, write the failing test, then fix; with a hard stop after three failed fixes to question the approach. Use when a test fails, a bug… - 100systematic-debugging
Debug a bug, test failure, crash, or unexpected behaviour by finding the root cause before changing anything, instead of guessing at fixes. Works in any language or stack. Use when something is broken, a test is failing, behaviour is wrong, or a previous fix didn't hold. - 92debug
Find the root cause of a bug before you fix it. Read this skill before you fix any bug. Read it also when the fix looks obvious. Use it when the user says "fix", "broken", "not working", "error", "failing", or "bug". Use it also when a test fails unexpectedly during other work. - 100bug-fix
Bug-fixing workflow that coordinates diagnosis, test-driven reproduction, root-cause analysis, and targeted fixes. Use when the user wants to fix a bug with thorough investigation and regression testing. - 85vibe-debug
Find the root cause before changing anything — for a bug, a test failure, a check that went red, or behaviour nobody can explain. Use when the cause is not yet known, when a previous fix did not hold, or when the same symptom has come back. - 100root-cause-analysis
Use when a bug has been reproduced or confirmed and needs its exact cause traced before a fix is proposed, or when the user says 'investigate issue'. Traces a bug to its exact cause in the codebase. Investigation only — reports the cause on the ticket; does not edit code.