Agent skill

Codd Scan

by yohey-w in yohey-w/codd-dev

Refresh a CoDD project's dependency graph from document frontmatter and source code.

MITAuto-check passedDevelopment

Install Codd Scan

skills CLI
$ npx skills add yohey-w/codd-dev --skill codd-scan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yohey-w/codd-dev codd-scan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yohey-w/codd-dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/codd-scan .claude/skills/codd-scan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
codd-scan
GitHub stars
115
Token cost
~1.4k tokens
SKILL.md length
665 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Refresh a CoDD project's dependency graph from document frontmatter and source code.

  • Works in 4 steps: Resolve the target project root first.… → Check whether codd/codd.yaml exists… → If codd/codd.yaml is missing, initialize… → …
  • Needs current graph data
  • SKILL.md covers When to Use, Preconditions, Command and What the Scan Does, plus 4 more sections
  • Calls pip

What it does

Codd Scan is an agent skill from yohey-w/codd-dev. Refresh a CoDD project's dependency graph from document frontmatter and source code. Use after changes to requirements, design docs, implementation, or tests when the user needs current graph data, frontmatter coverage, node and edge counts, or warnings before validation or impact analysis.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Architecture decision records. The repository describes itself as: CoDD: Coherence-Driven Development — Claude Code plugin for cross-artifact change impact analysis. The licence is MIT.

When your agent uses it

  • Needs current graph data
  • Frontmatter coverage
  • Node and edge counts
  • Warnings before validation

Example prompts

  • “/codd-scan”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Resolve the target project root first. Prefer an absolute path when the working directory is ambiguous.
  2. Check whether codd/codd.yaml exists under that path.
  3. If codd/codd.yaml is missing, initialize CoDD before scanning
  4. If codd is not on PATH, use one of these

What it can do on your machine

Read from SKILL.md and the folder at commit 41b5f87. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pip, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Codd Scan loads about 1.4k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 665 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yohey-w/codd-dev at commit 41b5f87, republished under its MIT licence (© yohey-w). 665 words, ~1,358 tokens.

Download SKILL.mdSave it as .claude/skills/codd-scan/SKILL.md (or your agent's skills folder).
name
codd-scan
description
Refresh a CoDD project's dependency graph from document frontmatter and source code. Use after changes to requirements, design docs, implementation, or tests when the user needs current graph data, frontmatter coverage, node and edge counts, or warnings before validation or impact analysis.

CoDD Scan

Refresh the CoDD dependency graph from document frontmatter and source code so later commands (codd validate, codd impact, codd generate, codd verify) operate on current project state. Use this after requirements, design docs, implementation, or tests change.

When to Use

  • After editing Markdown files with CoDD frontmatter
  • After adding or changing source files that affect dependencies
  • Before codd impact when you need a fresh graph
  • When scan counts look stale or unexpectedly low

Preconditions

  1. Resolve the target project root first. Prefer an absolute path when the working directory is ambiguous.
  2. Check whether codd/codd.yaml exists under that path.
  3. If codd/codd.yaml is missing, initialize CoDD before scanning:
bash
codd init --project-name "<project-name>" --language "<language>" --dest <path>
  1. If codd is not on PATH, use one of these:
    • pip install codd-dev
    • .venv/bin/codd scan --path <path>

Command

Run the scan from anywhere by passing the project root explicitly:

bash
codd scan --path <path>

If you are already at the project root, codd scan --path . is sufficient.

What the Scan Does

  1. Reads codd/codd.yaml
  2. Rebuilds auto-generated graph data from project documents and source code
  3. Preserves human-authored evidence
  4. Prints a short summary of frontmatter coverage and graph size

How to Interpret the Result

Typical output includes:

text
Scan complete:
  Documents with frontmatter: <count>
  Graph: <nodes> nodes, <edges> edges
  Evidence: <total> total (...)
  • Documents with frontmatter: how many Markdown documents in configured doc_dirs were successfully read as CoDD documents. If this is lower than expected, inspect missing frontmatter or wrong doc_dirs.
  • nodes: the number of tracked artifacts in the graph. In document-centric projects this is usually close to the total number of requirements/design/test artifacts being tracked.
  • edges: the total number of declared or inferred dependency relationships between those artifacts.
  • orphan nodes: artifacts that have no surviving dependency relationship. They are often a sign of missing depends_on, stale docs, or a document that should be deleted. Some top-level requirements may be intentional exceptions, but unexplained orphans should always be reviewed.
  • WARNING: lines: scan found suspicious input such as missing frontmatter or design docs with empty dependencies. Treat warnings as a prompt to run codd validate.
  • SCAN_ERROR (if surfaced by your wrapper, report script, or higher-level UI): frontmatter could not be parsed or read cleanly. Treat it as a validation problem and inspect the document with codd validate --path <path>.
Show full SKILL.md (306 more words)Show less

Use this decision guide after every scan:

ConditionNext action
Scan completed and counts look plausibleRun codd validate --path <path> to confirm references and frontmatter integrity
Scan printed warnings or your tooling reports SCAN_ERRORRun codd validate --path <path> immediately and fix the reported documents before moving on
Orphan nodes are presentCheck whether they are intentional. If not, add missing dependency metadata or remove obsolete docs, then rerun codd scan and codd validate
You already trust the graph and now need blast-radius analysis for recent changesRun codd impact --path <path>
You need impact for a specific commit or branch deltaRun codd impact --diff <git-ref> --path <path>

Autonomous Workflow

When using this skill without further user guidance:

  1. Confirm the project root and codd/codd.yaml
  2. If CoDD is not initialized, run codd init ... --dest <path> first
  3. Run codd scan --path <path>
  4. Read the summary and warnings
  5. Run codd validate --path <path> if anything looks wrong, incomplete, or newly changed
  6. Run codd impact --path <path> only after the graph is fresh and you need downstream impact analysis
  7. Report the scan summary in plain language: frontmatter coverage, node count, edge count, warnings, and whether follow-up validation or impact analysis is needed

Troubleshooting

  • Verify <path> points at the project root, not a subdirectory
  • Check that codd/ exists under the target path
  • Retry with an absolute path
codd: command not found
  • Install the CLI: pip install codd-dev
  • Or run the virtualenv binary directly: .venv/bin/codd scan --path <path>
Error: codd/ not found or codd/codd.yaml not found
  • Initialize CoDD first:
bash
codd init --project-name "<project-name>" --language "<language>" --dest <path>
  • Then confirm codd/codd.yaml and configured doc_dirs/source_dirs before scanning again
Frontmatter parse errors or SCAN_ERROR
  • Run:
bash
codd validate --path <path>
  • Fix malformed YAML frontmatter, undefined references, or circular dependencies
  • Rerun codd scan --path <path> after the validation issues are resolved

© yohey-w, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/codd-scan of yohey-w/codd-dev.

Open the folder on GitHubat commit 41b5f87

Compare with similar skills

Codd Scan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Codd Scan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Codd Scan this skillyohey-w/codd-dev115—~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3804 repos~2.4kAutomated safety check: PassMIT
Improve Codebase Architectureywwynm/EverythingDone14415 repos~1.3kAutomated safety check: PassGPL-3.0
Domain Modelingbrim-borium/spotify_sdk1665 repos~806Automated safety check: PassApache-2.0
Design Doc MermaidSpillwaveSolutions/design-doc-mermaid1751 repos~5.6kAutomated safety check: PassNone

Similar skills

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    380 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed
  • Improve Codebase Architecture

    ywwynm/EverythingDone

    Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.

    144 GitHub starsUsed in 15 repos~1.3k tokens
    DevelopmentAuto-check passed
  • Domain Modeling

    brim-borium/spotify_sdk

    Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.

    166 GitHub starsUsed in 5 repos~806 tokens
    DevelopmentAuto-check passed
  • Design Doc Mermaid

    SpillwaveSolutions/design-doc-mermaid

    Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.

    175 GitHub starsUsed in 1 repo~5.6k tokens
    DevelopmentAuto-check passed
  • Learning Opportunities

    DrCatHicks/learning-opportunities

    Facilitates deliberate skill development during AI-assisted coding.

    2.5k GitHub stars~2.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from yohey-w/codd-dev

All 11 skills in this repo
  • Codd Generate

    yohey-w/codd-dev

    Generate CoDD design documents for a greenfield project one wave at a time.

    115 GitHub stars~1.5k tokensUpdated 24 days ago
    Auto-check passed
  • Codd Greenfield

    yohey-w/codd-dev

    Run the CoDD greenfield autopilot: a requirements document in, a working system out, unattended.

    115 GitHub stars~2.2k tokensUpdated 24 days ago
    Auto-check passed
  • Codd Init

    yohey-w/codd-dev

    Initialize CoDD in a project and establish the first scan and validation baseline.

    115 GitHub stars~1.1k tokensUpdated 24 days ago
    Auto-check passed
  • Codd Propagate

    yohey-w/codd-dev

    Reverse-propagate source code changes back to affected CoDD design documents.

    115 GitHub stars~1.4k tokensUpdated 24 days ago
    Auto-check passed
  • Codd Restore

    yohey-w/codd-dev

    Reconstruct CoDD design documents from extracted code facts for a brownfield project.

    115 GitHub stars~1.3k tokensUpdated 24 days ago
    Auto-check passed
  • Codd Impact

    yohey-w/codd-dev

    Analyze the downstream impact of changed requirements, design docs, code, or tests in a CoDD project.

    115 GitHub stars~1.5k tokensUpdated 24 days ago
    Auto-check: warnings

Categories

Questions about Codd Scan

What does Codd Scan do?

Refresh a CoDD project's dependency graph from document frontmatter and source code. Codd Scan is an agent skill from yohey-w/codd-dev. Refresh a CoDD project's dependency graph from document frontmatter and source code.

When should I use Codd Scan?

Codd Scan fits situations like: needs current graph data; frontmatter coverage; Node and edge counts; warnings before validation.

How do I install Codd Scan in Claude Code?

Run `npx skills add yohey-w/codd-dev --skill codd-scan -a claude-code`. Or copy the skill folder (skills/codd-scan in yohey-w/codd-dev) into .claude/skills/codd-scan in your project. Claude Code loads it when a task matches its description.

How do I install Codd Scan in Codex?

Run `npx skills add yohey-w/codd-dev --skill codd-scan -a codex`. Or copy the skill folder (skills/codd-scan in yohey-w/codd-dev) into .agents/skills/codd-scan in your project. Codex loads it when a task matches its description.

Can I use Codd Scan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yohey-w/codd-dev --skill codd-scan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/codd-scan, .gemini/skills/codd-scan, .github/skills/codd-scan and .opencode/skills/codd-scan in your project.

What does Codd Scan need to run?

Going by SKILL.md and its folder, Codd Scan needs the command-line tools its instructions call (pip). Our summary lists: Python 3.

Does Codd Scan access the network?

SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Codd Scan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Codd Scan use?

Codd Scan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Codd Scan use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Codd Scan?

Skills that share tags, products or a category with Codd Scan: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 380 stars), Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars) and Domain Modeling (brim-borium/spotify_sdk, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Codd Scan?

yohey-w (a GitHub user) maintains it in yohey-w/codd-dev, which has 115 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 14, 2026.

Source: yohey-w/codd-dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.