MAINTAINERS.md

Maintainer checklist

1. Review PRs — Confirm the report is a usage/convention pitfall, not an upstream bug; check tool names against config/domains.json (domain_tools for home field; cross_tools are partners only, not membership) and the relevant skill’s cross_index.json under skills/.

2. Tool aliases — Prefer editing config/tool_aliases.yaml when the same tool appears under multiple spellings. The build script auto-adds unknown tokens (spaces → _); adjust after review.

3. Domains — New areas need an entry in config/domains.json and a sources/<slug>/ tree. After merge, run build_pitfall_skill.py only for domains that changed (repeat --domain for several). Each run updates domain_tools / cross_tools in domains.json for those slugs (skip with --no-update-domains only when intentional). Use --all-domains only when many trees were edited. Same YAML can be merged into multiple domains with merge_contributions.py --domain A --domain B file.yaml.

4. Dedup — Same issue URL + same tools set should not create two identical cross entries; different tool sets on one issue are allowed.

5. Release — Tag or note changelog when regenerating after bulk updates.