Loading...
Loading...
Found 11,542 Skills
Opt-in approval-first, whole-working-tree wrapper for the commit skill. Defaults to grouping all changes and requires the commit skill; selected installs must also install commit. Activate only when the user explicitly invokes `$commit-confirm` or explicitly asks to use the named commit-confirm skill. Do not activate merely because the user asks to review or propose commits, ask before committing, or wait for "go".
Opt-in evidence-first causal diagnosis for bugs, browser or app/device failures, flaky behavior, and performance regressions. Activate only when the user explicitly invokes `$diagnose` or explicitly asks to use the named diagnose skill. Do not activate merely because the user mentions a bug, asks why something failed, requests debugging or a fix, or describes unexpected behavior. Once explicitly invoked, locate likely causes, instrument relevant boundaries with extensive structured logging, reproduce the issue, analyze the collected logs, rank causes with confidence scores, and pursue 100% operational confidence while probes can increase confidence.
La puerta de entrada del kit — de un clon recién bajado a un cerrador andando, local o en Railway.
This skill should be used when the user asks to "rotate SSH keys", "regenerate SSH keys", "replace SSH keys", "renew SSH keys", or when the agent needs SSH access to a deployed VM for troubleshooting (logs, debugging, database access) but discovers the expected SSH key file is missing from the local disk (e.g. `~/.ssh/<repo-name>` does not exist). Also use when the user mentions "lost SSH key", "SSH key not found", "can't SSH into server", "permission denied SSH", "moved to a new computer", or "cloned repo on another machine".
Deterministic issue-relationship graph over GitHub native sub-issues + dependencies — compute the ready set / parent-rollup candidates / close-kick targets as pure calculation (scripts, no LLM judgment), write real edges when creating spin-off issues, and mutually exclude terminal actions across parallel agents via claim-comment fencing. Called by issue-sweep (candidate injection), issue-review (edge writing + rollup), and the future agent:ready producer routine.
One-time setup that maps direct competitors, alternatives, and category substitutes for the current project from the codebase, user input, and external research, then writes a root COMPETITORS.md. Use when the user invokes $setup-competitors-md, says "setup competitors", "create COMPETITORS.md", "competitive landscape", or asks to document rivals and differentiation for the project.
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents
Assisted Skill for Credit Application Submission. Automatically inventory notes and materials in customer files, assess completeness against the bank's pre-loan due diligence material standards, check for case conflicts and credit expiration status, generate a structured assessment report, and guide account managers to confirm submission. This Skill is used when users need to submit credit applications, initiate approval processes, apply for loan renewal, apply for additional credit, or assess whether materials are complete. Trigger words include: "submit credit application", "initiate approval", "submit credit", "loan renewal application", "additional credit application", "assess materials", "credit application submission", "initiate credit process". Not applicable to: post-loan management, risk classification adjustment, non-performing asset disposal, credit approval decision-making, or general consultations without specific customer background.
Проводит независимое ревью изменений кода без их исправления. Используй, когда пользователь явно просит проверить код, коммит, ветку, pull request или diff на соответствие задаче, корректность, безопасность, производительность и качество тестов. Не используй, когда пользователь просит изменить код, реализовать задачу или сначала найти причину проблемы.
Создаёт memory bank проекта с нуля и выполняет его первичное заполнение. Используй только при явном вызове /bro-init-memory-bank, когда пользователь хочет создать новый банк знаний проекта. Не используй для пополнения существующего memory bank или сохранения отдельного проектного решения.
Помогает совместно прояснить задачу, проверить идею, найти корневую причину проблемы или выбрать подход без реализации. Используй, когда пользователь просит обсудить задачу, разобраться в проблеме, сравнить варианты или задаёт вопросы «что думаешь?» и «как лучше сделать?». Не используй, когда пользователь явно просит составить план, реализовать задачу, проверить изменения кода или сохранить знания проекта.
Enable a symmetric collaborative closed-loop of "Primary Executor + Independent Reviewer" between Codex and Claude Code via native CLI. This applies when users require the two models to work together, cross-validate, conduct independent reviews, revise until ACK, or when tasks involve product requirement convergence, complex solutions, cross-module development, migration, security, major refactoring, and high-quality delivery; regardless of whether initiated from Codex or Claude Code, the current model will take charge and fully invoke the other party to complete requirement challenge, scheme gatekeeping, implementation cold review, and final acceptance.