Explore skills

Manually-triggered comprehensive codebase health audit covering security, architecture, documentation drift, dead code, and test coverage gaps. Produces a ranked markdown report, files prioritized GitHub issues, and proposes (but never autonomously opens) auto-fix PRs for trivial safe changes. Use when the user wants to audit, scan, review the health of, do a security check on, find dead code in,

Use when the user wants to prevent broken code from being pushed, block git push when tests fail, run tests before push, set up push protection, or add a safety net against pushing untested code. Covers any request to gate pushes on test results — whether they mention "hook", "pre-push", or just describe wanting to stop bad code from reaching the remote. Also handles auto-fix/auto-repair of test f

Audits a working feature for the gap between "happy path passes" and "production-ready" — edge cases, error handling, loading/empty/error states, a11y, responsive, i18n, observability, ops hooks. Use when a feature works but needs polish, for "완성도 높여줘", "production ready로", "edge case 검토", "polish this feature", "is this ready to ship?", "엣지 케이스 다 챙겼나", "PR 전 점검", "빠진 상태 없나", or before shipping an

SAP ABAP RESTful Application Programming Model (RAP) development skill. End-to-end scope: business objects (BO), CDS data model, behavior definitions and implementations, service definitions / bindings, file uploads/downloads, metadata extensions, value helps, and RAP testing. Use when the user asks to: build a RAP BO (managed or unmanaged), model CDS view entities / table entities / projection vi

Generates a branch-vs-default comparison report with plain-language explanations and senior dev review. Use when the user asks to summarize, compare, review, or explain branch changes, or wants a PR summary before merging.

Suggests 3 commit messages based on git diff and project conventions. Use when the user asks for commit message ideas, wants help writing a commit message, or has changes ready to commit.

Use when about to commit, create a PR, or declare work complete — after verification-before-completion confirms tests pass but before code ships. Catches security vulnerabilities, logic errors, and business rule bugs that slip through despite passing tests.

Use when planning any non-trivial change — refactor, bug fix, migration, optimisation, communication — and the agent should find the natural seams / high-leverage points of the target system rather than brute-forcing through. Cut at joints (low resistance, clean result), not at bone (high resistance, blade dulls, messy result). The patron-saint chengyu of working WITH the grain of the system.

Minimal test skill for E2E testing

Use Google Gemini for parallel code reviews, complex task validation, and second opinions. Runs Gemini CLI non-interactively to provide alternative perspectives on code quality, implementation decisions, and technical solutions.

Minimal test skill for E2E testing

Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions, high fan-out, refactor candidates, code quality audit, graph query syntax, Cypher