GitHub
Skills harvested from GitHub repositories
14810 skills availabletest-setup
This skill scaffolds the automated testing infrastructure for the project. It detects the configured engine, generates t...
ux-design
When this skill is invoked: Three authoring modes exist based on the argument: | Argument | Mode | Output file | |------...
test-helpers
Writing test cases is faster and more consistent when common setup, teardown, and assertion patterns are abstracted into...
test-flakiness
A flaky test is one that sometimes passes and sometimes fails without any code change. Flaky tests are worse than no tes...
tech-debt
Determine the mode from the argument: scan — Scan the codebase for tech debt indicators add — Add a new tech debt entry ...
test-evidence-review
/smoke-check verifies that test files exist and pass. This skill goes further — it reviews the quality of those tests an...
team-ui
When this skill is invoked, orchestrate the UI team through a structured pipeline. Decision Points: At each phase transi...
team-release
Argument check: If no version number is provided: Read production/session-state/active.md and the most recent file in pr...
team-qa
When this skill is invoked, orchestrate the QA team through a structured testing cycle. Decision Points: At each phase t...
team-polish
If no argument is provided, output usage guidance and exit without spawning any agents: Usage: /team-polish [feature or ...
team-live-ops
Argument check: If no season name or event description is provided, output: "Usage: /team-live-ops [season name or event...
team-narrative
If no argument is provided, output usage guidance and exit without spawning any agents: Usage: /team-narrative [narrativ...
team-level
When this skill is invoked: Decision Points: At each step transition, use AskUserQuestion to present the user with the s...
team-audio
If no argument is provided, output usage guidance and exit without spawning any agents: Usage: /team-audio [feature or a...
team-combat
Argument check: If no combat feature description is provided, output: "Usage: /team-combat [combat feature description] ...
story-done
This skill closes the loop between design and implementation. Run it at the end of implementing any story. It ensures ev...
start
This skill writes one file: production/review-mode.txt (review mode config set in Phase 3b). This skill is the entry poi...
sprint-status
This is a fast situational awareness check, not a sprint review. It reads the current sprint plan and story files, scans...
soak-test
A soak test (also called an endurance test) is an extended play session run with specific observation goals. Unlike a sm...
sprint-plan
Extract the mode argument (new, update, or status) and resolve the review mode (once, store for all gate spawns this run...
smoke-check
This skill is the gate between "implementation done" and "ready for QA hand-off". It runs the automated test suite, chec...
skill-test
Validates .claude/skills//SKILL.md files for structural compliance and behavioral correctness. No external dependencies ...
setup-engine
When this skill is invoked: Four modes: Full spec: /setup-engine godot 4.6 — engine and version provided Engine only: /s...
skill-improve
Runs an improvement loop on a single skill: test → fix → retest → keep or revert. --- Read the skill name from the first...