flywheel-scan

Scans targeted repository paths for architecture, performance, security, testing, or dependency concerns.

3|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-scan-burningportra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flywheel-scan
Source: https://github.com/burningportra/agent-flywheel-plugin/tree/main/skills/flywheel-scan
Command: npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-scan-burningportra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a full repository scan is expensive and noisy when you only care about one path or one concern. This Skill performs a focused scan of specific paths or focus areas without triggering a complete flywheel cycle. ## Core Features & Use Cases - Targeted Path Analysis: Narrow the scan to specific directories or files instead of the whole repository. - Focus-Area Scanning: Choose from architecture, performance, security, testing, or dependencies as the lens for analysis. - Profile Integration: Calls the flywheel_profile tool via the agent-flywheel MCP server to enrich findings with project context. - Use Case: You suspect performance issues in your API layer. Run a targeted scan on the api/ directory with a performance focus, review the findings, and optionally launch a flywheel cycle to address them. ## Quick Start Ask the agent to run a targeted scan on the src/api directory with a focus on performance.

Frequently Asked Questions about flywheel-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan only part of a repository instead of the whole codebase?▼

Run a targeted scan by specifying the path you want analyzed, such as a single directory or module. The scan uses an Explore agent limited to that scope, so results stay focused on the area you care about.

What focus areas can I choose for a targeted code scan?▼

You can focus the scan on architecture, performance, security, testing, or dependencies. If you do not specify one, the skill asks which area to analyze before proceeding.

Does flywheel-scan require the agent-flywheel MCP server?▼

Yes, the scan calls the flywheel_profile tool through the agent-flywheel MCP server with the current working directory and an optional goal. Without that server configured, the profiling step cannot complete.

When should I use a targeted scan instead of a full flywheel scan?▼

Use a targeted scan when you already know the path or concern you want to investigate and want quick findings without the overhead of a full cycle. A full flywheel scan is better for broad, whole-repository discovery.

What happens after the targeted scan finishes?▼

The scan displays key findings, immediate concerns, and suggested improvements for the specified area. It then asks whether you want to start a flywheel cycle targeting those findings.