All authors

Claude Skills by tusharsrivastava
github.com/tusharsrivastava15 skills0 installs0 views
- Commit BlocksSplits a working tree into conventional commits, each with one reason, and checks that each commit passes the gate on its own. Use when work is ready to commit.Votes: 0GitHub stars: 13
- Cookbook WritingMethod and style for a cookbook tutorial chapter. One story, each term taught as a plain idea first, reading levels checked by a script. Use when you write or review a tutorial or onboarding document.Votes: 0GitHub stars: 13
- Debug RcaRoot-cause method with the mcp-debugger (breakpoints, stack, variables), then a failing regression test and an RCA with a Fix spec. Use when a failure has a cause that is not clear, or the user says debug, root cause, RCA or step through it.Votes: 0GitHub stars: 13
- GitignoreCreates or refreshes .gitignore from gitignore.io templates and keeps the project block. Use when the user asks for a .gitignore, or the stack of the repository changes.Votes: 0GitHub stars: 13
- Goal LoopFix rounds toward one measurable goal on N failing scenarios (bench cases, end-to-end cases, evaluation cards). Classifies each failure, fixes in lanes, merges once, measures again. Use when the user says make these pass, or a bench is red.Votes: 0GitHub stars: 13
- HandoffRecords and prunes the handoff file, the state that carries between sessions. Use at the end of a session, before a context reset, or when the user asks where things stand.Votes: 0GitHub stars: 13
- InitSets up a repository for shark one time. Adds the missing template sections to CLAUDE.md or AGENTS.md with values from the repository, the Working rules block, one session start rule, and the shark:asd-ste100 output style. Keeps existing text. Use when the user says init or set up shark, or after a kit update.Votes: 0GitHub stars: 13
- Lead MergeMethod for the long-running lead who merges many patch or lane branches into one integration branch from a queue, with one gate for each batch and a merge log. Use for a merge queue.Votes: 0GitHub stars: 13
- Merge AuditRead-only audit of each merge of the lead against the round contract and the invariants. Finds merges that pass the tests but lose a rule. Use next to a lead merge.Votes: 0GitHub stars: 13
- OperatorSession harness. Does small, clear work directly and keeps each fix in scope. For larger work it chooses a mode (feature, review, debug), briefs agents and checks their reports. Use at the start of each session, and when the user says operator, split this work, run lanes or brief an agent.Votes: 0GitHub stars: 13
- Patch FanoutPorts many independent patch units in parallel, one shark:code-writer for each unit, from an audit or a decision list. Use after shark:port-audit, or for a batch of small independent fixes.Votes: 0GitHub stars: 13
- Port AuditFinds each rule that a refactor or a rebuild lost, by a static audit of the deleting commits against production. Use before a rewrite replaces production code, or when tests stay green but behaviour is lost.Votes: 0GitHub stars: 13
- System DesignDesign and review of the structure of a system with SOLID, design patterns, contracts and an invariant catalogue. Use for a design choice, a module boundary, a refactor plan or a design review.Votes: 0GitHub stars: 13
- Code AuthoringThe rules for writing production code and tests that shark:code-writer and shark:lead-engineer share - regression safety with a test baseline, scope, test first, introspectability, logging and comments. Use before you write or correct code.Votes: 0GitHub stars: 13
- Solution SpecCloses a spec before shark:code-writer builds it - the guards on the path, the input classes, the operations on the state, a behaviour table with one test for each row, the decided questions, and an adversarial check. Use after a root cause analysis, or before a round of code-writer lanes.Votes: 0GitHub stars: 13