All authors
Claude Skills by genai-io
github.com/genai-io10 skills0 installs2 views
- Code ReviewReview changed code for correctness bugs — logic errors, nil/error handling, concurrency, resource leaks, edge cases, broken invariants. Reports findings first, ordered by severity, then fixes on request. Scoped to correctness, not quality or style cleanups. Use when the user says "code review", "review my changes", "any bugs", "find bugs", or asks whether a change is correct.Votes: 0GitHub stars: 84
- DebugSystematic debugging that finds the root cause before changing any code — collect symptoms, trace the code path, check what changed, reproduce deterministically, form a testable hypothesis, then fix the cause (not the symptom) and prove it with a regression test. Use when the user reports a bug, a crash, a failing test, or says "debug", "why is this happening", "root cause".Votes: 0GitHub stars: 84
- RefactorRestructure existing code without changing its behavior — extract, rename, inline, split, deduplicate, reshape — with tests holding behavior fixed before and after. Scoped to structure only: no new features, no bug fixes, no behavior changes. Use when the user says "refactor", "clean up the structure", "extract this", "split this file", "untangle", or "restructure".Votes: 0GitHub stars: 84
- SimplifyReview changed code for reuse, quality, and efficiency, then clean up what you find — duplicated logic that could reuse an existing helper, hacky or redundant patterns, needless work on hot paths. Quality cleanup only: not bugs (that's code-review) and not behavior-preserving restructuring on request (that's refactor). Use when the user says "simplify", "clean this up", "is there a simpler way", or "tidy the diff".Votes: 0GitHub stars: 84
- TddTest-driven development — write a failing test that names the behavior, watch it fail, implement the minimum to make it pass, then refactor with tests green. Works for new features, bug fixes, and behavior changes. Use when the user says "tdd", "test-first", "write tests first", or wants a change built test-first.Votes: 0GitHub stars: 84
- QaRegression test a San feature by name. Looks for a feature doc in docs/reference/ or docs/packages/2-feature/, runs automated Go tests and interactive tmux tests, then produces a pass/fail report. Use this skill when the user says "qa", "regression test", "test feature X", "verify feature", or references a feature name like "agent", "cli-startup", "loop".Votes: 0GitHub stars: 84
- ReleaseCreate a new versioned release with changelog. Bumps version in code, updates CHANGELOG.md, commits, tags, and pushes using the repository release flow. GitHub Actions creates the release and uses only the current changelog section as release notes. Use when the user says "release", "cut a release", "bump version", "new release".Votes: 0GitHub stars: 84
- GuidesA skill is a markdown file the model can be made aware of, or that the user can invoke via a slash command. Skills are the simplest extension surface in San — one file, no install step. For the system-level design see [`packages/skill.md`](../packages/2-feature/skill.md) and [`concepts/extension-model.md`](../concepts/extension-model.md).Votes: 0GitHub stars: 84
- 2 FeatureLoads markdown-defined skills from user / project / plugin scopes, tracks their enable state, and renders the active-skills directory that the harness attaches to user messages via the `skills-directory` reminder (see [`concepts/harness-channels.md`](../../concepts/harness-channels.md)).Votes: 0GitHub stars: 84
- HelloA simple greeting skill for plugin testingVotes: 0GitHub stars: 84