Bevy profiling and migration
Separates slow builds, slow startup and slow gameplay before choosing a remedy. For an intended version change, it maps affected APIs and plugins while preserving a working revision to return to.
bevy-profiling-migration
See how it helpsWhen is it useful?
Use when a Bevy project stalls or an intended engine migration changes its behavior.
What does it help you do?
- Separates compilation, startup and ongoing frame costs using a repeatable gameplay route.
- Profiles costly systems before proposing architectural changes or dependency upgrades.
- Tracks affected APIs, plugin compatibility and a usable rollback revision.
Try asking this
Our large battle runs slowly, and we are considering a Bevy upgrade. First measure the busiest combat route and identify costly systems. If upgrading is justified and authorized, check plugin compatibility and replay that route on both revisions; keep the working baseline available.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Bevy — profiling migration
Use when diagnosing Bevy frame stalls, build/runtime regressions or version migration.
Version and project gate
Inspect Cargo.toml, Cargo.lock, Rust toolchain, exact Bevy release, plugin compatibility, feature selection, schedules, state definitions, asset roots and target backend. Read the matching migration guide before using newer examples. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Capture the pinned toolchain, features, target and reproduction. Separate compile/link time from startup and steady-state performance. Profile schedule hotspots before changing architecture. Migrate one release boundary with its matching guide and plugin matrix; preserve a compiling rollback revision.
Deliver
A measured bottleneck or migration ledger with exact versions, affected APIs and remaining blockers. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
A successful cargo check does not prove render behavior or a target device; never upgrade every plugin blindly.
Acceptance scenario
Build the intended target and replay the same gameplay route before/after; label checks that could not be run. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Talon. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md