Delegate to the `migrate-conductor-auto` agent for an autonomous Cucumber → Kotlin + JUnit 5 migration with policy-driven Draft approval and a bounded retry-with-fix loop across both verify phases (initial + post-cleanup). Human approval is retained only for the Scenario Outline port plan. Use when the user asks for a hands-free migration or runs /migrate-auto.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "migrate-auto" with this command: npx skills add andrey5608/skillsmp-andrey5608-andrey5608-migrate-auto
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Delegate to the `migrate-conductor` agent to migrate exactly one Cucumber scenario to Kotlin + JUnit 5 through the Draft → user-approval → Worker → results-verifier (initial) → Worker cleanup → results-verifier (post-cleanup) → journal pipeline. Use when the user asks to migrate a Cucumber scenario, port a `.feature` to JUnit 5, or runs /migrate. Always one scenario per run — never batch.
Append a single new entry to one of the append-only knowledge catalogs (`lessons-learned/migration.md`, `lessons-learned/cucumber-debug.md`, `lessons-learned/review.md`, `migration-patterns.md`, `migration-pitfalls.md`). Use when the user asks to record a lesson, canonical pattern, or pitfall, or says things like "remember this", "add a pattern", "record a pitfall".
Generate a concise English commit message from the staged diff (subject ≤72 chars, imperative, no trailing period, optional body only when the subject cannot carry the intent) and run `git commit` via HEREDOC after explicit user approval. Refuses `--no-verify` and `--amend`. Use when the user asks to commit staged changes or runs /commit.
Delegate to the `api-test-author` agent to write a Kotlin + JUnit 5 API test class for a specified set of endpoints in a given module, mirroring the module's existing architectural scheme (HTTP client, base class, fixtures, Allure conventions, parameterization style). Use when the user asks to create, author, or generate a new API test for a module / endpoint set, or runs /create-api-autotest.