Total Skills
9
Skills published by andrey5608 with real stars/downloads and source-aware metadata.
Total Skills
9
Total Stars
0
Total Downloads
0
Comparison chart based on real stars and downloads signals from source data.
add-lesson-learned
0
commit
0
create-api-autotest
0
debug-cucumber
0
explain-test
0
migrate-auto
0
migrate
0
review
0
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.
Diagnose a failing Cucumber scenario with a step → Kotlin step-definition trace, cross-reference to the `cucumber-debug.md` lessons catalog, and a minimal repro command. Use when the user reports a failing `.feature` scenario, pastes a Cucumber stack trace, or asks to debug a Gherkin test.
Explain a JUnit 5 Kotlin test (`.kt`) or a Cucumber scenario (`.feature`) in a structured English format (Purpose → Preconditions → Actions → Assertions → Bugs it catches → Limitations) with Allure metadata listed and, for Cucumber, a step → step-definition method trace. Use when the user asks what a test does, how it works, or to explain a `.kt` or `.feature` file.
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.
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.
Review a diff (or an explicit ref) against the pre-filled Kotlin / JUnit 5 / Cucumber / Allure backend rubric set. Emits a severity-tagged checklist with `file:line` anchors and a lesson-recording offer at the end. Use when the user asks for a code review, a diff review, or runs /review.
Scaffold a new VS Code Copilot skill at `.github/skills/<name>/SKILL.md` — interview the user for name, description, allowed-tools, target agent (if any), usage, behavior, invariants, refusals — then preview the full SKILL.md, ask for explicit `y`, write the file, and register the slash command in `.github/copilot-instructions.md`, `docs/README.md`, and `docs/jetbrains-cheatsheet.md`. Use when the user asks to create a new skill, add a new slash command, or runs /skill-creator.