repository-development
Edit RF-DETR source while following project contribution, test, style, docs, packaging, model-selection, and CI conventions.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- repository-development
- license
- Apache 2.0
- metadata
- { "disco-role": "operating" }
- description
- Edit RF-DETR source while following project contribution, test, style, docs, packaging, model-selection, and CI conventions.
- disable-model-invocation
- true
02 资源文件 4
- 参考文档references/contributor-guidance.md10.1 KB
- 参考文档references/test-selection.md9.1 KB
- 参考文档references/troubleshooting.md9.4 KB
- 脚本scripts/select_checks.py17.9 KB
03 SKILL.md 正文
RF-DETR Repository Development
Use this sub-skill when you are changing RF-DETR source, tests, docs, packaging, or CI. It is for contributor workflows, not for end-user inference, training, or export recipes.
Start Here
- Read Contributor guidance before editing source, tests, docs, package metadata, or workflow files.
- Use Test selection to choose focused checks during development and full gates before handoff.
- If a check fails or optional backends are involved, use Troubleshooting.
- To get a dry recommendation from changed paths, run:
python sub-skills/repository-development/scripts/select_checks.py PATH [PATH ...]
The script prints commands only; it does not run tests or modify files.
Routing
- For Python source, tests, examples, docs snippets, or configs, start with Contributor guidance, then choose checks from Test selection.
- For test helpers, fixtures, parametrization, or markers, read test style and the test tree map.
- For package metadata, extras, lock/dependency behavior, or CI install plans, read optional backend guidance and dependency checks.
- For documentation pages or MkDocs config, read docs/build guidance and docs troubleshooting.
- For pre-commit, ruff, mypy, license headers, docstrings, or formatting, read code quality rules and style troubleshooting.
- For CI-only GPU/XLA/CoreML/ExecuTorch/TensorRT failures, use the CI/backend split and backend troubleshooting.
Non-Negotiables
- Use TDD: failing test first for bug fixes; comprehensive tests for features.
- Every new or changed function/class needs type hints and a Google-style docstring; do not duplicate types inside docstrings.
- Python files need the RF-DETR license header.
- Run
pre-commit run --all-filesbefore any commit/handoff. - Default examples/docs/tests to
RFDETRSmall/"rfdetr-small"; do not add newRFDETRBase,"rfdetr-base", segmentation preview, or detection preview usage. Keypoint preview is the only preview variant to use for new material. - Keep imports direct and module-scope unless there is a clear optional-dependency, circular-import, import-behavior-test, or startup-side-effect reason.
- Prefer small visible duplication over a helper that adds indirection without reducing cognitive load.
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).