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.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "commit" with this command: npx skills add andrey5608/skillsmp-andrey5608-andrey5608-commit
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.
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".
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.