القائمة
Set up and query OSMCha monitoring for MetroNow zone changesets. Post-submission monitoring via REST API, pre-submission scoring via local osmcha Python package.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | osmcha-monitor |
| description | Set up and query OSMCha monitoring for MetroNow zone changesets. Post-submission monitoring via REST API, pre-submission scoring via local osmcha Python package. |
| when_to_use | User mentions OSMCha, monitoring edits, checking changesets, scoring proposed edits, or reviewing edit impact |
| allowed-tools | Read Grep Glob Bash(python *) Bash(curl *) |
| argument-hint | [changeset-id or zone] |
| arguments | ["target"] |
Monitor or score edits for: $target
The OSMCha REST API at osmcha.org/api/v1/changesets/{id}/ requires a changeset ID and only works after submission. Use this to:
The osmcha Python package (PyPI: OSMCha/osmcha) flags suspicious changesets locally using configurable thresholds:
create_threshold=200 — flag if creating more than 200 elementsmodify_threshold=200 — flag if modifying more than 200 elementstop_threshold=1000 — flag if total changes exceed 1000!python -c "import sys; sys.path.insert(0, 'src'); from osm.zones import ZONES; [print(f' {k}: bbox={v[\"bbox\"]}') for k,v in ZONES.items()]"
Create OSMCha saved filters for each zone:
https://osmcha.org/api/v1/changesets/?in_bbox={w},{s},{e},{n}
The web UI at http://localhost:3000 should subscribe to these feeds so reviewers see:
After submitting a changeset:
osmcha.org/api/v1/changesets/{changeset_id}/ for the analysisRun 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.