Cross-Cutting Checklist Generator
Builds a project checklist so scattered concerns never get half-updated
Test report
- Verdict
- Tested · Works
- Score
- Tested
- Jul 30, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Jul 30, 2026 · 494f937
⚠ This skill is no longer available upstream. Our re-check on Aug 10, 2026 couldn't find it any more (repo unreachable/deleted). The test below is what we measured on Jul 30, 2026 and we're leaving it up as a record — but there is nothing left to install, so we've removed the command.
Tested on an eleven-file project where the notification-channel set is duplicated across fourteen places, three of which contain no channel name at all: a budget divisor TOTAL_BUDGET // 3, a CSS repeat(3, 1fr) picker grid, and a docs sentence reading Three delivery channels are available. Adding a new channel the usual way — grep an existing channel name, edit the hits, run the test suite — updated 10 of 13 checkpoints and the tests still went green, so all three count-based spots stayed silently stale; following the skill produced a .credo/checklists/notification-channels.md that named them explicitly and the same change hit 13 of 13. Repeating with a second new channel reproduced the gap exactly: grep-driven 10 of 13 again, checklist-driven 13 of 13, which is the persistence payoff the skill claims. The catch is the namespace it writes into: .credo/ comes from the credo plugin, and running credo-init.sh in a fresh repo exits 4 with 'is a hub or has no credo project' unless you pass CREDO_DIR or pin the project, so a standalone copy of the skill has to create the directory itself and the checklists are not git-excluded.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 8/10
- Docs & honesty 4/5
What Cross-Cutting Checklist Generator does
Detects when one concern is duplicated across many places in a project — config keys, enums, translations, feature flags, API endpoints, docs — and writes a project-local checklist listing every spot with a locator and a note on what must stay in sync. On later edits it consults the checklist first and updates it afterwards, then verifies completeness before the change is called done. It fires whenever you add or change something that also exists elsewhere, including inside subagents.
How to install Cross-Cutting Checklist Generator
Nothing to install: the source repository no longer has this skill. If the author brings it back, our daily re-check will pick it up and the command will reappear here.
Commands — how to trigger Cross-Cutting Checklist Generator
-
/cross-cutting-checklist-generatorBuilds a project checklist so scattered concerns never get half-updated
It also activates on plain-language prompts like these:
-
Add a new value to the OrderStatus enum and keep every reference in sync -
I added a key to en.json, make sure the other locale files aren't missing it -
Add a webhook notification channel across the app without missing a spot
Frequently asked questions
- Is the Cross-Cutting Checklist Generator skill free?
- Yes. The skill itself is free from Marcel-Bich/marcel-bich-claude-marketplace. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Cross-Cutting Checklist Generator work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 30, 2026. Verdict: Tested · Works. Tested on an eleven-file project where the notification-channel set is duplicated across fourteen places, three of which contain no channel name at all: a budget divisor TOTAL_BUDGET // 3, a CSS repeat(3, 1fr) picker grid, and a docs sentence reading Three delivery channels are available. Adding a new channel the usual way — grep an existing channel name, edit the hits, run the test suite — updated 10 of 13 checkpoints and the tests still went green, so all three count-based spots stayed silently stale; following the skill produced a .credo/checklists/notification-channels.md that named them explicitly and the same change hit 13 of 13. Repeating with a second new channel reproduced the gap exactly: grep-driven 10 of 13 again, checklist-driven 13 of 13, which is the persistence payoff the skill claims. The catch is the namespace it writes into: .credo/ comes from the credo plugin, and running credo-init.sh in a fresh repo exits 4 with 'is a hub or has no credo project' unless you pass CREDO_DIR or pin the project, so a standalone copy of the skill has to create the directory itself and the checklists are not git-excluded.
- What is the Cross-Cutting Checklist Generator SkillProof Score?
- 8.8/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 8/10, docs & honesty 4/5.
- How do I install Cross-Cutting Checklist Generator?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Cross-Cutting Checklist Generator with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.