debug

Generate debug fixtures for local testing of FastEdge WASM apps in the visual debugger.

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/G-Core/fastedge-plugin --skill debug-g-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/G-Core/fastedge-plugin/tree/main/plugins/gcore-fastedge/skills/debug
Command: npx skills add https://github.com/G-Core/fastedge-plugin --skill debug-g-core

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @gcoredev/fastedge-test, and includes references (resource) components.

What problem does it solve? Manually authoring scenario configurations for the FastEdge visual debugger is tedious and error-prone, especially when an app has many geo-routing, env-var, or auth branches. This Skill generates a fixtures/ directory of ready-to-load .test.json scenarios so developers can inspect request/response behavior in the browser-based debugger without writing each fixture by hand. ## Core Features & Use Cases - Manual and Inferred Modes: Collaboratively pick scenarios from source reading, or pass --infer to derive a structured scenario list automatically using the patterns in reference/inference.md. - Safe Fixture Writes: Pre-flight checks never silently overwrite hand-authored .test.json or .env files; conflicting fixtures trigger a diff summary and an explicit keep/replace/cancel prompt. - Governance-Aware Setup: Detects "never change code" rules in AGENTS.md/CLAUDE.md before mutating package.json, and supports --no-modify-project / --modify-project overrides. - Smoke Checks and Rust Stderr Pre-Check: Optionally validates fixtures load cleanly via @gcoredev/fastedge-test, and warns Rust developers when eprintln!/stderr logging would be invisible in the debugger. - Use Case: A developer with a geo-redirect CDN app runs the skill with --infer and gets happy-path, germany, us, and fallback fixtures plus a fixtures/.env, then loads each scenario in the visual debugger at localhost:5179. ## Quick Start Ask the agent to generate debug fixtures for your FastEdge project, optionally with the --infer flag to derive scenarios from source automatically.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I generate debug fixtures for a FastEdge WASM app?

Run the debug skill against your project directory to create a fixtures/ directory of .test.json scenario files. Use the --infer flag to derive scenarios automatically from source, or default manual mode to pick scenarios collaboratively.

What is the difference between FastEdge debug fixtures and tests?

Fixtures are manual exploration scenarios loaded in the visual debugger's browser UI, while tests are CI pass/fail assertions generated by the separate test skill. Both use .test.json-style configs but serve independent purposes.

Does the debug skill overwrite my existing fixtures?

No. A pre-flight scan buckets each intended write: identical files are skipped, new files are written, and differing files trigger a diff summary with keep/replace/cancel options. Existing fixtures/.env files are always preserved.

Why are my Rust log lines missing in the FastEdge visual debugger?

FastEdge captures stdout only, so eprintln!, eprint!, io::stderr, and default env_logger output are silently dropped. The skill's Rust pre-check scans for these patterns and warns you to convert them to println! before debugging.

Can I prevent the skill from modifying package.json?

Yes. Pass --no-modify-project to skip all package.json mutation and receive manual setup instructions instead. The skill also auto-detects "never change code" rules in AGENTS.md or CLAUDE.md and switches to recommendation-only mode.