All authors
Claude Skills by alkofu
github.com/alkofu18 skills0 installs52 views
- Agent CreatorCreate new AI agents or modify existing agents in this repository. Use when users want to create a new specialized agent, update an existing agent definition, add agent documentation, or understand the agent creation process.Votes: 0GitHub stars: 3
- Bash Code QualityDefensive coding standards for bash scripts authored as deliverables. Apply when writing or editing any `.sh` file or a script whose first line is a bash shebang — even when the user does not ask for best practices explicitly.Votes: 0GitHub stars: 3
- Code ReviewDefines the high-signal review contract for code and diff reviews. Use whenever the user asks for a code review, PR review, diff review, asks to review a pull request, asks "is this code OK to merge", asks to identify issues in a changeset, or invokes a `/review` command — even when the user does not explicitly say "skill". This skill determines what qualifies as a reportable finding, what does not, and how findings are structured and validated before being reported. Invoke it before surfacin...Votes: 0GitHub stars: 3
- Commit Message GuideGuide for creating well-structured conventional commits. Use when creating git commits, drafting commit messages, or reviewing commit message quality.Votes: 0GitHub stars: 3
- Doc ReviewMethodology for detecting documentation gaps in a codebase, used during gap-analysis phases to produce a structured, severity-tiered list of missing or inaccurate user-facing documentation.Votes: 0GitHub stars: 3
- File OrganizationGuide for sensible file and module organization. Use when designing file structure for a new feature, deciding whether to split or merge files, refactoring a large file, evaluating whether a new file is justified, deciding whether to create a new directory, choosing where test files should live, or naming a new directory.Votes: 0GitHub stars: 3
- Open Pull RequestREQUIRED for all pull requests. Always use when opening PRs, creating merge requests, or executing gh pr create / glab mr create commands. Enforces conventional branch names and conventional-commit PR titles.Votes: 0GitHub stars: 3
- Skill CreatorCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Votes: 0GitHub stars: 3
- Task ObserverCapture lightweight observations about friction, surprises, or repeated mistakes during a Claude Code session, so they can be reviewed later and turned into skill improvements. Use whenever you notice a pattern worth remembering — confusing instructions in a skill, a workaround you had to invent, a step that should be automated, or behaviour that contradicted a skill's guidance. Always log when you correct yourself or the user corrects you on something a skill should have prevented.Votes: 0GitHub stars: 3
- Validate Before PrREQUIRED before opening any pull request. Always invoke when about to open a PR, create a merge request, push for review, or run pre-PR checks. Runs lint and format checks as a gate before PR creation.Votes: 0GitHub stars: 3
- Write Reliable TestsGuide for writing reliable, deterministic automated tests. Use when writing new tests for a feature or bug fix, reviewing or refactoring existing test code, creating setup and teardown logic, choosing between unit/integration/e2e testing, designing test fixtures or factories, troubleshooting flaky tests, or writing mocks and stubs. Apply this skill whenever test code is being authored or evaluated, even if the user does not explicitly ask for test quality guidance.Votes: 0GitHub stars: 3
- ClarifyFront-loaded task intake: before any planning, do a short code scan, restate the task, and ask every clarifying question in one batch so the user answers once and the rest of the delivery runs without check-ins. Produces a Task Brief (objective, scope, answers, assumptions, code pointers) that planning starts from. Use at the start of any constructive task whose goal, scope, or done-criteria could reasonably be read more than one way — in a plain session, inside `wayblade`, or as the methodol...Votes: 0GitHub stars: 3
- Docs WritingStyle and workflow for writing or updating project documentation — READMEs, architecture and design docs, ADRs, API references, and docstrings. Documents intent, constraints, and decisions instead of narrating readable code, and points to code locations rather than shadowing them in prose. Use whenever creating or editing user-facing docs, updating docs after a code change, or deciding how much to explain — in a plain session, inside `wayblade`, or as the methodology preloaded into the Quill ...Votes: 0GitHub stars: 3
- Evaluate RulesGrade AI-agent instruction files — CLAUDE.md, AGENTS.md, .claude/rules/*.md, agent definitions (agents/*.md), skills (SKILL.md), and reference files — against a rule-writing rubric, and report pass/warn/fail per criterion with quoted evidence and concrete rewrites. Use when the user asks to evaluate, audit, review, grade, lint, or tighten a CLAUDE.md, a rules file, an agent prompt, or a skill, or asks whether an instruction "should be a rule", "is in the right place", or "is too long". Read-o...Votes: 0GitHub stars: 3
- Implementation DisciplineDiscipline for turning a task or plan into working code: minimal diffs, matching existing codebase patterns, incremental verification, and a three-attempt escalation limit. Use when implementing a feature, fix, or plan step that modifies code — in a plain session, inside the `wayblade` delivery flow, or as the methodology preloaded into the Bitsmith agent. Apply even for small changes when correctness and diff size matter.Votes: 0GitHub stars: 3
- InvestigationEvidence-first, read-only method for open-ended "why is this broken?" questions: restate the symptom, gather code and runtime evidence (logs, metrics, Kubernetes state via available MCP tools), form 1-3 grounded hypotheses, test them read-only, and produce a Diagnostic Report with root cause or an explicit "inconclusive". Use when a bug, failure, or unexpected behavior has no known cause yet — before planning or fixing — in a plain session, inside `wayblade`, or as the methodology preloaded i...Votes: 0GitHub stars: 3
- PlanningMethodology for turning a clear task into an actionable, verifiable work plan before implementation: start from a `clarify` Task Brief (or an already-clear request), research the codebase, ask the user only when there is a real fork between implementation approaches, write 3-6 atomic steps with behavioral acceptance criteria, run a pre-submission checklist, and ask for plan approval only when the work is complex. Use when a task is multi-step, cross-cutting, or risky enough that a plan should...Votes: 0GitHub stars: 3
- WaybladeManually-invoked delivery-contract skill. A single continuous Claude Code context owns an entire delivery end-to-end — clarify, plan, implement, debug, validate, docs, commit/push, PR — delegating only for the mandatory Ruinor review and for specialists on explicit request. Use when one session should carry a whole change without full multi-agent orchestration.Votes: 0GitHub stars: 3