maintenance
Routes UnrealCV command-doc, public API snapshot, and coverage-maintenance tasks.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- maintenance
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Routes UnrealCV command-doc, public API snapshot, and coverage-maintenance tasks.
- disable-model-invocation
- true
02 资源文件 5
- 参考文档references/troubleshooting.md2.9 KB
- 参考文档references/workflows.md3.2 KB
- 脚本scripts/generate_command_schema.py10.5 KB
- 脚本scripts/update_public_api_snapshot.py3.6 KB
- 脚本scripts/validate_command_coverage.py3.9 KB
03 SKILL.md 正文
Maintenance
Use this sub-skill when the repo changes and the generated command docs or public API snapshot need to be refreshed. The bundled helpers default to ../../references/unrealcv-source/, so they do not need the original checkout unless you intentionally override the root.
Read first
../../references/source-bundle.mdfor the packaged source snapshot layout.references/workflows.mdfor snapshot and schema refresh steps.references/troubleshooting.mdfor drift, editor-only-route, and coverage issues.scripts/update_public_api_snapshot.pyfor the public API snapshot workflow.scripts/validate_command_coverage.pyfor command-doc coverage checks.scripts/generate_command_schema.pyfor schema regeneration when the command surface changes.
What this sub-skill covers
- Refreshing the packaged
../../references/unrealcv-source/client/python/unrealcv/public_api_snapshot.json - Regenerating the packaged
../../references/unrealcv-source/docs/reference/command_schema.jsonand related command docs - Validating that the generated docs mention every runtime command
- Checking that the public API snapshot still matches the exported Python surface
- Distinguishing runtime commands from editor-only bindings
Typical triggers
- "I added or removed a command handler; update the docs."
- "The public API snapshot is stale."
- "The generated command docs are missing a route."
- "Validate command coverage after changing the C++ or Python API surface."
What belongs elsewhere
- Runtime client usage belongs in
../python-client/. - Plugin build, install, and packaging belong in
../plugin-build/. - Do not route a live-server debugging task here just because it touches command names.
Usage pattern
- Refresh the generated snapshot or schema with the bundled helper.
- Re-run the coverage check.
- Review any runtime-versus-editor mismatch before declaring the docs current.
- Only pass
--repo-rootwhen you intentionally want to inspect another checkout instead of the packaged snapshot.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).