'commit' 검색 결과

Generates account research briefs, personalized outreach sequences, persona-specific talk tracks, and objection handling frameworks for B2B SaaS BDR teams. Use when preparing BDR outreach for target accounts, building prospecting sequences, creating call scripts, developing objection responses, onboarding new BDRs, or reviewing outreach performance. Also use when asked to "write outreach emails," "build a prospecting sequence," "create a call script," "handle objections," or "research an account for outreach." Designed for BDR teams selling compliance, security, and GRC platforms to mid-market and enterprise buyers with multi-persona buying committees.

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

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.

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

Release tdmcp: write the Keep-a-Changelog entry, bump the SemVer version across every manifest, then (autonomously, per project policy) commit, tag, and push — gated on a td-qa PASS, with hard git safety rails. Use when releasing/shipping/cutting a tdmcp version, writing the CHANGELOG, bumping the version, or tagging a release.

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

Fix red CI or set up GitHub Actions end to end: read the failing run, find the root cause, patch and validate the workflow, push only after GO, and watch the run go green on the pushed commit. Use for "CI is red", "the build fails on GitHub", "set up CI for this repo", "fix the workflow".

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

Release a new AOS version to npm through the release-please PR: check the commit subjects, review and gate the release PR, merge it only after GO, watch the release workflow and check version drift. Use for "release AOS", "cut an AOS release", "merge the release PR", "publish a new AOS version".

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

Behavioral UX specialist applying choice architecture, friction audits, and commitment design to guide users toward intended actions without coercion. Use when optimizing conversion flows, onboarding, or checkout UX.

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

A relentless interview to sharpen a plan or design before committing to an approach. Use on any "grill me" or "grill this plan" trigger phrase, when the user asks to stress-test a decision, plan or design, and before handing a finished plan off to a startcycle run or a plan-canvas review.

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

Generate a concise and structured PR description from commit history with minimal token usage

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

変更をステージング・コミットする。「コミット」「コミットして」「変更をコミット」「gitignore チェック」「コミット前チェック」「機密ファイル確認」などで起動。

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

Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation. Optimized to avoid AI detection patterns. Use when writing any content beyond code.

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

Critical Git safety rules to prevent destructive operations. Use whenever performing git operations, reverting changes, or managing commits. Prevents accidental loss of work.

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

Use when: analysing a project's delivery health — CI/CD, commit patterns, and working tree state.

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

GitHub PR lifecycle: branch, commit, open, CI, merge.

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

Pre-commit review: security scan, quality gates, auto-fix.

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

MCP Agent Mail - Mail-like coordination layer for multi-agent workflows. Identities, inbox/outbox, file reservations, contact policies, threaded messaging, pre-commit guard, Human Overseer, static exports, disaster recovery. Git+SQLite backed. Python/FastMCP.

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

Handle pull requests and review comments using GitHub CLI (gh). Use when the user wants to check PR comments, address review feedback, reply with commit hashes, or work with pull requests.

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

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

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

Add GitHub permalinks with fixed SHA/commit references to research documentation containing code snippets. Use when writing technical docs with code examples, creating investigation/research docs that reference source files, user asks to "add permalinks" or "add GitHub links", documenting code research findings with file:line references, or creating audit trails needing permanent code references. Triggers on "add github links", "add permalinks", "link to source", "make code references permanent".

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

Vendor (copy-import) a single external Claude Code skill into your own skills repo correctly — with license compliance and full provenance/attribution. Deterministic, idempotent primitive: given an upstream ref (owner/repo/path@sha or a GitHub URL) it fetches the skill, detects and gates on the license, copies the folder, injects a provenance frontmatter block (license + metadata: author/source/upstream_commit/vendored_at/provenance), ships the upstream LICENSE, adds a ## Credits section, and records a CREDITS.md ledger entry. Use when the user asks to "vendor a skill", "import a skill", "clone a skill", "borrow someone's skill", "add an external skill with attribution/credit", or スキルを取り込む / vendoring / 他人のスキルを自分のリポに取り込む. This is the import primitive that a skill-scout/curator orchestrator calls; it does NOT discover or evaluate — it correctly imports ONE skill you already chose.

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

「学内委員会・教授会の議事録作成を AI で効率化したい」「録音から要点抽出のプロセスを標準化したい」 「機密性の高い会議で AI を使っていいか判断したい」「人事案件を含む教授会で AI 議事録ツールを 使って大丈夫か確認したい」「Enterprise 版がない自学で使える経路を知りたい」場面で使う、 議事録 AI 化の判断と運用のスキル。 `skills/confidential-info-guidelines/` の 3 段分類と連携し、会議機密性 × 出席者同意 × 匿名化の 3 軸判断でツール選定と運用手順を示す。

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

変更内容を確認し、論理的な単位で複数のコミットに分けて実行します

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

Improve, rewrite, and explain workplace English for an English-as-a-second-language professional in Australia. Use when the user asks to polish, fix, rewrite, improve, or check work emails, Slack or Teams messages, follow-ups, replies to managers or stakeholders, technical explanations, status updates, polite chasing messages, questions, pushback, issue explanations, or similar workplace communication for Australian companies. Ask targeted clarifying questions before rewriting when the intended meaning, recipient, action, deadline, blame, commitment, or technical conclusion is unclear.

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