Loading...
Loading...
Found 3,098 Skills
Ship the current work. If the branch has an open PR (e.g. from a manual /engineer), merge it once CI is green; otherwise run the validation pipeline plus the tests relevant to the changed files, then commit and push. Use only when the user explicitly invokes /shipit. Never auto-ship.
Set up, supervise, and control a persistent multi-layer "explore → execute → escalate" agent loop on a project. Use whenever a user asks to keep an agent running on a task across sessions or days — finding bugs, polishing writing, distilling a style, watching feeds, scanning for gaps, or any task whose value grows with how many findings the agent produces. Also use when the user wants to inspect, pause, resume, stop, or send a new instruction to an already-running perpetuum task.
Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.
Generate ultra-compact commit messages. Follows the Conventional Commits format with subject ≤50 characters, prioritizing "why" over "what". Supports both Japanese and English. Trigger with "Make a commit message", "/commit", or "/genshijin-commit". Auto-trigger candidate when staging changes.
Triage and orchestrate code reviews. Analyzes PR intent, identifies touched surfaces, assesses risk, and routes to specialist skills. Does NOT perform detailed review - delegates to specialists. Supports full pipeline with "Review PR <number>" command.
Create a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.
Gitコミットを日付ごとに集計してMarkdownテーブルで出力するスキル。 機能: (1) 指定日のコミット一覧取得 (2) worktree含む全ブランチ対応 (3) PR番号の自動取得 (4) JST時刻でのテーブル出力
Use this to write commit messages unless specific commit message conventions are explicitly specified.
Open a pull request the bklit-ui way: stage and commit with pre-commit hooks, run ultracite from the repo root, run a production test build, fix failures, push, and create a PR with a structured summary. Use when the user asks to commit, push, open a PR, "ship it", or run the full pre-PR checklist.
Analyse a repository to identify its focus, technology stack, and labels, then search for and apply appropriate shields.io badges to markdown files.
Cache Playwright browser binaries in CI/CD pipelines (GitHub Actions, Azure DevOps) to avoid 1-2 minute download overhead on every build.
Scan the codebase for potential secret leaks including API keys, tokens, passwords, hardcoded project IDs, and sensitive identifiers. Use when the user says "check for secrets", "scan for leaks", "security check", or before committing sensitive changes.