'commit' 검색 결과

Use when the user asks to "build our social crisis protocol", "mentions are exploding — what do we do first", or "when do we pause the posting queue"; produces a 1-5 severity ladder with tunable Estimated trigger thresholds (mention-velocity multiples vs the 7-day listening baseline, sentiment flip, journalist/regulator contact, employee-conduct class), the first-mechanical-action rule — pause ALL scheduled posts AND paid amplification, with dated state markers dropped to the channels proposal protocol and reconciled post-incident — a pre-approved holding-statement library with committed update cadences, when-NOT-to-post rules, a spokesperson/approval matrix, and a post-crisis retro template; re-runs the social-quality-auditor pre-publish gate before un-pausing the queue. Not for email deliverability incidents (blocklist, spam-rate spikes) — use deliverability-qa; inside a launch window launch-day-conductor owns incident handling. 社媒危机预案/暂停队列/声明库/发言人矩阵

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"; produces a hypothesis, variant matrix, sample-size/duration/power plan, and a documented effect/uncertainty read from own exported results. It applies only a precommitted owner-approved action rule; the statistical helper never chooses a business action. Not for producing variants — use ad-creative-builder; not for reading back one shipped change — use paid-measurement-loop. 广告AB测试设计/实验设计/显著性判定/增效测试

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Partner, channel, and ecosystem marketing for B2B SaaS. Use this skill for co-marketing with technology alliances and channel partners, integration launches, joint campaigns and content, partner tiering and enablement, and cloud-marketplace go-to-market (AWS, Azure, GCP listings, private offers, committed-spend drawdown). Also triggers on: partner marketing, co-marketing, channel, reseller, alliance, ecosystem, integration launch, marketplace listing, AWS Marketplace, private offer, MDF, joint webinar, co-branded.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Professional code review with auto CHANGELOG generation, integrated with Codex AI. Use when you want professional code review before commits, you need automatic CHANGELOG generation, or reviewing large-scale refactoring.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate structured changelogs from git history. Use when user asks "what changed recently", "generate a changelog", "summarize commits" or user wants to understand recent development activity.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Stage files, run pre-commit, fix failures, loop until clean

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Ship current branch — CI, SonarCloud, code review, security review, fix all issues, merge. Assumes code is already committed and pushed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes - Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Trace BIRD routing-daemon behavior through the actual C source tree. Use for implementation questions, suspected upstream bugs, parser/keyword origins, filter instructions, protocol state machines, route attributes, birdc commands, stack traces, or BIRD 2 versus BIRD 3 source comparisons. Prefer a local checkout or exact upstream tag/commit and cite concrete files, functions, and revisions. Route config linting to bird-agent and active incidents to bird-troubleshooting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when keeping a Codex goal active across turns to research GitHub issues, PRs, and feature requests, handle each accepted change as a documented local commit, and publish only within the user's scope.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Public repo identity - use in README and published repos. For real identity details, use a local-only identity file that is not committed. Use when editing README*, CONTRIBUTING*.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a pull request from the current branch for pitwall, into the right base for this repo's two-tier flow — feature branches (`dev-<feature>`) target `dev`, and `dev` itself targets `master` as a release PR. Analyzes the new commits, drafts a PR title and a Summary/Test-plan body matching this repo's existing PR style, previews it for approval, then creates it via the `gh` CLI. A release PR into `master` additionally settles the version and writes the release notes file before the tag exists. Use whenever the user says "pr", "pull request", "open a pr", "create pr", "ship it", "merge into dev", "merge into master", "cut a release", "raise a pr", or anything about getting the current branch merged — even if they don't say the word "skill".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for Nauthilus validation, guardrails, dependency patch refreshes, vendoring, generated-output checks, `make release-guardrails`, govulncheck-sensitive publishing, structured commits, branch/tag choreography, website-doc side effects, and final clean-state reporting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Framework 저장소의 목적별 커밋 작성 시 한국어 제목과 변경 종류에 맞는 타입 적용.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Framework 저장소의 Draft PR 생성, 검증 결과와 체크리스트 갱신, merge commit 작성 시 공통 규칙 적용.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Senior Kotlin specialist code review — framework-agnostic. Use whenever the user asks to review, audit, critique, or get feedback on Kotlin code, a file, a class, a function, a module, a diff, a branch, a commit, or a pull request. Judges Kotlin language idioms, logic correctness, architecture and layering, concurrency (coroutines, Flow, structured concurrency, cancellation, race conditions), null safety, exception safety, testability, performance, and security. Detects force-unwraps, unchecked casts, GlobalScope, leaked mutability, broken structured concurrency, hidden side effects, weak abstractions, untestable seams, allocation hot spots, weak crypto, input-validation gaps, and PII logging. Outputs prioritized findings with file:line anchors and minimal-diff fixes. No assumptions about DI framework, UI framework, or build system.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up and optimize repositories for AI coding agents. Creates minimal AGENTS.md, CLAUDE.md symlink, docs/REQUIREMENTS.md, docs/BUSINESS-RULES.md, feedback loops, and deterministic enforcement (Claude Code hooks, OpenCode plugins). Use when user wants to make a repo AI-friendly, set up AGENTS.md/CLAUDE.md, document requirements/business rules for AI, add pre-commit hooks for AI workflows, or optimize codebase structure for coding agents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Autonomous build-ship-verify loop that ends with code committed, deployed, and confirmed live. Triggers on: "$ownership", "execute X with ownership", "build this overnight", or any request for an autonomous product loop with no human checkpoints until production is verified. NOT for: one-off tasks, quick fixes, or supervised dev work (use devprocess for those).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Structured build workflow: branch, delegate to coding agent, test, screenshot, and commit. Triggers on: "$devprocess", "build this properly", "use the coding agent workflow", or any feature/refactor/infrastructure change that is too large for a direct edit. NOT for: one-line fixes, doc edits, prompt tweaks, or simple config changes — do those directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Automate doc generation with JSDoc/TSDoc, linters, and pre-commit hooks. Use when setting up markdownlint, configuring doc linting pipelines, integrating JSDoc/TSDoc, or building automated documentation workflows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Git operations, shell scripting, CI/CD pipelines, and terminal automation. Use for conventional commits, PowerShell/Bash scripting, configuring GitHub Actions, or automating development tooling workflows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

End-to-end ABM program design and orchestration for B2B SaaS mid-market and enterprise motions. Use when building a target account list, designing account tiering criteria, planning ABM channel orchestration, coordinating BDR outreach with marketing campaigns, defining ABM measurement frameworks, or running an ABM program review. Also use when asked to "build an ABM program," "set up account-based marketing," "design a target account strategy," "plan ABM campaigns," or "measure ABM results." Designed for demand gen teams selling to Mid-Market companies with $10K-$50K+ ACV, multi-persona buying committees, and 3-6 month sales cycles.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.