Loading...
Loading...
Found 12 Skills
Map a codebase into a structured vocabulary — surfaces, features, entities, flows, compartments, invariants, tech stack — plus code-health metrics. Produces a JSON map and an interactive local UI. Use whenever the user wants to understand or audit a codebase.
Set up or modernize code-quality tooling for JavaScript and TypeScript projects. Use when creating a project, adding code-health or CI quality checks, making a repository agent-ready, or consolidating dead-code, duplication, architecture, dependency, and changed-code analysis. Do not use for formatting-only, lint-rule-only, or TypeScript type-error tasks. Do not use to run an analysis of a project that is already set up; use the fallow skill for that.
Review code with validated evidence. Use for normal, security, performance, or deep audits of diffs, architecture, data, tests, dependencies, docs, and code health.
Use when reviewing code, pull requests, patches, CLs, diffs, or proposed implementations for engineering quality, code health, design, functionality, tests, maintainability, specialist risk, or approval risk. TRIGGER on "review this PR", "code review", "LGTM?", "approve?", "is this code/diff/change safe to merge/deploy?", and local diff reviews. DO NOT TRIGGER for PR descriptions, PR splitting, author review-feedback responses, or non-code safety questions unless code review is requested.
Real-time structural Code Health via CodeScene MCP — review before edits, verify score deltas after changes, gate commits and PRs. Use when reviewing code quality, refactoring, checking if AI changes degraded a file, or before commit/PR.
Diagnose and fix React Native & Expo codebase health issues. Use when reviewing React Native code, fixing performance problems, auditing accessibility, or improving architecture.
High-level project analysis. Use when asked to analyze, review, or evaluate a project's architecture, structure, and overall health.
Applies Google's engineering practices for strict, health-focused code reviews.
Systematic codebase quality scan for identifying duplication, redundancy, and improvement opportunities. Use when reviewing a repo's architecture, finding refactoring targets, or assessing code health. Triggers: "scan the repo", "find code duplication", "suggest improvements", "code quality review", "is there redundant code", "refactoring plan", "architecture review".
explore — Deep codebase exploration with parallel agents. Use when exploring a repo or discovering architecture.
Technical debt inventory, prioritization, and audit for PHP/Laravel (MySQL) and Node/TypeScript/React projects. Use when assessing code health, identifying refactoring candidates, planning debt paydown, or auditing a codebase for accumulated debt. Triggers on "audit technical debt", "find tech debt", "debt inventory", "what should we refactor first", or tasks involving code health, security debt, performance debt, data debt, observability debt, debt prioritization, or remediation planning.
Set up the Fallow app in Codex after the plugin is installed: check the fallow installation, choose the default analysis scope, run the first analysis, and show the user where the dashboard, the Code Health tab, @Fallow mentions and the config editor are. Use when the user chooses Set up for Fallow in Codex, or asks to onboard or configure the Fallow app. Do not use for setting up lint, format or CI tooling; use fallow-setup for that.