Menu
SkillsMP has collected 61 skills from fallow-rs/fallow. Open a skill to review its source and details.
Showing 40 of 61 collected skills.
Audit Fallow for unnecessary code, misleading tests, redundant abstractions, avoidable copying, and stale maintenance guidance. Use for a requested slop audit or deep cleanup pass.
Audit Fallow for unnecessary code, misleading tests, redundant abstractions, avoidable copying, and stale maintenance guidance. Use for a requested slop audit or deep cleanup pass.
Codebase intelligence for TypeScript and JavaScript. Static analysis reports changed-code risk, cleanup opportunities, duplication, circular dependencies, complexity hotspots, architecture boundaries, design-system drift, feature flags, and opt-in security…
Codebase intelligence for TypeScript and JavaScript. Static analysis reports changed-code risk, cleanup opportunities, duplication, circular dependencies, complexity hotspots, architecture boundaries, design-system drift, feature flags, and opt-in security…
Codebase intelligence for TypeScript and JavaScript. Static analysis reports changed-code risk, cleanup opportunities, duplication, circular dependencies, complexity hotspots, architecture boundaries, design-system drift, feature flags, and opt-in security…
Review fallow's GitHub Action, shell scripts, jq filters, annotations, review comments, and workflow integration. Use when changes touch action/, action.yml, GitHub review formatting, or CI shell/jq behavior.
Review fallow's GitLab CI integration, scripts, jq filters, MR comments, and report formatting. Use when changes touch ci/ or GitLab-specific output behavior.
Research, implement, test, document, and review a Fallow feature, fix, refactor, or repository improvement. Use when asked to build or change Fallow.
Prepare local changes for review with an intentional commit, push, and ready PR for fallow. Use when the user wants to publish work, open a PR, or turn local changes into a reviewable branch.
Perform Fallow's comprehensive pre-merge review. Use after implementation or when asked to review a branch, pull request, or diff.
Review fallow's GitHub Action, shell scripts, jq filters, annotations, review comments, and workflow integration. Use when changes touch action/, action.yml, GitHub review formatting, or CI shell/jq behavior.
Review fallow's GitLab CI integration, scripts, jq filters, MR comments, and report formatting. Use when changes touch ci/ or GitLab-specific output behavior.
Research, implement, test, document, and review a Fallow feature, fix, refactor, or repository improvement. Use when asked to build or change Fallow.
Prepare local changes for review with an intentional commit, push, and ready PR for fallow. Use when the user wants to publish work, open a PR, or turn local changes into a reviewable branch.
Perform Fallow's comprehensive pre-merge review. Use after implementation or when asked to review a branch, pull request, or diff.
Triage and address GitHub PR review feedback for fallow, then implement the agreed fixes. Use when the user wants to inspect PR comments, requested changes, or unresolved review threads and act on them.
Use browser automation to review docs pages, preview URLs, rendered output, or web-facing fallow surfaces. Use when the user wants a screenshot-based review, browser smoke test, docs site check, or preview deployment inspection.
Review SARIF, CodeClimate, compact, markdown, badge, and other CI-facing output formats for correctness and integrator expectations. Use when changes affect machine-consumed report formats or CI presentation layers.
Review fallow's human-readable CLI output for scanability, information hierarchy, empty states, and terminal compatibility. Use when changes affect human output, command UX, or text formatting in the CLI.
Investigate and fix failing GitHub Actions checks for this repo or its PRs. Use when the user asks to debug CI failures, broken workflows, failed release jobs, or failing GitHub checks.
Review machine-readable JSON output changes for schema stability, determinism, and downstream usability. Use when changes affect JSON output, result fields, ordering, snapshots, or integration contracts.
Review fallow's LSP server behavior, diagnostics, code actions, code lens, and protocol-facing UX. Use when changes touch crates/lsp or LSP-visible behavior.
Review fallow's MCP server for tool contract clarity, output stability, and agent usability. Use when changes touch crates/mcp or AI-agent integration surfaces.
Review Rust code changes in fallow for correctness, performance, cache-friendly design, and project conventions. Use when changes touch Rust crates such as config, types, extract, graph, core, cli, lsp, or mcp.
Triage a GitHub issue against the current fallow codebase and determine validity, priority, scope, and likely implementation shape. Use when the user asks to triage an issue, assess a bug report, or evaluate an enhancement request.
Review fallow's VS Code extension behavior, activation, commands, views, downloads, and LSP-client integration. Use when changes touch editors/vscode.
Triage and address GitHub PR review feedback for fallow, then implement the agreed fixes. Use when the user wants to inspect PR comments, requested changes, or unresolved review threads and act on them.
Use browser automation to review docs pages, preview URLs, rendered output, or web-facing fallow surfaces. Use when the user wants a screenshot-based review, browser smoke test, docs site check, or preview deployment inspection.
Review SARIF, CodeClimate, compact, markdown, badge, and other CI-facing output formats for correctness and integrator expectations. Use when changes affect machine-consumed report formats or CI presentation layers.
Review fallow's human-readable CLI output for scanability, information hierarchy, empty states, and terminal compatibility. Use when changes affect human output, command UX, or text formatting in the CLI.
Investigate and fix failing GitHub Actions checks for this repo or its PRs. Use when the user asks to debug CI failures, broken workflows, failed release jobs, or failing GitHub checks.
Review machine-readable JSON output changes for schema stability, determinism, and downstream usability. Use when changes affect JSON output, result fields, ordering, snapshots, or integration contracts.
Review fallow's LSP server behavior, diagnostics, code actions, code lens, and protocol-facing UX. Use when changes touch crates/lsp or LSP-visible behavior.
Review fallow's MCP server for tool contract clarity, output stability, and agent usability. Use when changes touch crates/mcp or AI-agent integration surfaces.
Review Rust code changes in fallow for correctness, performance, cache-friendly design, and project conventions. Use when changes touch Rust crates such as config, types, extract, graph, core, cli, lsp, or mcp.
Triage a GitHub issue against the current fallow codebase and determine validity, priority, scope, and likely implementation shape. Use when the user asks to triage an issue, assess a bug report, or evaluate an enhancement request.
Review fallow's VS Code extension behavior, activation, commands, views, downloads, and LSP-client integration. Use when changes touch editors/vscode.
Iteratively review and improve a Fallow user-facing surface across representative real-world projects until the panel has no blocking concerns.
Iteratively review and improve a Fallow user-facing surface across representative real-world projects until the panel has no blocking concerns.
Iteratively reduce Fallow binary size using cargo-bloat and release-build measurements while preserving features, performance, and compatibility.