Loading...
Loading...
Found 18 Skills
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals
Run a dev task — "run xxx", "change xxx", "build xxx", "implement xxx", or a spec or set of tickets to implement. To find and fix a bug for a given error, use the fix skill instead.
SOLID and IoC design review. Use when the user asks to check SOLID, judge the design quality of a class or namespace, or when another skill needs a design review of the code it touched.
Perform an independent, evidence-grounded review of git diffs against requested specifications, architectural invariants, and code standards. Use when reviewing pull requests, inspecting code changes before merge, auditing diffs for regressions, or performing pre-commit sanity reviews — even if the user does not explicitly say "fable-review" (e.g. "review this diff", "check this PR", "critique my changes", "code review this branch"). Do NOT use for implementing fixes directly (use fable-tdd/fable-execute) or executing tests (use fable-verify).
Review changes since a fixed point along five independent axes: repository standards, originating spec, performance, observability, and accessibility. Use for branches, pull requests, work in progress, or requests to review since a commit, branch, tag, or merge-base.
Runs a comprehensive project fitness review combining architecture, security, reliability, testing, performance, algorithms, data, accessibility, process, and maintainability analysis. Use when the user says "full review", "comprehensive review", "project fitness", "review everything", or wants all review skills run on current changes before shipping.