Loading...
Loading...
Found 50 Skills
Build feature command
Generate formatted changelogs from git history since the last release tag. Use when preparing release notes that categorize changes into breaking changes, features, fixes, and other sections.
Git workflow patterns for commits, branching, PRs, and history management across heterogeneous repositories. Use when creating commits, managing branches, opening pull requests, or rewriting history. Do not use for non-git implementation tasks or repo-specific release policy decisions without repository documentation.
⚠️ MANDATORY - YOU MUST invoke this skill at the start of EVERY task. Reviews git history, status, and context before starting any work. Runs parallel git commands to understand current state, recent changes, and related work. NEVER gather git context manually.
Rummage through code with curious precision, inspecting every corner for security risks and cleaning up what doesn't belong. Use when auditing security, finding secrets, removing dead code, or sanitizing before deployment.
Use this skill to quickly understand "what changed and what matters". Use when resuming work after absence, preparing handoff documentation, reviewing sprint progress, analyzing git history for context. Do not use when doing detailed diff analysis - use diff-analysis instead. DO NOT use when: full code review needed - use review-core instead.
Project status report generation from git history, task context, and milestone tracking. Use when creating weekly updates, sprint reviews, stakeholder reports, or project dashboards.
Turn many commits into a curated grouped squash summary compatible with the opinionated wording style of git-visual-commits. Use this skill whenever the user asks to squash a branch into a concise summary, write a squash-and-merge summary, summarize a commit range or PR as grouped lines, clean up noisy commit history, or asks for a curated summary without committing. Treat phrases like "squash summary", "squash commit message", "summarize this branch", "turn these commits into one summary", "rewrite these 10+ commits", or "draft the squash summary" as automatic triggers. This skill is non-mutating: it inspects git history and diffs, then returns grouped summary lines only. It preserves technical identifiers where possible, groups by intent rather than chronology, merges overlapping commits, drops low-signal noise, uses strong concrete verbs, favors readable GitHub and terminal output, keeps every output line at or below 72 characters, and does not invent unsupported changes or drift into changelog wording.
Use when converting Java source files to idiomatic Kotlin, when user mentions "java to kotlin", "j2k", "convert java", "migrate java to kotlin", or when working with .java files that need to become .kt files. Handles framework-aware conversion for Spring, Lombok, Hibernate, Jackson, Micronaut, Quarkus, Dagger/Hilt, RxJava, JUnit, Guice, Retrofit, and Mockito.
Post-mortem diagnostic analysis of failed or stuck workflows. Detects stuck loops, missing artifacts, abandoned work, scope drift, and crash/interruption patterns through git history and plan file analysis. Produces a structured diagnostic report with anomaly confidence levels, root cause hypotheses, and recommended remediation. READ-ONLY: never modifies files. Use for "forensics", "what went wrong", "why did this fail", "stuck loop", "diagnose workflow", "post-mortem", "workflow failure", or "session crashed". Do NOT use for debugging code bugs (use systematic-debugging), reviewing code quality (use systematic-code-review), or fixing issues (forensics only diagnoses).
Explains the intent behind source code by finding original session transcripts. Use explain with a function, file, or line of code to understand why it exists.
Detects hardcoded secrets, API keys, passwords, and credentials in source code. Use when checking for leaked secrets, credential exposure, or before committing code.