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

Polylith Migrate Extract To Base

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 Extract To Base

skills CLI
$ npx skills add DavidVujic/python-polylith --skill polylith-migrate-extract-to-base -a claude-code

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

GitHub CLI
$ gh skill install DavidVujic/python-polylith polylith-migrate-extract-to-base --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-extract-to-base .claude/skills/polylith-migrate-extract-to-base && 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-extract-to-base
GitHub stars
553
Token cost
~1.3k tokens
SKILL.md length
545 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 7 steps: Create the Base Directory → Move Application Code → Update pyproject.toml → …
  • SKILL.md covers Goal, Inputs, Steps and Verify, plus 2 more sections
  • Calls git

What it does

Polylith Migrate Extract To Base 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.] Extract all application code from projects/<PROJECT/ into a temporary migration base.

Its SKILL.md is about 1.3k 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-extract-to-base”

Workflow steps

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

  1. Create the Base Directory
  2. Move Application Code
  3. Update pyproject.toml
  4. Fix Imports
  5. Update manifest.md
  6. Handle Namespace Changes
  7. Use Shims if Needed

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 Extract To Base loads about 1.3k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 545 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.3k

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). 545 words, ~1,333 tokens.

Download SKILL.mdSave it as .claude/skills/polylith-migrate-extract-to-base/SKILL.md (or your agent's skills folder).
name
polylith-migrate-extract-to-base
description
[Internal sub-skill of `polylith-migrate-orchestrator`. Do not load directly — load `polylith-migrate-orchestrator` first, which drives all phases.] Extract all application code from `projects/<PROJECT>/` into a temporary migration base.

Skill: polylith-migrate-extract-to-base

Goal

Extract all application code from projects/<PROJECT>/ into a temporary migration base (bases/<TARGET_TOP_NS>/<INITIAL_BASE_NAME>/).

Inputs

From migration/<PROJECT>/state.md:

  • PROJECT_DIR
  • ORIG_TOP_NS
  • TARGET_TOP_NS (default: ORIG_TOP_NS)
  • INITIAL_BASE_NAME
  • RUN_TEST_CMD (optional: RUN_LINT_CMD, RUN_TYPECHECK_CMD)

From migration/<PROJECT>/manifest.md:

  • Directory tree and module map.

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

Steps

1. Create the Base Directory
  • Create bases/<TARGET_TOP_NS>/<INITIAL_BASE_NAME>/.
2. Move Application Code
  • Move application packages/modules from projects/<PROJECT>/ to the base:
    • For src/ layout: Move projects/<PROJECT>/src/<pkg>/ under the base.
    • For flat layout: Move projects/<PROJECT>/<pkg>/ under the base.
  • Leave non-code files (Dockerfiles, k8s manifests, deploy scripts, pyproject.toml) in projects/<PROJECT>/.
3. Update pyproject.toml
  • Add the base to [tool.polylith.bricks]:
    toml
    [tool.polylith.bricks]
"../../bases/<TARGET_TOP_NS>/<INITIAL_BASE_NAME>" = "<TARGET_TOP_NS>/<INITIAL_BASE_NAME>"
4. Fix Imports
  • Update imports minimally to ensure tests and linting pass.
5. Update manifest.md
  • Reflect the new structure in migration/<PROJECT>/manifest.md.
6. Handle Namespace Changes

If TARGET_TOP_NS != ORIG_TOP_NS, the migration orchestrator will handle this in subsequent phases:

  1. polylith-migrate-generate-shim will create a compatibility shim at projects/${PROJECT}/${ORIG_TOP_NS}/__init__.py that re-exports from ${TARGET_TOP_NS}.${INITIAL_BASE_NAME}.
  2. polylith-migrate-automate-import-updates will update imports in the new base location (at bases/${TARGET_TOP_NS}/${INITIAL_BASE_NAME}/) to reference the new namespace.
  3. polylith-migrate-update-tests will update test files to use the compatibility shim.
7. Use Shims if Needed
  • If imports break during this phase, add minimal temporary shims to re-export names from the new brick API.
  • Track shims in migration/shims.md.
  • Note that comprehensive shim generation will be handled in the polylith-migrate-generate-shim phase.

Verify

  • RUN_TEST_CMD succeeds with the same pass/fail counts as the pre-migration baseline recorded in polylith-migrate-discover.
  • 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 (280 more words)Show less

Common failure modes

SymptomLikely causeRemediation
ModuleNotFoundError: No module named '<ORIG_TOP_NS>.<x>' after moveTARGET_TOP_NS != ORIG_TOP_NS and imports weren't rewritten or shimmed.This is resolved by later phases per SHIM_STRATEGY (chosen in polylith-migrate-analyze-imports): shimless rewrites every reference in polylith-migrate-automate-import-updates (phase 4); shim adds a re-export shim under ORIG_TOP_NS in the phase 4b sub-track (polylith-migrate-generate-shim). To keep this phase green in the meantime, add a minimal temporary shim and record it in migration/shims.md (step 7).
RUN_TEST_CMD collects 0 tests after the moveTest files moved but pytest rootdir / testpaths still points at the old projects/<PROJECT>/tests location.Update pyproject.toml [tool.pytest.ini_options].testpaths or pass explicit dirs in RUN_TEST_CMD. (Note: polylith-migrate-prepare-project moves tests properly — if extract-to-base touched tests at all, consider undoing that part.)
poly check reports "brick imports another brick that is not in [tool.polylith.bricks]"Step 3 only added the base; imports inside the base may pull in components not yet listed.Run POLY_CMD_PREFIX sync --quiet to populate the rest, then re-run check.
Editable install / build fails (error: package directory '<x>' does not exist)The base move broke the previous [tool.setuptools] or [tool.hatch.build] packages setting in projects/<PROJECT>/pyproject.toml.Update packages to point at the new <TARGET_TOP_NS> namespace, or remove the explicit packages setting and let Polylith's build hook handle it.
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> — extract-to-base"

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-extract-to-base of DavidVujic/python-polylith.

Open the folder on GitHubat commit a7a80f2

Compare with similar skills

Polylith Migrate Extract To Base 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 Extract To Base compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Polylith Migrate Extract To Base this skillDavidVujic/python-polylith553—~1.3kAutomated safety check: PassMIT
Migrate Internal Package into GhostTryGhost/Ghost56k—~3.8kAutomated safety check: PassMIT
Reversible MigrationJuliusBrussee/caveman111k1 repos~196Automated safety check: PassApache-2.0
Database Migrationsaffaan-m/ECC276k4 repos~3kAutomated safety check: PassMIT
Database Migrationsaffaan-m/ECC276k1 repos~2.4kAutomated safety check: PassMIT
Migrate Styled Components To Vanilla Extractsanity-io/sanity6.4k—~5.8kAutomated safety check: PassMIT

Similar skills

  • Migrate Internal Package into Ghost

    TryGhost/Ghost

    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

  • Database Migrations

    affaan-m/ECC

    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

  • Database Migrations

    affaan-m/ECC

    Ş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

  • Migrate Styled Components To Vanilla Extract

    sanity-io/sanity

    Official

    Step-by-step procedure for migrating components in the Sanity monorepo off styled-components to vanilla-extract (zero-runtime CSS).

    6.4k GitHub stars~5.8k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • Od Code Migration

    nexu-io/open-design

    Default reference pipeline for the code-migration taskKind — code-import → design-extract → token-map → rewrite-plan → patch-edit ↔ build-test devloop → diff-review → handoff.

    100k GitHub stars~378 tokensUpdated today
    DevelopmentAuto-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).

    553 GitHub stars~757 tokensUpdated 5 days ago
    Auto-check passed

  • Polylith Check

    DavidVujic/python-polylith

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

    553 GitHub stars~972 tokensUpdated 5 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.

    553 GitHub stars~800 tokensUpdated 5 days ago
    Auto-check passed

  • Polylith Dependency Management

    DavidVujic/python-polylith

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

    553 GitHub stars~643 tokensUpdated 5 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.

    553 GitHub stars~906 tokensUpdated 5 days ago
    Auto-check passed

  • Polylith Diff

    DavidVujic/python-polylith

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

    553 GitHub stars~1.1k tokensUpdated 5 days ago
    Auto-check passed

Questions about Polylith Migrate Extract To Base

What does Polylith Migrate Extract To Base do?

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

How do I install Polylith Migrate Extract To Base in Claude Code?

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

How do I install Polylith Migrate Extract To Base in Codex?

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

Can I use Polylith Migrate Extract To Base 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-extract-to-base -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-extract-to-base, .gemini/skills/polylith-migrate-extract-to-base, .github/skills/polylith-migrate-extract-to-base and .opencode/skills/polylith-migrate-extract-to-base in your project.

What does Polylith Migrate Extract To Base need to run?

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

Does Polylith Migrate Extract To Base 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 Extract To Base 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 Extract To Base use?

Polylith Migrate Extract To Base 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 Extract To Base use?

About 1.3k tokens (SKILL.md is roughly 5.3k 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 Extract To Base?

Skills that share tags, products or a category with Polylith Migrate Extract To Base: Migrate Internal Package into Ghost (TryGhost/Ghost, 56k stars), Reversible Migration (JuliusBrussee/caveman, 111k stars), Database Migrations (affaan-m/ECC, 276k 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 Extract To Base?

DavidVujic (a GitHub user) maintains it in DavidVujic/python-polylith, which has 553 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.