All authors
Claude Skills by Xnadir
github.com/Xnadir10 skills0 installs11 views
- GradersNo description providedVotes: 0GitHub stars: 5
- Answer FirstPuts the answer, result, or next action in the first sentence and cuts preamble, restated questions, recaps, and sign-offs. Use when answering a direct technical question, reporting the result of a task, or when the user asks for shorter, more direct, or less verbose replies.Votes: 0GitHub stars: 5
- Secure DefaultsApplies secure defaults when writing code that handles untrusted input, such as SQL queries, shell commands, file paths, HTML output, redirects, auth, secrets, or deserialization. Use when writing or changing code in web handlers, CLIs, database access, file uploads, or anything that touches user-supplied data or credentials.Votes: 0GitHub stars: 5
- Stdlib FirstSolves small programming problems with the language's standard library, platform features, or already-installed packages before adding a new dependency. Use when writing code that could pull in a package (dates, deep clone, UUIDs, HTTP, arg parsing, formatting, validation), or when the user asks which library to use.Votes: 0GitHub stars: 5
- SurgicalKeeps code changes to the smallest diff that fully solves the request. Use when editing existing code to fix a bug, add a feature, or respond to review, especially in files with unrelated code nearby. Prevents drive-by refactors, reformatting, renames, and "while I'm here" cleanups that make diffs hard to review.Votes: 0GitHub stars: 5
- Bug Hunt ReviewReviews code or a diff for real defects, meaning inputs or states that produce wrong results, crashes, data loss, or security holes, and reports each with a concrete failure scenario. Use when asked to review code, a pull request, a diff, or a change before merge. Leaves out style nitpicks unless asked.Votes: 0GitHub stars: 5
- GrillInterviews the user about an under-specified feature, project, or plan before any code is written, one decision at a time with a recommended answer for each. Use when the user asks to be grilled, interviewed, or questioned about requirements, a plan, or a design before building.Votes: 0GitHub stars: 5
- HandoffWrites a handoff note that lets a fresh agent session or a teammate resume the current task without re-reading the conversation. Use when the user asks for a handoff, summary for later, or context dump, or before ending a long session, switching machines, or clearing context mid-task.Votes: 0GitHub stars: 5
- Prove ItSeparates what was checked from what was only written before a coding task is reported as done. Use when finishing a code change, bug fix, or refactor, and before saying anything is fixed, working, passing, or complete. Pairs each claim with the command and output that backs it, and lists what was not verified.Votes: 0GitHub stars: 5
- Root CauseFinds and fixes the actual cause of a bug instead of patching the symptom at the place it was reported. Use when debugging an error, a failing test, a crash, or wrong output, and when a bug report names one caller, page, or input. Traces the failure back to where the bad state originates and fixes it once there.Votes: 0GitHub stars: 5