mkl-bump-version
Evaluate conventional commits since latest tag, determine next SemVer, and surgically update version files.
38,472 Skills
Search uses this published catalog; rankings and counts are snapshots.
Evaluate conventional commits since latest tag, determine next SemVer, and surgically update version files.
Resolve static type checker errors (mypy, pyright) using localized symbol-level diagnostics without whole-file rewrites. Use when type checks fail on candidate patches.
Generate grouped, token-compact changelogs and release notes from git log.
Generate concise Conventional Commits under 50 tokens from staged git diffs.
Offload verbose reasoning, trial commands, and intermediate drafts to ephemeral scratch files to preserve context tokens.
Isolate suspect files and line ranges before code repair using AST skeletons and stack traces (< 300 tokens). Use before editing code to prevent full-file context dumps.
Translate and localize Polish and English technical documentation, UI text, and project updates. Use for natural PL/EN phrasing while preserving commands, placeholders, factual precision, and a project glossary.
Prepare release notes and migration guidance from a verified revision range and project release policy. Use for release preparation; never present open PRs or planned changes as shipped features.
Analyze cProfile or py-spy tables to optimize real bottlenecks without code guessing.
Prune verbose histories, logs, and resolved turns during long debugging or triage sessions into a stateful compact handoff.
Reduce a reported software bug to a runnable, minimal reproduction with the exact command, environment, and observed failure. Use when verifying a bug report; do not infer success from a failing setup command.
Review a pull request for concrete correctness regressions using its diff, surrounding code, and relevant tests. Use for a requested PR review; distinguish actionable defects from optional preferences.
Turn a repository issue into an evidence-backed triage note: observed behavior, missing reproduction details, possible duplicates, and the next useful action. Use for issue triage, not implementation or bulk issue closure.
Draft clear, respectful replies to issues, PR discussions, and technical support reports from available evidence. Use to explain status, request a minimal reproduction, or communicate a project decision without inventing commitments.
Write a focused regression test from an established bug reproduction and public behavior. Use when a fix needs a test that fails on the affected version; avoid mirroring the implementation or weakening assertions.
Write or revise interface labels, errors, empty states, and confirmation text from actual product behavior. Use for UI microcopy with clear next actions, preserved localization tokens, and explicit length constraints.
Catalog captured:2026-11-21