sagargupta16/debug-triage
plugins/debug-triage/skills/debug-triage/SKILL.md
Use when triaging a pasted error, stack trace, or terminal transcript. Activates on "debug this", "fix this", "why is this broken", or when a user pastes red terminal output. Produces a tight cause-fix-test report, not a lecture.
$ install --global
skillsauthnpx skillsauth add sagargupta16/claude-skills debug-triageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 14, 2026, 5:01 AM165.0s1 file scanned
SKILL.md
- name:
- debug-triage
- description:
- Use when triaging a pasted error, stack trace, or terminal transcript. Activates on "debug this", "fix this", "why is this broken", or when a user pastes red terminal output. Produces a tight cause-fix-test report, not a lecture.
- allowed-tools:
- Read Grep Glob Bash(git log:*) Bash(git blame:*) Bash(git diff:*)
debug-triage
When to activate
- User pastes a terminal or PowerShell transcript containing an error.
- User pastes a stack trace.
- User says "debug", "fix this", "why is this broken", "what's going on here".
Do NOT activate for refactoring requests, feature work, or general code review -- those are separate tasks.
Steps
- Parse the actual error. Read stack traces bottom-up. The top frame is usually the symptom; the root cause is deeper in the stack or earlier in the log. Ignore generic first lines like "Traceback (most recent call last):" or "Uncaught Error".
- State the likely cause in one sentence. Not a paragraph. "Null dereference on
user.profilebecause the auth middleware returnsnullfor unverified emails." - Propose the fix as a diff or command. Not prose. Either a code snippet showing before/after, or the exact shell command to run.
- Name a regression test. Where it would live (
tests/auth/email_verify_test.py), and what assertion would catch this bug next time. One line. - Flag sibling updates. If the fix changes behavior documented in README, CHANGELOG, or any doc file, list them. If not, say "none".
Rules
- Don't ask the user to reformat the paste. Parse whatever they gave you.
- Fix first, explain if asked. Don't narrate what the error means at length.
- Ambiguous errors: if 2+ causes are equally likely, pick the likeliest and say so in one line. Do not dump all possibilities unless asked.
- Recent changes are suspect. Run
git log -5 --oneline -- <file>on the failing file. If a recent commit touched the failing line, mention it. - Environment first. If the error looks like it could be environmental (missing env var, wrong Node/Python version, CRLF line endings, path with spaces), check the environment before hypothesizing code bugs.
Output
Cause: <one line>
Fix: <diff or command>
Regression test: <path + what it asserts>
Siblings to update: <list or "none">
No preamble. Lead with Cause:.
Related Skills
sagargupta16/starter-session-audit
testing
VerifiedTrustedCommunity
Use when the user asks to audit a session for uncaptured learnings. Activates on "audit this session", "session audit", "what did we miss", "end of session check", or "/starter-session-audit". Scans the conversation for corrections, preferences, decisions, and new context, then proposes where to save each.
4SKILL.mdUpdated May 23, 2026
sagargupta16/repo-polish
testing
VerifiedTrustedCommunity
Use when setting up new repositories, auditing existing ones, or preparing repos for public visibility. Generates .gitignore, .env.example, README, and LICENSE files. Detects committed secrets and flags security issues.
4SKILL.mdUpdated May 23, 2026
sagargupta16/renovate-triage
tools
VerifiedTrustedCommunity
Use when triaging open Renovate PRs across your own repos into merge / close / defer. Activates on "renovate triage", "review dep PRs", "monthly deps", or on the 1st of a month if deps are grouped monthly.
4SKILL.mdUpdated May 23, 2026
sagargupta16/refactoring
development
VerifiedTrustedCommunity
Use when restructuring code without changing behavior -- extracting functions, renaming, moving files, reducing duplication, migrating between patterns (JS to TS, CJS to ESM), or addressing code smells. Covers safe refactoring workflows for any language.
4SKILL.mdUpdated May 23, 2026