/catalog-collision-scan - Catalog Collision Scan Slash Command
Slash command runbook for scanning HeyClaude catalog collisions by slug, title, repo URL, and docs URL before opening a content-only PR—using audit-content patterns and GitHub code search.
Open the source and read safety notes before installing.
Safety notes
- Read-only search workflow—does not modify catalog files automatically.
- GitHub code search results may lag newly merged entries; also grep local content/ before opening PRs.
Privacy notes
- Search queries and repository paths enter Claude session context; avoid embedding secrets in search terms.
Prerequisites
- Local clone of awesome-claude with Node.js for audit-content scripts.
- GitHub CLI authenticated when using code search against the upstream repository.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Command syntax
- /catalog-collision-scan <category> <proposed-slug>
Full copyable content
/catalog-collision-scan <category> <proposed-slug>About this resource
Purpose
Run a collision scan before opening a one-file content PR: local content/ grep,
node scripts/audit-content.mjs, and GitHub code search for slug/title/source overlap.
Workflow
/catalog-collision-scan <category> <proposed-slug>- Grep
content/<category>/for slug, title fragments, repoUrl, and documentationUrl candidates. - Run
node scripts/audit-content.mjs -- --category <category>for semantic duplicates in metadata. - Use GitHub code search (
docs.github.comsearching-code guide) for open PR overlap. - Document findings in the PR Duplicate Check section.
Source Verification Notes
Verified on 2026-06-17 against GitHub code search docs and repository audit scripts.
Duplicate Check
Distinct from content-only-submission-pr-gate-rules (full PR gate policy). This command is an operator runbook for pre-submit collision scanning only.
Editorial Disclosure
Community command runbook by kiannidev for maintainers preparing content-only submissions.
Source citations
Add this badge to your README
Show that /catalog-collision-scan - Catalog Collision Scan Slash Command is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/commands/catalog-collision-scan)How it compares
/catalog-collision-scan - Catalog Collision Scan Slash Command side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | /catalog-collision-scan - Catalog Collision Scan Slash Command Slash command runbook for scanning HeyClaude catalog collisions by slug, title, repo URL, and docs URL before opening a content-only PR—using audit-content patterns and GitHub code search. Open dossier | /documentation-refresh - Documentation Refresh Runbook Community slash command runbook to refresh stale project documentation after code changes: use git history to find affected docs, compare README commands to package scripts, and flag broken internal links before opening a docs PR. Open dossier | /frontend-visual-qa - Chrome Design Verification Runbook Community slash command runbook for frontend visual QA using documented Claude Code Chrome integration workflows: enable /chrome, open a local page, read console messages, and follow the design verification checklist from the Chrome integration guide. Open dossier | /mcp-smoke-test - MCP Server Verification Runbook Community slash command runbook for post-install MCP verification using only documented Claude Code MCP commands: claude mcp list, claude mcp get, and the /mcp panel for authentication status before exercising a read-only tool. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | commands | commands | commands | commands |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | kiannidev | kiannidev | kiannidev | kiannidev |
| Added | 2026-06-17 | 2026-06-16 | 2026-06-16 | 2026-06-16 |
| Platforms | Claude Code | Claude Code | Claude Code | Claude Code |
| Source repo | — | — | — | — |
| Safety notes | ✓Read-only search workflow—does not modify catalog files automatically. GitHub code search results may lag newly merged entries; also grep local content/ before opening PRs. | ✓Read-only git history inspection unless the operator approves doc edits. Validate git refs before interpolating them into shell commands. | ✓Chrome integration runs in a visible browser with your logged-in session; avoid production admin flows. Handle login pages and CAPTCHAs manually when the integration pauses. | ✓Prefer read-only tools during verification; avoid destructive MCP tools on production data. Remove failing servers from MCP config before sharing logs externally. |
| Privacy notes | ✓Search queries and repository paths enter Claude session context; avoid embedding secrets in search terms. | ✓Commit messages and doc drafts enter model context; scrub internal-only details first. | ✓Console logs and screenshots may include staging data; redact before external sharing. | ✓MCP tool outputs may include repository paths; redact before posting publicly. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Featured in
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.