utsabpanta
- 20 skills
- 0 followers
- 10 hours ago last updated
- ▌ Adr · utsabpantaThis skill should be used when the user types /adr, says they are making an architecture decision, asks to write an ADR, or wants a technical tradeoff recorded for the future.
- ▌ Tldr · utsabpantaThis skill should be used when the user types /tldr, or asks for a three-bullet summary of a file, a function, or a diff.
- ▌ Retro · utsabpantaThis skill should be used when the user types /retro, is running a team retrospective, or asks to reflect on a sprint or a finished project.
- ▌ 5 Whys · utsabpantaThis skill should be used when the user types /5-whys, or asks for a root-cause analysis of a recurring problem, an outage, or a repeated failure.
- ▌ Harden Setup · utsabpantaThis skill should be used when the user asks to "audit my Claude Code setup", "check my hooks", "is my .claude config safe", "harden Claude Code for my team", or mentions that a hook does not seem to be firing or blocking. It finds configuration that looks correct but silently does nothing.
- ▌ Standup · utsabpantaThis skill should be used when the user types /standup, asks for standup notes, or asks what they did yesterday.
- ▌ Incident · utsabpantaThis skill should be used when the user types /incident, says they have a production incident or outage, or asks for help writing a postmortem after one.
- ▌ Test Gen · utsabpantaThis skill should be used when the user types /test-gen, asks to write tests for a file or function, or says their code lacks coverage.
- ▌ Tradeoff · utsabpantaThis skill should be used when the user types /tradeoff, or asks to compare two or more technical options, libraries, or approaches against each other.
- ▌ Hook Authoring · utsabpanta bundleThis skill should be used when the user asks to "write a hook", "add a Claude Code hook", "make Claude stop doing X automatically", "block a tool call", or wants a hook tested. It covers choosing the event, the exit-code and JSON contract, and shipping the hook with a test.
- ▌ Blame Why · utsabpantaThis skill should be used when the user types /blame-why, or asks why a specific line of code exists, who wrote it, or what a line was for.
- ▌ API Design · utsabpantaThis skill should be used when the user types /api-design, is adding or changing an HTTP or RPC endpoint, or asks for a review of an API surface before it ships.
- ▌ Debug Help · utsabpantaThis skill should be used when the user types /debug-help, says something is broken or behaving unexpectedly, or is stuck on a bug and guessing at fixes.
- ▌ Rubber Duck · utsabpantaThis skill should be used when the user types /rubber-duck, or says they want to think a problem through out loud without being handed an answer.
- ▌ Permission Policy · utsabpantaThis skill should be used when the user asks to "set up permissions for Claude Code", "stop Claude asking me every time", "lock down Claude for my team", "what should I allowlist", or is choosing between permission modes. It produces a permission policy calibrated to the repo, not a generic list.
- ▌ What Changed · utsabpantaThis skill should be used when the user types /what-changed, or asks what changed since a branch, tag, date, or commit.
- ▌ Refactor Plan · utsabpantaThis skill should be used when the user types /refactor-plan, describes a large refactor, or asks how to split a change that has grown too big to review.
- ▌ Release Notes · utsabpanta bundleThis skill should be used when the user asks to "write release notes", "update the changelog", "what changed in this release", "cut a release", or mentions CHANGELOG.md. It mines a commit range and writes for either a customer audience or a Keep a Changelog file.
- ▌ Dependency Check · utsabpantaThis skill should be used when the user types /dependency-check, is about to add a package, or asks whether they should pull in a library.
- ▌ Migration Review · utsabpantaThis skill should be used when the user types /migration-review, is about to ship a database schema change, or asks whether a migration is safe to run against production.