correct
From the author
Find 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.
Install
npx skills add backnotprop/pstack --skill correct -a claude-code
Installs to .claude/skills/correct/ · Each command fetches the skill straight from GitHub with the open skills CLI.
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
No warnings.
Why 90
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.
- error-recoveryNoobyGains/godmodeUse when a fix attempt has failed more than once for the same problem, when a fix for one problem causes another, when the same file keeps being edited without progress, when test results get worse, or when the work feels stuck in a loop.Testing★ 115
- debuggingwjgoarxiv/litgravityFix a bug: reproduce it, test several hypotheses, isolate the cause, lock it with a failing test, then verify on the real surface.Engineering★ 166
- fixavibebuilder/claude-primeFix bugs and broken behavior when there is enough evidence to act on a repair path. Use for errors, crashes, incorrect results, API failures (500, 404, 403), CORS problems, database exceptions, broken rendering, duplicated or wrong data, off-by-one mistakes, timezone/date bugs, broken forms, config-caused runtime failures, and regressions. Trigger when the user wants the bug repaired and the conversation already contains a clear failing area, a reproducible failing test, a concrete error path, or a prior diagnosis to implement. Do NOT use for new features, pure explanation, architecture discussion, broad research, or bug reports where the main need is figuring out why the behavior happens — use diagnose for that.Testing★ 119
- honor-codetmcfarlane/team-avatarZuko's honor code for making repeated agent mistakes impossible. Zuko turned his past mistakes into a code he lives by. Use for correct, /correct, "stop making this mistake", "agents keep doing X", or each time the operator corrects you. Finds the mistake classes agents repeat in this repo and fixes each at the highest level that works, architecture first, then types, then a lint whose error names the fix, then a test, and docs last. Proves each check fails on a real past mistake.Engineering★ 111
- principle-fix-root-causesmichael-denyer/pstack-claudeApply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.Engineering★ 3.6K
- test-fixdrobins25/craftThis skill should be used when validate-chunk reports test failures specifically, when the user says "tests are failing", "figure out what's wrong with the tests", "fix the failing tests", or when test assertions don't match expected output after chunk implementation. Triages whether the test or the implementation is wrong and fixes the correct one.Testing★ 69
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in