Найдите подходящую возможность для вашего агента.
Commit and ship a branch to production by rebasing the current branch onto local production, fast-forwarding production, pushing both branches, and switching back to main. Use when a user asks to /ship, ship changes, ship everything, or to perform this exact production shipping workflow.
A comprehensive guide and set of instructions for performing code reviews on the codebase.
Submit code review requests to multiple AI providers (GitHub Copilot, Anthropic Claude, OpenAI Codex, Google Gemini) and get patches back. Use when user says "code review", "review this code", "get a patch for", or needs AI-generated unified diffs for code fixes.
Follow project-wide development conventions including consistent project structure, clear documentation, version control best practices, environment configuration, and dependency management. Use this skill when organizing project files and directories, writing README files, creating commit messages, managing environment variables, or handling dependencies. When working with configuration files, documentation files, package managers, or version control. When setting up new features, organizing code structure, or maintaining project documentation. This skill applies when working with project structure, `.env` files, `package.json`, `requirements.txt`, `Gemfile`, README files, and any project-level configuration.
Fetch, preview, test, and merge GitHub PRs locally. Use when the user wants to evaluate a PR before merge.
Create a git worktree for a bd issue. Use when spawning a worker agent for an issue. Keywords: worktree, worker, spawn, parallel, issue.
Jujutsu (jj) is a powerful Git-compatible version control system with innovative features like automatic rebasing, working-copy-as-a-commit, operation log with undo, and first-class conflict tracking. This skill is triggered when the user says things like "use jj", "run jj commands", "jujutsu version control", "migrate from git to jj", "jj rebase", "jj squash", "jj log", or "help with jj workflow".
Format git commits with proper standards, signatures, and conventional commit format. Use when user says "commit", "create commit", "format commit message", or when staging changes for commit.
This skill teaches how to manage stacked PRs (pr1 → pr2 → pr3) after the base PR merges. Covers rebasing dependent PRs onto the updated base branch using cherry-pick workflow. Use this when you have a chain of dependent PRs and need to update them after merging earlier PRs in the stack.
Update existing pull request title and description based on latest changes. Use when user wants to refresh PR with latest commits. Triggers include: - Korean: "PR 업데이트해줘", "PR 수정해줘", "PR 다시 만들어줘" - English: "update PR", "refresh PR", "regenerate PR description" - Context: User has existing PR and wants to update title/description after adding more commits
Use when running /ltk:sync-submodules, updating submodules, or needing to "sync", "merge", "adapt", "learn from" other Claude Code plugins or repos
This skill should be used when the user asks about "interpreting ctx-monitor traces", "understanding execution logs", "reading trace files", "what do ctx-monitor events mean", "debugging trace output", or needs guidance on trace file formats, event types, common failure patterns, or troubleshooting ctx-monitor output.
Structured logging with Pino for this project. Environment-aware configuration, context-based child loggers, ILogger adapter for compatibility. Triggers on "logging", "logger", "createLogger", "pino", "structured logging".
Automatically investigate logs when errors occur, debugging issues, or troubleshooting problems. Check frontend logs (LogViewer) and backend logs (daily log files) for error patterns. Use when user reports bugs, errors appear, or functionality isn't working as expected.
JSON-based structured logging for audit trails and debugging. Use for logging all agent operations, quality metrics, errors, and execution times with daily rotation and automatic cleanup.
Refactors Grafana Jsonnet dashboards to eliminate duplication and align with available unified libraries while preserving behavior. Use when dashboards contain duplicated code, inconsistent patterns, legacy panel types, or need standardization with existing conventions. Produces single self-contained files without dashboard-specific libraries.
Design and implement wide-event logging with tail sampling for context-rich, queryable observability
Follow these patterns when implementing activity emission and audit logging in OptAIC. Use for emitting ActivityEnvelopes on mutations (create, update, delete, execute), designing payloads, and ensuring audit compliance.
Ensure every critical action is logged (vital for UAG/Trust Room).
