# Sweep Collisions

> Check repository history, open work, automation, and available work trackers for overlapping changes before implementation.

- Skill: `homenshum/sweep-collisions` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add homenshum/sweep-collisions`
- Raw SKILL.md: https://api.skillmd.com/api/skills/homenshum/sweep-collisions/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: HomenShum (https://skillmd.com/u/homenshum)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/homenshum/sweep-collisions

---


# Sweep collisions

Read [the execution contract](references/contract.json) before starting. Validate the final receipt with its parameterized `verification.argv`, replacing `{python}`, `{skill_dir}`, and `{receipt}` with concrete local values.

Before editing a contested seam, search the repository, recent branches or
reviews available in scope, and deployment or scheduled automation that can
write the same surface.

Return a receipt with the queried sources, exact search terms, time boundary,
overlapping owners, conflicting contracts, and `CLEAR`, `COORDINATE`, or
`BLOCKED`. Label unavailable sources `UNVERIFIED`; absence of access is not a
clear result.

Use connectors only when already authorized. Never broaden a repository task
into messages, tickets, or remote changes without explicit authority.