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 Definition Of Done

by DavidVujic in DavidVujic/python-polylith

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

MITAuto-check passedTesting & QA

Install Polylith Migrate Definition Of Done

skills CLI
$ npx skills add DavidVujic/python-polylith --skill polylith-migrate-definition-of-done -a claude-code

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

GitHub CLI
$ gh skill install DavidVujic/python-polylith polylith-migrate-definition-of-done --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-definition-of-done .claude/skills/polylith-migrate-definition-of-done && 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-definition-of-done
GitHub stars
554
Token cost
~1.5k tokens
SKILL.md length
663 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 2 steps: Baseline test count restored → No undocumented shims remain
  • Testing & QA work in your project
  • SKILL.md covers Done When, End-to-end checks, Verify and Common failure modes, plus 1 more section
  • Calls git and pytest

What it does

Polylith Migrate Definition Of Done 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.] Define the criteria for completing the migration process.

Its SKILL.md is about 1.5k 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 Testing & QA. The repository describes itself as: Tooling support for the Polylith Architecture in Python. The licence is MIT.

When your agent uses it

  • Testing & QA work in your project

Example prompts

  • “/polylith-migrate-definition-of-done”

Workflow steps

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

  1. Baseline test count restored
  2. No undocumented shims remain

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
    • pytest

    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 Definition Of Done loads about 1.5k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 663 words of instructions outside code blocks.

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

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). 663 words, ~1,544 tokens.

Download SKILL.mdSave it as .claude/skills/polylith-migrate-definition-of-done/SKILL.md (or your agent's skills folder).
name
polylith-migrate-definition-of-done
description
[Internal sub-skill of `polylith-migrate-orchestrator`. Do not load directly — load `polylith-migrate-orchestrator` first, which drives all phases.] Define the criteria for completing the migration process.

Skill: polylith-migrate-definition-of-done

Done When

Structure
  • Temporary migration base is gone or thin.
  • Bases contain only entrypoints/wiring.
  • All non-entrypoint code lives in components.
Source Project
  • projects/<PROJECT>/ contains only:
    • Packaging config (pyproject.toml).
    • Runner scripts and task runners (Makefile, Justfile).
    • Project-specific config (e.g., alembic.ini).
  • Project pyproject.toml references all required bricks.
  • Brick names are meaningful and non-generic.
  • Base names are project-prefixed to avoid collisions.
Tests
  • Tests are moved from projects/<PROJECT>/tests/ to workspace level (required).
  • Unit-test layout — one of the following (see polylith-migrate-refactor-tests):
    • Per-brick (theme-aligned): loose → test/bases/<TARGET_TOP_NS>/<base>/ and test/components/<TARGET_TOP_NS>/<component>/; tdd → bases/<base>/test/<TARGET_TOP_NS>/<base>/ and components/<component>/test/<TARGET_TOP_NS>/<component>/. Or
    • Workspace-level service dir test/<svc>_service/ — valid when shared test helpers can't cheaply become fixtures (the namespace-merge hazard makes a per-brick split unsafe otherwise). Record the chosen layout in state.md.
  • Integration tests live in a shared location (e.g., test/integration/ or test/<svc>_service/integration/).
  • Shared fixtures live in a conftest.py (e.g. test/<TARGET_TOP_NS>/conftest.py, test/conftest.py, or the service dir's conftest.py).
  • RUN_TEST_CMD points to the test root and collects the same number of tests as the pre-migration baseline.
Infrastructure
  • Infrastructure folders are moved to infra/<folder>/<project-name>/, or the move is deferred with a documented rationale in state.md when the deploy cannot be verified in the migration environment (see polylith-migrate-prepare-project). Either way, alembic/ stays with alembic.ini in the project.
Interfaces
  • Each component defines its public API via __init__.py.
  • Bricks import each other via those APIs.
Linting and Type-Checking
  • Linting/formatting and type-checking use the workspace's configured tool(s).
  • RUN_LINT_CMD and RUN_TYPECHECK_CMD pass if set. They may be intentionally empty when the project's pre-migration baseline already failed these gates (recorded in polylith-migrate-discover); pre-existing violations are not the migration's responsibility — note them as a follow-up rather than blocking the migration.
Dependencies
  • Workspace root pyproject.toml contains all third-party dependencies with version constraints.
  • Project pyproject.toml lists runtime dependencies without version numbers.
Cleanup
  • Migration artifacts (migration/<PROJECT>/state.md, migration/<PROJECT>/manifest.md, and any migration/shims.md) are either removed or kept under migration/<PROJECT>/ for reference (user's choice).
  • The migration branch (GIT_BRANCH from state.md) is ready to be merged or rebased into the main branch. Per-phase commits remain available for review/bisect.

End-to-end checks

These checks go beyond per-phase verification and exercise the migrated project as a whole. Both must pass.

1. Baseline test count restored

Compare collected test count to the baseline recorded by polylith-migrate-discover:

bash
<RUN_TEST_CMD_with --collect-only -q | tail -1>

The count must equal the baseline. A lower count means pytest discovery is misconfigured (see polylith-migrate-refactor-tests failure modes). A higher count means tests were inadvertently duplicated during the move.

Show full SKILL.md (274 more words)Show less
2. No undocumented shims remain

Inspect migration/<PROJECT>/shims.md (if it exists):

  • Empty or absent → ✅ proceed.
  • Lists active shims → either remove them now (rewrite imports to the new namespace and delete the shim modules) or schedule their removal as a follow-up PR and reference that PR in the migration branch description. Do not merge with undocumented shims.

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 info to inspect the workspace and confirm all projects and bricks are correctly registered.

Common failure modes

SymptomLikely causeRemediation
RUN_TEST_CMD passes but collected test count is lower than the baseline from polylith-migrate-discoverpytest discovery is misconfigured after the test reorganisation.Update [tool.pytest.ini_options].testpaths (or pass paths explicitly in RUN_TEST_CMD). Run pytest --collect-only and diff against baseline collection. See polylith-migrate-refactor-tests for details.
poly check is green and tests pass, but a base imports something that no longer exists at the expected pathEntrypoint wiring regression introduced while moving code into bases/components.Verify each base's entrypoint module imports cleanly and that its wiring matches the original. Revisit polylith-migrate-distribute-wiring.
migration/shims.md still lists active shimsShims from polylith-migrate-extract-to-base (namespace change) were never removed.Either rewrite imports to the new namespace and delete the shims, or schedule shim removal as a follow-up PR and note it in the migration branch description. Do not merge with undocumented shims.

Commit

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

bash
git add -A && git commit -m "migrate(<PROJECT>): phase <N> — definition-of-done"

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-definition-of-done of DavidVujic/python-polylith.

Open the folder on GitHubat commit a7a80f2

Compare with similar skills

Polylith Migrate Definition Of Done 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 Definition Of Done compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Polylith Migrate Definition Of Done this skillDavidVujic/python-polylith554—~1.5kAutomated safety check: PassMIT
Pester Failure AnalysisPowerShell/PowerShell56k—~5.1kAutomated safety check: PassMIT
Rust TDD Workflowrtk-ai/rtk83k—~753Automated safety check: NotesApache-2.0
Clawteam DevHKUDS/ClawTeam5.5k1 repos~1.1kAutomated safety check: PassMIT
Browser Testing with Chrome DevToolsaddyosmani/agent-skills105k4 repos~3.5kAutomated safety check: WarnMIT
Apple Container Test RunnerRustPython/RustPython22k—~467Automated safety check: PassMIT

Similar skills

  • Pester Failure Analysis

    PowerShell/PowerShell

    Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.

    56k GitHub stars~5.1k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Rust TDD Workflow

    rtk-ai/rtk

    Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated yesterday
    Testing & QAAuto-check: notes

  • Clawteam Dev

    HKUDS/ClawTeam

    A skill your agent uses when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually…

    5.5k GitHub starsUsed in 1 repo~1.1k tokens
    Testing & QAAuto-check passed

  • Browser Testing with Chrome DevTools

    addyosmani/agent-skills

    Connects an agent to a real Chrome instance through the Chrome DevTools MCP server, so it can inspect the DOM, read console errors and profile performance directly.

    105k GitHub starsUsed in 4 repos~3.5k tokens
    Testing & QAAuto-check: warnings

  • Apple Container Test Runner

    RustPython/RustPython

    Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.

    22k GitHub stars~467 tokensUpdated today
    Testing & QAAuto-check passed

  • Codex Plugin QA

    code-yeongyu/oh-my-openagent

    Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.

    70k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-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

Categories

Questions about Polylith Migrate Definition Of Done

What does Polylith Migrate Definition Of Done do?

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

When should I use Polylith Migrate Definition Of Done?

Polylith Migrate Definition Of Done fits situations like: testing & QA work in your project.

How do I install Polylith Migrate Definition Of Done in Claude Code?

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

How do I install Polylith Migrate Definition Of Done in Codex?

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

Can I use Polylith Migrate Definition Of Done 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-definition-of-done -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-definition-of-done, .gemini/skills/polylith-migrate-definition-of-done, .github/skills/polylith-migrate-definition-of-done and .opencode/skills/polylith-migrate-definition-of-done in your project.

What does Polylith Migrate Definition Of Done need to run?

Going by SKILL.md and its folder, Polylith Migrate Definition Of Done needs the command-line tools its instructions call (git and pytest).

Does Polylith Migrate Definition Of Done 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 Definition Of Done 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 Definition Of Done use?

Polylith Migrate Definition Of Done 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 Definition Of Done use?

About 1.5k tokens (SKILL.md is roughly 6.2k 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 Definition Of Done?

Skills that share tags, products or a category with Polylith Migrate Definition Of Done: Pester Failure Analysis (PowerShell/PowerShell, 56k stars), Rust TDD Workflow (rtk-ai/rtk, 83k stars), Clawteam Dev (HKUDS/ClawTeam, 5.5k stars) and Browser Testing with Chrome DevTools (addyosmani/agent-skills, 105k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Polylith Migrate Definition Of Done?

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.