Inventory codebase specifications, invariants, gotchas, linters, and CI checks.
npx skills add https://github.com/marktoda/cohesive --skill discover-substrate
Please help me install this Agent Skill. Skill: discover-substrate Source: https://github.com/marktoda/cohesive/tree/main/skills/discover-substrate Command: npx skills add https://github.com/marktoda/cohesive --skill discover-substrate
When preparing to modify a codebase, teams often lack a clear inventory of existing specifications, named invariants, gotchas, semantic linters, and enforcement mechanisms, leading to broken behavior, duplicated work, and lost institutional knowledge. This skill eliminates that guesswork by systematically surfacing what substrate already exists and what is missing for the exact change surface you are about to touch.
Use the discover-substrate skill to inventory all existing specs, invariants, and gotchas for the payment processing subsystem before planning a refactor.
High-intent search queries and answers about installing and using this skill.
To inventory codebase invariants before a refactor, run a bounded scan to categorize existing specifications, behavior matrices, named invariants, gotchas, tests, and CI checks for your target change surface. This structured discovery separates existing substrate from missing memory with concrete file:line evidence.
Codebase substrate discovery is the systematic surfacing of existing specifications, invariants, gotchas, semantic linters, and enforcement mechanisms for a targeted change surface. You need it before modifying code to eliminate guesswork, prevent duplicated work, and avoid losing institutional knowledge.
Find missing test coverage and specification gaps by running a substrate audit that surfaces missing memory with concrete file:line evidence. This flags critical gaps in existing invariants and tests before you write code, preventing regressions rather than fixing them afterward.
Yes, you can audit a specific subsystem by running a bounded scan targeting your exact change surface. This categorizes all existing normative docs, behavior matrices, invariants, gotchas, tests, and custom linters only for the targeted code area rather than the entire repository.
Yes, this codebase audit approach works for planning spec rewrites by confirming all existing invariants around behaviors like transaction idempotency and audit logging are captured. It serves as the mandatory first step for refactor planning and spec rewriting workflows.
After completing a codebase substrate inventory, follow the single recommended next Cohesive skill identified in the structured discovery report. Downstream workflows include brainstorm-design, audit-substrate, review-codebase, and review-diff for processing the surfaced gaps and existing substrate.
hpsgdAutomate passive reconnaissance on a target domain using public sources.
marktodaScan codebases for implicit rules and generate draft Cohesive substrate artifacts.
marktodaGenerate codebase-grounded design options and pressure-test them with 25 questions.
rodrigotoledoIdentifies subdomains and bounded contexts in a codebase using DDD strategic design.
