Fetches and processes GitHub pull requests waiting for review. Returns fully formatted markdown with PRs grouped by category (Feature/Bug, Chores, Dependency Updates) and sorted by age. Includes metadata like CI status, review status, size metrics, and viewing history. Use when user wants to see their PR review queue.

Sync and integrate Fever Partners API for plans, reviews, attendees, and venues. Use when implementing Fever data sync, debugging API issues, or building review/analytics features.

Review code changes for FFP project standards including multi-tenant security, British English, architecture patterns, and SOLID principles. Use when reviewing PRs, checking branch changes, or auditing code quality.

Applies best practices for logging, project structure, and environment variable usage specifically to the main application file.

Focuses on routing, CSRF protection, context handling, and template usage within the internal handlers directory.

This rule instructs the AI to make changes file by file, allowing the user to review each change individually.

Edit files locally using built-in tools instead of PowerShell string replacement. 5000% efficiency boost!

Specifies file management guidelines, including including full file paths as comments, updating project structure in AI.MD, and maintaining package.json. This rule ensures organized and well-documente

Defines the file organization structure for TypeScript projects, emphasizing modularity and separation of concerns.

Enforces the use of full file paths when referencing, editing, or creating files in the project. This rule ensures consistency and accuracy in file operations across the entire project.

This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.

Final Approach - the landing sequence. Runs Go Poll with review agents (mission-control, telemetry, flight-director) using Haiku model. Supports A+ skip rule for efficient re-reviews.

Start dev server, generate QA checklist, guide manual verification. Use before creating PR.

Generate income statements, balance sheets, and cash flow statements with GAAP presentation and period-over-period comparison.

Parse and analyze personal financial transaction CSV exports to calculate account totals and generate detailed breakdowns. Use when the user asks to analyze transaction data, generate financial summaries, calculate account balances, or review spending from CSV exports. Supports account grouping (Galicia, Mercado Pago, Quiena, LLC/Relay, HSBC, Crypto), automatic internal transfer detection, and detailed transaction listings.

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

Modern find-and-replace using sd (simpler than sed) and batch replacement patterns. Triggers on: sd, find replace, batch replace, sed replacement, string replacement, rename.

Searches and recommends Claude Code skills and plugins from local database and SkillsMP API. Activates when user asks to find skills, search plugins, get recommendations for PDF/Git/code-review/frontend tools, or requests feature-based tool discovery.

Prepare a GitHub issue branch for PR with quality checks, cleanup, and review recommendations.

Manually complete a phase and update phase.md. Use when you want to manually review/edit phase completion, or when auto-detection didn't trigger.

Best practices for interacting with Firebase services, including security and optimization.

Reviews Rust firmware code for the BVR (Base Vectoring Rover) with focus on safety-critical systems, CAN bus protocol compliance, motor control logic, state machine correctness, and embedded testing patterns. Use when reviewing BVR firmware changes, debugging actuator control, testing motor communication, validating safety mechanisms, checking async patterns, or evaluating control system modifications. Covers watchdog implementation, e-stop handling, rate limiting, VESC motor controller integration, and Tokio async runtime patterns.

Fix bad coding practices identified by audit, following fail-fast principles

Fixes image issues in uncommitted blog posts before publishing.

Diagnose and fix CI/CD failures by analyzing logs, reproducing locally, and applying fixes. Use when CI checks fail on pull requests.

Automatically fixes detekt code quality issues by running detekt --auto-correct iteratively until all auto-correctable findings are resolved

Preview broken wikilinks and spawn autonomous repair agent.

Handle PR review comments by choosing the appropriate response for each comment.

fix-pr-feedback

Address PR review comments by selecting appropriate skills based on modified files. Use when fixing review feedback on pull requests.

'Orchestrate fixing issues found by /review. Handles issue discovery, user confirmation, plan creation, and execution via /implement.'

Verify fix commits address audit findings without new bugs

>

Use when review findings need fixing via subagents - invoked by review-loop after each iteration

Generate comprehensive educational flashcards based on Bloom's Taxonomy methodology (Remember, Understand, Apply, Analyze, Evaluate, Create). Creates structured flashcards with difficulty ratings, detailed explanations, and practice hints. Use when user requests flashcard generation, study cards, review materials, learning flashcards, mentions Bloom's Taxonomy, or provides educational topics for flashcard creation. Activates for study topics, course materials, reference files (.md, .txt, .pdf), or educational content requiring systematic review materials.

flask-reviewer

John Carmack-level implementation review via rp-cli for current branch changes. Use when reviewing code changes, PRs, or implementations. Triggers on mentions of code review, implementation review, or PR review.

Carmack-level plan review via rp-cli context builder + chat. Use when reviewing implementation plans, architecture docs, or design specs. Triggers on mentions of plan review, design review, or architecture review.

Verify plan consistency, generate summaries, maintain plan health. Use for review, verification, summaries, or plan maintenance. Mostly read-only with maintenance operations.

Detect human-oriented content in LLM artifacts. Flags attribution, personas, redundant explanations, marketing language, and decorative elements that waste tokens without improving LLM behavior.

Review Flutter app PRs for bugs, UX issues, performance regressions, missing tests, and readability; include app code, packages/plugins, and CI config. Use when asked to review a Flutter PR, do a Flutter code review, or find bugs in Flutter repositories.

flutter-reviewer

Clean Architecture patterns for Flutter with Riverpod state management. Use when building or reviewing Flutter apps with layered architecture (Domain, Data, Application, Presentation).

View detailed information about a specific uxscii component including metadata, states, props, and ASCII preview. Use when working with .uxm files, when user wants to see, view, inspect, or get details about a .uxm component.

Quick MVP deployment to fly.io for JavaScript (Next.js, RedwoodSDK, Express), Rust (Axum, Rocket), Python (FastAPI), and generic Dockerfiles. Use when deploying applications to fly.io, setting up databases (Postgres, volumes, Tigris object storage), managing secrets, configuring custom domains, setting up GitHub Actions workflows, creating review apps for pull requests, or troubleshooting fly.io deployments. Covers complete deployment workflows from initial setup through production.

Enforce specific directory structure for React and MobX Projects.

Schedule a follow-up reminder for a specific date. Use when user wants to set a reminder to follow up on a project, task, question, or any item. Adds entries to _Followups.md which get pulled into daily notes.

Reorder Foodora orders + track ETA/status with ordercli. Never confirm without explicit user approval. Triggers: order food, reorder, track ETA.

Use when monitoring code quality over time, measuring refactoring impact, tracking if complexity is improving or worsening, or validating technical debt work - tracks complexity metrics across git history identifying improving, stable, or deteriorating files

Describes Form and Actions implementations.