All authors
Claude Skills by viacheslav-tronko
github.com/viacheslav-tronko7 skills0 installs8 views
- Concept ExplanationEvidence-bound investigation producing a falsifiable architectural mental model of a code concept, pattern, term, or component in large legacy codebases. Use WHENEVER user asks WHAT/HOW/WHERE about code — /explain, "explain X", "what is X", "how does X work", "trace this concept across layers", "preflight before bug-fix", "build mental model", "architectural overview", "layer-by-layer explanation", "F/B/D-XXX pattern explanation", or pastes a domain term or component name asking what it does ...Votes: 0GitHub stars: 6
- Implementation BlueprintPre-implementation blueprint for AI coding agents on legacy codebases. Use WHENEVER user asks HOW to implement, plan, or design — /howto.implement, /blueprint, "implementation plan / analysis / strategy / approach", "how to implement / add / build / refactor", pastes Jira / user story / RCA / SPEC asking "plan this", or mentions Tree of Thoughts, spec-driven development, Design-by-Contract. Falsification-first, anti-hallucination — Approach #0 baseline + 3+ alternatives, confidence-weighted Y...Votes: 0GitHub stars: 6
- Requirements AnalysisEvidence-bound transformation of vague human requirements (Jira ticket, Confluence page, free text, file path) into AI-ready specifications for coding agents. Use WHENEVER user asks to /distill, "analyze requirements", "clarify task", "vague requirements", "ambiguous AC", "task vs bug", "EARS", "Given-When-Then", "GWT", "AI-ready spec", "prepare spec for implementation", "Open Questions", "INVEST", "MoSCoW", "user story analysis", "acceptance criteria", "steps to reproduce", "expected vs actu...Votes: 0GitHub stars: 6
- Root Cause AnalysisRoot cause analysis for software bugs in large legacy codebases. Use this skill WHENEVER the user asks WHY a bug happens, asks for RCA, mentions root cause analysis, says /bug.why, /bug.investigate, asks "why is this failing", "find the root cause", "trace this exception", "investigate this bug", "post-incident review", or pastes a stack trace, error log, exception, NullReferenceException, SqlException, InvalidOperationException, or asks 5 Whys / Kepner-Tregoe / IS-IS-NOT / fault localization...Votes: 0GitHub stars: 6
- Surgical ImplementationSurgical code-execution skill for AI coding agents on legacy codebases. Use WHENEVER the user asks to IMPLEMENT, CODE, BUILD, APPLY, or FIX from a contract source — IMP / Plan + TASK-NN, RCA report, freeform task, or Jira ticket. Triggers on /implement, /bug.fix, /code, /apply, /fix, "implement this", "code this", "build this", "apply this fix", "fix this bug", "execute the plan", "implement the blueprint", paths like `IMP-*.md`, `PLAN-*.md`, `RCA-*.md` followed by "implement"/"fix"/"apply", ...Votes: 0GitHub stars: 6
- Task VerificationHypothesis-driven task-correctness verification for AI coding agents on legacy codebases. Use WHENEVER user asks to verify, audit, or pre-flight a task artifact (IMP, RCA, Plan, Implementation, Fix, Jira ticket) before submission — /verify, /verify-task, /gate2, "verify this", "verify the RCA", "verify the implementation", "is this fix correct", "double-check my plan", "audit before merge", "pre-flight before PR", "Gate 2 / Pre-Send check", "find what's wrong with my IMP", or pastes RCA-/IMP-...Votes: 0GitHub stars: 6
- White Box TraceWhite-box code-path tracing in two modes. REAL — empirical verification of completed code via CFG/MPC traversal, Counterfactual + optional Live Mutation Testing, PBT hook, Tandem-FL on FAIL, Killer-Path-First, FAIL-FAST, persistent index-prefixed JSONL trace with resume + confidence decay, Reviewer Agent re-rank, Reflexion lessons, structured fix_proposal + repro_snippet. VIRTUAL — pre-implementation falsification of RCA reports / Implementation Blueprints / Plans / freeform ideas via Planner...Votes: 0GitHub stars: 6