Loading...
Loading...
Found 37 Skills
Generate a map of all files relevant to a task before making changes
Update documentation after code changes. Use when adding features, changing keybindings, modifying config options, or updating TUI behavior. Automatically finds and updates relevant documentation files (README, recipes, help text).
Keep README files current with project changes. Use when project structure changes, features added, or setup instructions modified. Suggests README updates based on code changes. Triggers on significant project changes, new features, dependency changes.
Verifies code changes by running tests and generation scripts
Lightweight workflow for straightforward changes — plan → implement → optional PR. Direct-commit by default; synthesize is opt-in via synthesisPolicy or a runtime request_synthesize event. Use for trivial fixes, config tweaks, single-file changes, or exploratory work that doesn't warrant subagent dispatch or two-stage review. Triggers: 'oneshot', 'quick fix', 'small change', or /oneshot.
Refresh AI's understanding of code. Use this skill when the user mentions terms like "refresh", "re-understand", "refresh cache", "reload", etc. This skill compares all modified files, re-reads and understands the code that may have been modified by humans, ensuring that the AI's context is synchronized with the latest code state.
Use when completing development phases or branches to identify and update CLAUDE.md or AGENTS.md files that may have become stale - analyzes what changed, determines affected contracts and documentation, and coordinates updates
Audit test coverage for code changes. Identifies untested logic and provides specific test recommendations. Read-only analysis. Use before PR or after implementation. Triggers: review coverage, check tests, test coverage, are tests adequate.
Use when the user wants to verify their understanding of a branch's code changes by being quizzed on runtime behavior, assumptions, failure points, and edge cases instead of just reading diffs
Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.
Contribute changes to the Feynman repository itself. Use when the task is to add features, fix bugs, update prompts or skills, change install or release behavior, improve docs, or prepare a focused PR against this repo.
Use when developing a new feature, fixing a bug, or making significant code changes - guides the full cycle from planning through verified commit with expert review