Query this repo's code graph instead of ls/grep/reading files blindly. Use whenever you are understanding the codebase or its architecture, tracing how something works, or searching for a symbol or term; before changing a symbol, to get its blast radius (dependent symbols, tests to run, API surface, and other indexed…
Query this repo's code graph instead of ls/grep/reading files blindly. Use whenever you are understanding the codebase or its architecture, tracing how something works, or searching for a symbol or term; before changing a symbol, to get its blast radius (dependent symbols, tests to run, API surface, and other indexed…
Use this skill when the user is debugging a bug, error, crash, or issue that might be tied to a specific point in time (e.g., "crash from 3 hours ago", "bug in v2.4.1", "last night's deploy"). It guides the agent to reconstruct the historical code state and analyze the bug in that context.
Run or resume an autonomous build/fix loop that iterates plan → implement → evaluate against a user-approved, testable contract until it passes. Use when the user wants an agent loop, wants a task to keep iterating unattended or in the background (e.g. overnight), or wants to resume, check the status of, or cancel a…
An archiving tool for completed software changes. It creates a summary, synchronizes requirements with feature specifications, and checks that related project knowledge has been updated.
A review skill that checks an implementation against its tasks, written requirements, project rules, supporting knowledge, tests, and—when relevant—its design.
Create or refine a DESIGN.md from a public website URL, then use that design system to build and open a standalone HTML page based on either a reference URL or the user's requested page and content. Visually validate the HTML and feed reusable corrections back into DESIGN.md. Use when the user wants a DESIGN.md, an…
Two-party posture — user as director, agent as executor; every fork, tradeoff, or choice surfaced via batched AskUserQuestion with a recommended default. Use when the user invokes /duet, says "ask before" / "pair with me" / "human-in-the-loop", or for aesthetic/architectural/irreversible decisions.
Install a Claude-Code PreToolUse hook that blocks destructive git commands (push variants including force-push, hard reset, force clean, branch -D, checkout/restore overwrites) before Bash runs them. Use when the user wants git safety rails, force-push prevention, or repository-wipe protection.
Investigate a reported bug to root cause, then emit a TDD-shaped fix plan as an issue artifact. Trigger when the user reports a bug, says "triage", asks for issue investigation, or wants a fix plan before code changes.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Operating rules for projects using the AI Development Methodology — markdown + git governance for mixed human/AI-agent teams. Load when working in a repo that follows it, or for any process question: sizing and filing backlog items, what counts as Done (Status/Test fields), the file-lock protocol for parallel agents…
A read-only consistency check for changes to SpecLite’s canonical source files. A canonical source is the main version from which related files, documentation, tests, and packaging data are derived.
★not rated 4 2mo agoA91 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: