explain-code
Gives guidelines on how to explain code with call graphs and pseudocode. Invoke this when creating code explanations. Common user requests: - "Explain {feature or function}" - "Show me how {feature} works" - "C...
Discover Testing & security skills, compare source repositories and read the instructions for each workflow.
Gives guidelines on how to explain code with call graphs and pseudocode. Invoke this when creating code explanations. Common user requests: - "Explain {feature or function}" - "Show me how {feature} works" - "C...
Write solution options documents to evaluate and compare different technical approaches with trade-off analysis Common user requests: - "Evaluate options for [problem]" - "Compare [solution A] vs [solution B]"...
Refine an implementation
Get alternative perspectives on a plan
Guidelines for automated and manual verification of code changes. When to use: - After making code changes to ensure correctness As part of the implementation workflow
Use when executing implementation plans from planning phase to verified completion
tbd
Analyse and review a pull request
Distill learnings into improvements for the skills and AGENTS.md instructions
Guidelines for documenting work in a changelog artefact after implementing and verifying work
Refine a plan
Create hierarchical, bottom-up "layered summaries" by generating `AGENTS.md` files per directory in a subtree (e.g., `reth/crates/engine`). Deep directories summarize files and key APIs; parent directories roll...
Pack repositories with Repomix for whole-codebase, cross-file analysis. Default to a whole-repo measurement pass, then a filtered whole-repo pack; if it fits under ~1M tokens, stop and hand off to Gemini. Only...
This skill should be used when the user asks to "find where X is defined", "find references to X", "where is X used", "locate the definition of", "where is the class/function/method", "jump to definition", "fin...
Converts "AI" comments in local files into Github PR review comments
Generate and edit images using nanobanana CLI with Google Gemini API. Use for creating images, slides, banners, and visual content from text prompts.
Design system for Daily Writing Friends app. MUST use when doing ANY UI work including components, pages, buttons, forms, styling, Tailwind CSS, dark mode, theming, layouts, cards, inputs, or visual changes. En...
Use when passing callbacks to custom hooks, fixing react-hooks/exhaustive-deps warnings, or debugging unexpected re-renders in React components.
Use when creating or modifying React components (.tsx files). Enforces component structure, import order, and hooks patterns.
PR stacking workflow for breaking large features into smaller, dependent PRs. Use when planning multi-step features, creating dependent branches, or rebasing stacked changes.
Use when user explicitly asks to refactor code, or when test coverage is requested for untested code with side effects. Enforces Functional Core Imperative Shell pattern extraction before any changes.
Use when writing or modifying any code. Enforces naming conventions, function design, and code clarity principles.
Use when writing tests, adding coverage, implementing business logic, or building features with TDD. Enforces output-based testing of pure functions only - never test imperative shell directly.
Use when needing to check PR review comments on current branch, before addressing reviewer feedback, or when asked to fetch/review PR comments
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.