菜单
Use when models have changed significantly, after migrations, or when cross-app relationship data in docs/systems/MODEL_MAP.md seems stale. Also use when you can't find how systems connect and need to regenerate the model map.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when running or writing tests in this repo — choosing the SQLite fast tier vs Postgres parity tier, the just test recipes, @tag("postgres") decisions, --keepdb pitfalls, or diagnosing SQLite-vs-PG test failures.
Use when working on a GitHub issue from start to merged PR. Picks up an issue (or prompts for one), drafts the spec onto the issue body for team review, implements after a member approves it (spec:approved label), opens a PR, watches CI and fixes failures, and handles post-merge cleanup including filing follow-up issues. Polytoken-native: orchestrates the ported brainstorming + writing-plans + using-git-worktrees skills.
Use when starting feature work that needs isolation from the current workspace, or before executing implementation plans — ensures an isolated workspace exists.
Use when a class/function/model has no live caller and you're deciding whether it's a speculative stub, dead code, or unfinished work — or when writing new code whose caller doesn't exist yet. Traces a surface's origin (git history, linked issue/spec, roadmap/ADR) before classifying it, and documents intent forward so the next reader doesn't have to redo the trace.
Use when a feature design, spec, or implementation plan is about to propose a new code surface (model, dataclass, enum, serializer, component, hook, helper, field, endpoint) OR wire up an existing stub (a "not wired" button/endpoint/flow), or when relying on a systems/architecture/roadmap doc's claim about what exists or doesn't, OR when filing a follow-up/audit issue or writing a "deferred follow-up" into a spec (a deferral is a proposed future surface — verify its premise before it becomes a filed issue) — before committing the spec, filing the issue, or writing code.
Use when adding or working with Django models in this repo, resolving an apparent N+1, optimizing queries, caching, or walking foreign-key relationships — and before writing any resolve_/batch_fetch_ helper or flushing the identity map.
| name | codebase-indexing |
| compatibility | polytoken |
| description | Use when models have changed significantly, after migrations, or when cross-app relationship data in docs/systems/MODEL_MAP.md seems stale. Also use when you can't find how systems connect and need to regenerate the model map. |
Regenerate the auto-generated model relationship map that prevents expensive codebase searches. The map lives at docs/systems/MODEL_MAP.md and contains FK relationships, reverse relations, and service function signatures for every Django app.
uv run python tools/introspect_models.py > docs/systems/MODEL_MAP.md
The script (tools/introspect_models.py) introspects all Django apps and outputs:
services.pyIf a new Django app is created, add its label to the TARGET_APPS list in tools/introspect_models.py.
docs/systems/MODEL_MAP.md is regenerated by many PRs, so it collides on nearly every rebase onto a moved main. Don't hand-merge the conflict markers, and don't try to regenerate while the file still has conflict markers (the tool won't cleanly overwrite a conflicted file).
Clean resolution: git checkout --theirs docs/systems/MODEL_MAP.md (in a rebase, --theirs = the commit being applied = your work) → git add → finish the rebase. Then, on the final clean tree, regenerate once more and git diff --stat it — a correct merge yields zero diff (your regen already matches the merged models). If it shows a diff, commit the fresh regen.
sync-with-main.sh's potentially_impacted_issues for MODEL_MAP are usually just "another open branch touched the same generated file" title-matches, not real semantic conflicts — don't comment on them.
Run the regen command from the worktree root, not cd src && uv run ... — the latter creates a stray src/.venv that breaks the shard-coverage pre-commit hook (see the running-tests skill).
When looking for how systems connect:
docs/systems/MODEL_MAP.md for the model or app namedocs/systems/INDEX.md for concept-to-location mappingCLAUDE.md for design rules and patterns