New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Codd Propagate

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

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

MITAuto-check passedDevelopment

Install Codd Propagate

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

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

GitHub CLI
$ gh skill install yohey-w/codd-dev codd-propagate --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-propagate .claude/skills/codd-propagate && 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-propagate
GitHub stars
115
Token cost
~1.4k tokens
SKILL.md length
574 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 4 steps: codd/codd.yaml exists with source_dirs… → Design docs have modules field in their… → There are uncommitted source code… → …
  • Needs to map changed source files to modules
  • SKILL.md covers When to Use, Propagation Direction, How It Works and Prerequisite Checks, plus 7 more sections
  • Calls git and python

What it does

Codd Propagate is an agent skill from yohey-w/codd-dev. Reverse-propagate source code changes back to affected CoDD design documents. Use after code changes when the user needs to map changed source files to modules, identify impacted design docs, and optionally update those docs while preserving CoDD coherence.

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 to map changed source files to modules
  • Identify impacted design docs
  • Optionally update those docs while preserving CoDD coherence

Example prompts

  • “/codd-propagate”

Requirements

  • Python 3

Workflow steps

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

  1. codd/codd.yaml exists with source_dirs configured in scan.
  2. Design docs have modules field in their frontmatter.
  3. There are uncommitted source code changes (or specify --diff target).
  4. Confirm you are in the intended project root.

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:

    • git
    • python

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

  • Network

    No URLs in SKILL.md. Its commands use git, 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 Propagate loads about 1.4k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 574 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
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). 574 words, ~1,361 tokens.

Download SKILL.mdSave it as .claude/skills/codd-propagate/SKILL.md (or your agent's skills folder).
name
codd-propagate
description
Reverse-propagate source code changes back to affected CoDD design documents. Use after code changes when the user needs to map changed source files to modules, identify impacted design docs, and optionally update those docs while preserving CoDD coherence.

CoDD Propagate

Reverse-propagate source code changes to design documents. When source code changes, codd propagate identifies which design docs are affected via the modules field and optionally updates them using AI.

When to Use

  • After modifying source code and before committing
  • When you want to check which design docs are affected by code changes
  • When you want to auto-update design docs to reflect code changes
  • As part of the modification flow (code changed → propagate → review → commit)

Do NOT use this for:

  • Document-to-document propagation — use /codd-impact instead
  • Initial design doc generation — use /codd-generate (greenfield) or /codd-restore (brownfield)

Propagation Direction

CoDD supports two propagation directions:

DirectionCommandTriggerMechanism
Forward (doc → doc)codd impactDesign doc changedCEG dependency graph (depends_on)
Reverse (code → doc)codd propagateSource code changedmodules field in frontmatter

/codd-propagate handles the reverse direction only.

How It Works

git diff HEAD              # 1. Detect changed source files
  ↓
source_dirs mapping        # 2. Map files to modules (e.g. src/auth/service.py → "auth")
  ↓
modules field lookup       # 3. Find design docs with matching modules
  ↓
Analysis report            # 4. Show which docs need attention
  ↓ (--update only)
AI update                  # 5. AI updates affected doc bodies

Prerequisite Checks

Before running propagate, verify:

  1. codd/codd.yaml exists with source_dirs configured in scan.
  2. Design docs have modules field in their frontmatter.
  3. There are uncommitted source code changes (or specify --diff target).
  4. Confirm you are in the intended project root.

If modules fields are missing, run codd plan --init to regenerate wave_config with modules, then regenerate or restore design docs.

Analysis Only (Default)
bash
codd propagate --path .

This shows:

  • Changed source files and their module mappings
  • Design docs affected by those changes
  • Suggestion to run with --update if updates are needed

Review the analysis before deciding whether to update.

With AI Update
bash
codd propagate --path . --update

This additionally:

  • Calls AI to update each affected design doc body
  • Preserves frontmatter exactly as-is
  • Leaves doc body unchanged for bug fixes or refactoring that don't affect design

After update, review every changed document before committing.

HITL Gates

  1. After analysis: Review the file → module → doc mapping. Confirm the affected docs list is correct before running with --update.
  2. After update: Read every updated design doc. Confirm:
    • Changes accurately reflect the code modification
    • No unrelated sections were altered
    • Bug fixes / refactoring correctly left the doc body unchanged
    • Frontmatter was preserved exactly
Show full SKILL.md (240 more words)Show less

When NOT to Update

Not every code change needs a design doc update. The AI prompt explicitly tells the model to leave the body unchanged for:

  • Bug fixes that don't change the design
  • Minor refactoring (rename, extract method)
  • Performance optimizations that don't change architecture
  • Test additions or modifications

Use analysis-only mode (codd propagate without --update) to check which docs are affected, then decide manually whether an update is warranted.

Options

FlagDescription
--pathProject root (default: current directory)
--diffGit diff target (default: HEAD)
--updateActually update affected docs via AI (default: analysis only)
--ai-cmdOverride AI command for this run

Complete Modification Flow

After modifying source code:

bash
# 1. Check reverse impact (code → docs)
codd propagate --path .

# 2. If design docs need updating
codd propagate --path . --update

# 3. Rebuild dependency graph
codd scan --path .

# 4. Check forward impact (doc → doc) if design docs changed
codd impact --path .

# 5. Validate and commit
codd validate --path .
git add -A && git commit

Troubleshooting

  • No changed files detected
    • Ensure you have uncommitted changes, or specify a different --diff target (e.g. --diff HEAD~3).
  • No affected design docs found
    • Check that source_dirs is configured in codd.yaml → scan.
    • Check that design docs have modules fields in their frontmatter.
    • Verify the module names match (e.g. src/auth/service.py maps to module auth).
  • Updated doc body is empty or garbled
    • Re-run with --update. If the AI output is still bad, manually edit the doc.

Guardrails

  • Use the codd command, not python -m codd.cli.
  • Always run analysis first (without --update) to confirm affected docs before updating.
  • Do not skip human review of updated documents.
  • Do not combine with codd impact in the same step — propagate handles code→doc, impact handles doc→doc.
  • After propagate with --update, always run codd scan to refresh the dependency graph.

© 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-propagate of yohey-w/codd-dev.

Open the folder on GitHubat commit 41b5f87

Compare with similar skills

Codd Propagate 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 Propagate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Codd Propagate 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 yesterday
    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 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

  • Codd Scan

    yohey-w/codd-dev

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

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

Categories

Questions about Codd Propagate

What does Codd Propagate do?

Reverse-propagate source code changes back to affected CoDD design documents. Codd Propagate is an agent skill from yohey-w/codd-dev. Reverse-propagate source code changes back to affected CoDD design documents.

When should I use Codd Propagate?

Codd Propagate fits situations like: needs to map changed source files to modules; identify impacted design docs; optionally update those docs while preserving CoDD coherence.

How do I install Codd Propagate in Claude Code?

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

How do I install Codd Propagate in Codex?

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

Can I use Codd Propagate 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-propagate -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-propagate, .gemini/skills/codd-propagate, .github/skills/codd-propagate and .opencode/skills/codd-propagate in your project.

What does Codd Propagate need to run?

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

Does Codd Propagate access the network?

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

Is Codd Propagate 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 Propagate use?

Codd Propagate 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 Propagate 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 Propagate?

Skills that share tags, products or a category with Codd Propagate: 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 Propagate?

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.