Agent skill

Polylith Migrate Distribute Wiring

by DavidVujic in DavidVujic/python-polylith

[Internal sub-skill of polylith-migrate-orchestrator. An agent skill from DavidVujic/python-polylith.

MITAuto-check passed

Install Polylith Migrate Distribute Wiring

skills CLI
$ npx skills add DavidVujic/python-polylith --skill polylith-migrate-distribute-wiring -a claude-code

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

GitHub CLI
$ gh skill install DavidVujic/python-polylith polylith-migrate-distribute-wiring --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/DavidVujic/python-polylith.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/polylith/migrate-project/polylith-migrate-distribute-wiring .claude/skills/polylith-migrate-distribute-wiring && 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
polylith-migrate-distribute-wiring
GitHub stars
554
Token cost
~1k tokens
SKILL.md length
467 words
Files
1
Skills in repo
37
Repo updated
First seen
Licence
MIT

At a glance

[Internal sub-skill of polylith-migrate-orchestrator. An agent skill from DavidVujic/python-polylith.

  • Works in 6 steps: Read the Residual Component → Identify the Split → Extract Shared Helpers → …
  • SKILL.md covers Goal, Inputs, Steps and Verify, plus 2 more sections
  • Calls git

What it does

Polylith Migrate Distribute Wiring is an agent skill from DavidVujic/python-polylith. [Internal sub-skill of polylith-migrate-orchestrator. Do not load directly — load polylith-migrate-orchestrator first, which drives all phases.] Distribute app-wiring code from the residual component into the appropriate bases and shared components.

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

The repository describes itself as: Tooling support for the Polylith Architecture in Python. The licence is MIT.

Example prompts

  • “/polylith-migrate-distribute-wiring”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Read the Residual Component
  2. Identify the Split
  3. Extract Shared Helpers
  4. Move Composite Functions
  5. Update Tests
  6. Clean Up

What it can do on your machine

Read from SKILL.md and the folder at commit a7a80f2. 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

    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

Polylith Migrate Distribute Wiring loads about 1k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 467 words of instructions outside code blocks.

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

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 DavidVujic/python-polylith at commit a7a80f2, republished under its MIT licence (© DavidVujic). 467 words, ~1,027 tokens.

Download SKILL.mdSave it as .claude/skills/polylith-migrate-distribute-wiring/SKILL.md (or your agent's skills folder).
name
polylith-migrate-distribute-wiring
description
[Internal sub-skill of `polylith-migrate-orchestrator`. Do not load directly — load `polylith-migrate-orchestrator` first, which drives all phases.] Distribute app-wiring code from the residual component into the appropriate bases and shared components.

Skill: polylith-migrate-distribute-wiring

Goal

Distribute app-wiring code from the residual component into the appropriate bases and shared components.

Inputs

From migration/<PROJECT>/state.md:

  • TARGET_TOP_NS
  • INITIAL_BASE_NAME
  • Verification commands.
  • Base names.

From migration/<PROJECT>/manifest.md:

  • Current module map, including what remains in the residual component.

All inputs from state.md are assumed to satisfy the validation rules in polylith-migrate-discover (### Validation rules). Validate before proceeding.

Steps

1. Read the Residual Component
  • List every public function remaining in the residual module.
  • Confirm it contains only app-wiring code.
2. Identify the Split
  • Trace callers of each function (use grep).
  • Group callers by base or runner script.
  • Map each function to its natural base:
Function PatternBelongs InRationale
init_consumer, close_consumerHandler/consumer baseKafka consumer lifecycle is handler-specific
init_jobJobs baseJob bootstrap is jobs-specific
init_api / app factoryAPI baseHTTP server setup is API-specific
3. Extract Shared Helpers
  • Identify shared init functions (e.g., init_logging, init_db).
  • Move shared helpers to a bootstrap component if needed.
4. Move Composite Functions
  • Move composite functions to their respective bases.
  • Update runner scripts to import from the base directly.
5. Update Tests
  • Update integration tests to monkeypatch the correct module.
6. Clean Up
  • Delete the residual component directory.
  • Update pyproject.toml to remove the residual brick.

Verify

  • RUN_TEST_CMD succeeds.
  • If set, RUN_LINT_CMD and RUN_TYPECHECK_CMD succeed.
  • Run POLY_CMD_PREFIX check to validate the workspace structure.
  • Run POLY_CMD_PREFIX sync to synchronize the [tool.polylith.bricks] table with actual imports.
Show full SKILL.md (240 more words)Show less

Common failure modes

SymptomLikely causeRemediation
Two bases now import the same init_<x> function and the residual still existsStep 6 wasn't reached — the function moved into one base but the residual reference wasn't deleted.Confirm the residual is gone; if init_<x> is genuinely shared by 2+ bases, it belongs in a shared bootstrap component (step 3), not in either base.
mock.patch("<TARGET_TOP_NS>.<INITIAL_BASE_NAME>.init_api") fails after the moveThe test references the old residual path; the function now lives in a base.Update mock patch strings to the new location, typically <TARGET_TOP_NS>.<base_name>.<init_func>.
poly check says the residual brick is still declared but its files are gonepyproject.toml [tool.polylith.bricks] still lists the deleted brick.Remove the line from [tool.polylith.bricks] and re-run POLY_CMD_PREFIX sync --quiet.
Application starts but a runtime feature is missing (e.g., logging, DB)A shared init helper was moved into one base only. The other base never calls it.Promote the helper to a shared bootstrap component and call it from every base's startup path.
Verification fails and you can't quickly diagnosePhase commit not yet made.git reset --hard HEAD to roll back to the previous phase's commit and consult the user.

Commit

After verification passes, commit this phase to the migration branch:

bash
git add -A && git commit -m "migrate(<PROJECT>): phase <N> — distribute-wiring"

Substitute <PROJECT>, <N>, and <phase-name> from state.md and the orchestrator's phase table. Do not proceed to the next phase without a clean commit — the per-phase commit is the rollback point for the next phase's failure-mode tables.

© DavidVujic, 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 .agents/skills/polylith/migrate-project/polylith-migrate-distribute-wiring of DavidVujic/python-polylith.

Open the folder on GitHubat commit a7a80f2

Compare with similar skills

Polylith Migrate Distribute Wiring 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.

Polylith Migrate Distribute Wiring compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Polylith Migrate Distribute Wiring this skillDavidVujic/python-polylith554—~1kAutomated safety check: PassMIT
Migrate Internal Package into GhostTryGhost/Ghost56k—~3.8kAutomated safety check: PassMIT
Reversible MigrationJuliusBrussee/caveman111k1 repos~196Automated safety check: PassApache-2.0
Distributed Triagepytorch/pytorch104k—~2.8kAutomated safety check: PassCustom licence
Database Migrationsaffaan-m/ECC276k4 repos~3kAutomated safety check: PassMIT
Database Migrationsaffaan-m/ECC276k1 repos~2.4kAutomated safety check: PassMIT

Similar skills

  • Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    56k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Reversible Migration

    JuliusBrussee/caveman

    Implement reversible compatibility-safe transitions. Use for schema, data, API, protocol, configuration, or dependency migrations requiring rollback and…

    111k GitHub starsUsed in 1 repo~196 tokens
    DevelopmentAuto-check passed
  • Distributed Triage

    pytorch/pytorch

    Sub-triages issues in the oncall:distributed queue by assigning distributed module labels, routing to sub-oncalls, and marking triaged.

    104k GitHub stars~2.8k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Safe, reversible database migration patterns: forward-only production changes, expand-contract zero-downtime renames, concurrent indexes, batched backfills, and per-tool workflows for PostgreSQL…

    276k GitHub starsUsed in 4 repos~3k tokens
    DatabasesAuto-check passed
  • Şema değişiklikleri, veri migration'ları, rollback'ler ve PostgreSQL, MySQL ve yaygın ORM'ler (Prisma, Drizzle, Django, TypeORM, golang-migrate) arasında sıfır kesinti deployment'ları için…

    276k GitHub starsUsed in 1 repo~2.4k tokens
    DatabasesAuto-check passed
  • Rules and examples for safe, reversible schema changes in production: zero-downtime column and index changes, large data backfills and ORM migration workflows.

    276k GitHub stars~3.3k tokensUpdated today
    DatabasesAuto-check passed

More from DavidVujic/python-polylith

All 37 skills in this repo
  • Polylith Base Creation

    DavidVujic/python-polylith

    Create a Polylith base with poly create base — the entry point of a deployable application (HTTP API, CLI, message-queue consumer, AWS Lambda handler, GCP Cloud Function, scheduled job).

    554 GitHub stars~757 tokensUpdated 6 days ago
    Auto-check passed
  • Polylith Check

    DavidVujic/python-polylith

    Validate a Polylith workspace with poly check — the canonical CI gate.

    554 GitHub stars~972 tokensUpdated 6 days ago
    Auto-check passed
  • Polylith Component Creation

    DavidVujic/python-polylith

    Create a Polylith component with poly create component — a reusable, isolated brick implementing business logic, a feature, a domain module, or a capability.

    554 GitHub stars~800 tokensUpdated 6 days ago
    Auto-check passed
  • Polylith Dependency Management

    DavidVujic/python-polylith

    Add or manage third-party dependencies in a Polylith workspace.

    554 GitHub stars~643 tokensUpdated 6 days ago
    Auto-check passed
  • Polylith Dependency Visualization

    DavidVujic/python-polylith

    Visualize brick × brick dependencies with poly deps — find circular dependencies, inspect a brick's public interface, and detect interface-bypass violations.

    554 GitHub stars~906 tokensUpdated 6 days ago
    Auto-check passed
  • Polylith Diff

    DavidVujic/python-polylith

    List Polylith bricks whose implementation changed since a git tag using poly diff.

    554 GitHub stars~1.1k tokensUpdated 6 days ago
    Auto-check passed

Questions about Polylith Migrate Distribute Wiring

What does Polylith Migrate Distribute Wiring do?

[Internal sub-skill of polylith-migrate-orchestrator. An agent skill from DavidVujic/python-polylith. Polylith Migrate Distribute Wiring is an agent skill from DavidVujic/python-polylith. [Internal sub-skill of polylith-migrate-orchestrator.

How do I install Polylith Migrate Distribute Wiring in Claude Code?

Run `npx skills add DavidVujic/python-polylith --skill polylith-migrate-distribute-wiring -a claude-code`. Or copy the skill folder (.agents/skills/polylith/migrate-project/polylith-migrate-distribute-wiring in DavidVujic/python-polylith) into .claude/skills/polylith-migrate-distribute-wiring in your project. Claude Code loads it when a task matches its description.

How do I install Polylith Migrate Distribute Wiring in Codex?

Run `npx skills add DavidVujic/python-polylith --skill polylith-migrate-distribute-wiring -a codex`. Or copy the skill folder (.agents/skills/polylith/migrate-project/polylith-migrate-distribute-wiring in DavidVujic/python-polylith) into .agents/skills/polylith-migrate-distribute-wiring in your project. Codex loads it when a task matches its description.

Can I use Polylith Migrate Distribute Wiring 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 DavidVujic/python-polylith --skill polylith-migrate-distribute-wiring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/polylith-migrate-distribute-wiring, .gemini/skills/polylith-migrate-distribute-wiring, .github/skills/polylith-migrate-distribute-wiring and .opencode/skills/polylith-migrate-distribute-wiring in your project.

What does Polylith Migrate Distribute Wiring need to run?

Going by SKILL.md and its folder, Polylith Migrate Distribute Wiring needs the command-line tools its instructions call (git).

Does Polylith Migrate Distribute Wiring 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 Polylith Migrate Distribute Wiring 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 Polylith Migrate Distribute Wiring use?

Polylith Migrate Distribute Wiring 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 Polylith Migrate Distribute Wiring use?

About 1k tokens (SKILL.md is roughly 4.1k 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 Polylith Migrate Distribute Wiring?

Skills that share tags, products or a category with Polylith Migrate Distribute Wiring: Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars), Reversible Migration (JuliusBrussee/caveman, 111k stars), Distributed Triage (pytorch/pytorch, 104k stars) and Database Migrations (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Polylith Migrate Distribute Wiring?

DavidVujic (a GitHub user) maintains it in DavidVujic/python-polylith, which has 554 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 4, 2026.

Source: DavidVujic/python-polylith on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.