From jhostalek-skills
Use when auditing and fixing logic bugs in a scope — off-by-one, wrong operator, inverted condition, unhandled boundary cases, unit/dimension mismatch, code that doesn't do what its name or docstring claims. Triggers on "audit correctness", "fix logic bugs", "check for off-by-one", "correctness review".
How this skill is triggered — by the user, by Claude, or both
Slash command
/jhostalek-skills:audit-correctnessThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
!`cat "${CLAUDE_SKILL_DIR}/../audit-workflow.md"`
!cat "${CLAUDE_SKILL_DIR}/../audit-workflow.md"
Run as the correctness dimension.
Find code whose behavior diverges from what it claims to do. Intent lives in names, signatures, docstrings, comments, caller expectations — behavior contradicting any of them → one is wrong, usually the code. Read for what code does, not what it claims; names, comments, and diff messages prime confirmation bias toward the claimed intent.
High-yield patterns:
< vs <= against length)|| vs &&, missing De Morgan flip)Scope: producing the wrong answer w/ no error. Distinguish from audit-error-handling (errors that vanish — swallowed, unobserved).
<fix_gate> Auto-fix only where intent is pinned — by name, signature, docstring, or caller pattern. The split decides who fixes a divergence, never whether it gets reported. </fix_gate>
npx claudepluginhub jhostalek/dotclaude --plugin jhostalek-skillsGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.