All authors
Claude Skills by gaurav8936
github.com/gaurav893617 skills0 installs0 views
- Second OpinionReview a change, a plan or a document as an independent second agent — correctness first, then risk, then simplicity — with every finding tied to a file and line and a severity.Votes: 0GitHub stars: 2
- Show The EvidenceBack every claim in a report with something the reader can open — a file and line, a commit, a command with its output, a screenshot — and label anything unverified as a guess.Votes: 0GitHub stars: 2
- Test FirstWrite the failing test that proves the change is needed, watch it fail for the right reason, then write the smallest code that makes it pass, then tidy up with the tests green.Votes: 0GitHub stars: 2
- Agent RoutingChoose the agent and model for a piece of work by its kind (research, design, code, review, test, docs, chore), the remaining capacity of each seat, and the rule that a reviewer is never the author. Holds the routing.json and roles.json One Roof reads.Votes: 0GitHub stars: 2
- Bounded LoopsMake any repeated or self-paced agent work safe — a written goal, a machine-checkable stop condition, a cap on attempts and time, a report after every round, and a clean way to interrupt.Votes: 0GitHub stars: 2
- Fan Out Or NotDecide whether a job should be split across several parallel agents or sub-agents, or done inline in one session — using independence, size, review cost and file overlap as the tests.Votes: 0GitHub stars: 2
- Parallel WorktreesRun several agents on one repository at once without collisions — a git worktree and branch per task, non-overlapping file claims, and landing one task at a time with tests after each merge.Votes: 0GitHub stars: 2
- Ask Before IrreversibleSort every action into reversible or not, and pause for an explicit yes before anything that deletes data, rewrites shared history, deploys, spends money or reaches other people.Votes: 0GitHub stars: 2
- Keep Secrets OutKeep API keys, tokens, passwords and private data out of code, commits, logs, plans and prompts — check before committing, and know what to do when one leaks.Votes: 0GitHub stars: 2
- Capture GotchasWhen something surprising breaks, write one short note — symptom, cause, fix, how to check — named after the symptom, in the shared gotchas folder, so the next session finds it before repeating the mistake.Votes: 0GitHub stars: 2
- Repo MapWrite or refresh docs/codebase-map.md — what the repository is, how to run it, its entry points, a one-line-per-folder tour, and the invariants that must not break — so any agent can orient in one read.Votes: 0GitHub stars: 2
- Plan ObjectiveTurn an objective into a visible, editable step plan for One Roof — steps, agent and model per step, dependencies, done-when checks and expected cost — written as Markdown plus a oneroof-plan JSON block.Votes: 0GitHub stars: 2
- Write The SpecBefore any code, write a one-page spec — the problem, what done looks like as checks anyone can run, what is out of scope, and the open questions — and get it approved.Votes: 0GitHub stars: 2
- Last CallSession-close ritual — sweep loose ends, move durable facts into the shared docs, write the handoff, and score readiness by counting a checklist. Every step runs, every time.Votes: 0GitHub stars: 2
- Next Session HandoffWrite a paste-ready next-session handoff into the shared docs (git), so any agent — Claude, Codex, Kimi, Hermes — can resume cold from that one file.Votes: 0GitHub stars: 2
- Where Are WeSession-open orientation — read the latest handoff, the shared READ-FIRST and every repo's recent git state, then say in one screen which thread to pick up and the first command.Votes: 0GitHub stars: 2
- Ship DomainPromote finished work from your working branch to staging and then production through the pipeline — pre-flight checks, one promotion per stage, verification after each hop, and a known way back.Votes: 0GitHub stars: 2