All authors
Claude Skills by netanelavr
github.com/netanelavr17 skills0 installs2 views
- Kit Audit MetricsKeep aggregate data work honest — define the question, trace every number to a query, separate fact from interpretation. Use for counts, rates, trends, funnels, reports, or “why did metric X move”.Votes: 0GitHub stars: 6
- Kit Audit SkillsAudit this repo’s skills and rules for overlap, contradiction, stale names, catalog drift, and employer/proprietary leakage. Use after adding, renaming, or removing a skill or rule, or when the kit feels too large.Votes: 0GitHub stars: 6
- Kit Capture LessonTurn a correction into a short written rule so it does not repeat. Use after steering, a repeated bug class, or “remember this”.Votes: 0GitHub stars: 6
- Kit Challenge DesignStress-test a plan or design against domain language, docs, and code. Ask hard questions one at a time. Update CONTEXT.md and ADRs as decisions crystallize. Use when you already have a draft plan or spec and want to find gaps before implementation.Votes: 0GitHub stars: 6
- Kit Check BlastFind what a change could break beyond the diff, and prove the one fact that makes it safe by running real code. Use before shipping a small diff you don’t fully trust.Votes: 0GitHub stars: 6
- Kit Create PrCommit changes and create a pull request with proper formatting. Use when ready to publish work for review.Votes: 0GitHub stars: 6
- Kit Debug ProdInvestigate production bugs using logs, traces, error trackers, and metrics. Use when the user reports errors, user/session/trace IDs, timeframes, or status codes. Requires connected tools and/or a team `wire-observability.md`.Votes: 0GitHub stars: 6
- Kit DecisionsKeep a short living decision log for one large feature. Use while building it, before continuing the work, or when a reviewer needs the history.Votes: 0GitHub stars: 6
- Kit ExplainProblem / Solution / How it works plus one compact mermaid for a PR or short HLD. Use to explain a change — not for ASCII brainstorm boards or full design grilling.Votes: 0GitHub stars: 6
- Kit Learn RepoLearn an unfamiliar codebase — purpose, layout, how to run/test, safe change points. Use when joining a repo, switching projects, or before the first change in a new area.Votes: 0GitHub stars: 6
- Kit MinimizeFind the smallest useful path to an engineering outcome. Use for minimal PR, least diff, 80/20, or anti-over-engineering.Votes: 0GitHub stars: 6
- Kit Optimize ContextAnalyze always-on agent context across coding hosts (Cursor, Claude Code, Codex, Gemini CLI, etc.) and suggest token reductions. Use when sessions feel heavy before you type anything.Votes: 0GitHub stars: 6
- Kit PlanAlign on a buildable concept, then wait for explicit approval before coding. Use for complex or fuzzy work — includes three ticket readings when the ask is ambiguous.Votes: 0GitHub stars: 6
- Kit ProveRequire live proof for any “works / tested / validated” claim — CLI, raw JSON/logs, timestamps, or a real runtime path. Use when verifying a fix, smoke, or “validate it works”. Not for stripping a finished diff or design debate.Votes: 0GitHub stars: 6
- Kit ReviewReview a branch or PR - author self-check (changed files only) or reviewer second-pass (architecture + diff). Use before publish or when reviewing someone else's PR. Modes are author or reviewer.Votes: 0GitHub stars: 6
- Kit Triage CommentsTriage PR review comments — choose batch (collect/classify/approve as a set) or one-by-one walkthrough with the user before fixing. Use after review feedback lands.Votes: 0GitHub stars: 6
- Kit Strip DiffRemove extras from a finished diff. Use when the outcome already works and the diff still has unused additions, extra instruction lines, or format-only hunks.Votes: 0GitHub stars: 6