菜单
Prepare all OSM community requirements before mechanical edits — wiki page, talk-us discussion, import account setup, changeset tag templates. This is mandatory and NOT optional.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run the full TIGER defect audit pipeline for a MetroNow service zone — fetch from Overpass, classify defects, analyze history, generate reports.
Diff OSM geometry and attributes against TIGER/Line 2024 to identify import drift, new roads, and name-field artifacts in MetroNow zones.
Generate a MapRoulette challenge from scan results for defect classes with high false-positive rates. Creates GeoJSON tasks constrained to MetroNow zone polygons.
Deep revision history analysis for specific OSM ways — fetches full version history from OSM API v0.6, identifies import bot vs human edits, classifies review status with confidence scores.
Submit corrections to OSM API v0.6 with full community compliance — proper changeset tags, size limits, rate-limit awareness, and dry-run support.
Decompress MetroNow docs so future-you (and fresh AI sessions) can pick the project back up cold without re-deriving everything. Use when the user says docs are confusing, plain, dense, hard to follow, missing context, jargon-heavy, jump straight to conclusions, or are hard to come back to after time away; asks why something is the way it is; says they can't tell what a term means; asks for a walkthrough, explainer, primer, or context refresher; says a section assumes too much; or wants visual aids. Diagnoses missing-middle gaps (undefined jargon, unstated WHY, skipped bridge steps, prose where a picture is needed) and rewrites sections using a fixed template — definition first, then bridge steps, then a load-bearing diagram, then code citations. Outputs to docs/explainers/<topic>.md or in-place edits. No VitePress, no static-site generator — just markdown that GitHub renders.
| name | community-prep |
| description | Prepare all OSM community requirements before mechanical edits — wiki page, talk-us discussion, import account setup, changeset tag templates. This is mandatory and NOT optional. |
| when_to_use | User mentions community compliance, wiki page, talk-us, import account, before first submission, or asks if ready to submit |
| allowed-tools | Read Grep Glob Bash(python *) Bash(curl *) |
RESEARCH-FINDINGS Section 3 Item 8 and CLAUDE.md both state: mechanical edits require wiki documentation, talk-us@ discussion, and _cincyimport-convention account. Failing to comply risks unilateral revert by the DWG without notice, regardless of edit quality.
Create at: wiki.openstreetmap.org/wiki/Automated_edits/<username>
Must include:
Post on BOTH:
talk-us@openstreetmap.org mailing listcommunity.openstreetmap.org forum (US section)Discussion should describe:
Follow the Cincinnati convention established by the CAGIS Building Import:
<username>_cincyimport (e.g., krassy513_cincyimport)Prepare the standard tags (see /changeset-submit for full list):
comment= — descriptive per-changesetsource= — data sources usedmechanical=yescreated_by=MetroNow TIGER Audit Pipelinedescription= — URL to wiki documentation pagebot=yes if fully automated (not for reviewed edits)The Cincinnati OSM community is active:
The CAGIS Building Import (2018-ongoing, ~358,167 buildings) followed this exact process:
_cincyimport account suffix conventionFollow the same pattern for credibility with the local community.
If any mapper or community member objects to the edits: