1.4천건 · 관련도순
Combine specialized language models without retraining using mergekit. The skill explains how to choose merging methods, configure each model’s contribution, compare resulting variants, and prepare a merged model for evaluation and deployment.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Resolve an in-progress git merge or rebase conflict end to end: read the conflict state, recover each side's original intent, resolve every hunk, run the project's checks, and prepare the merge/rebase for an explicitly approved finish. Use when asked to "resolve merge conflicts", "fix this rebase", "finish the merge", or when `git status` shows conflicted (unmerged) paths. NOT for the full ship pipeline that merges the base branch first (see mk:ship); NOT for debugging a runtime bug or test failure unrelated to a conflict (see mk:investigate / mk:fix).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Handle merged cells before filling Excel templates with openpyxl, a Python library for spreadsheets. This skill shows how to inspect merged ranges, unmerge the required areas, write values, and save the workbook without merged-cell write errors.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
親イシュー配下のサブイシュー（孫以下の全子孫を含む）を依存順を保ちつつ worktree で並列に自動実装・push 前 review・PR 作成・CI 監視・マージ可能状態化まで一括自動化。 「イシューツリーを並列実装」「配下のサブイシューをまとめて実装」「ツリー全体を並列で実装して」「イシュー階層を自動開発」で使用。 per-issue 計画立案（Plan: セッション継承モデル）→実装（Implement: sonnet）の分業。push 前 review（Review 通過後にのみ push・PR 作成して CI を 1 回だけ起動）。 外部チェック構成は args の externalChecks で明示（{"app", "context"} の組で宣言。[] で「なし」を確定して不要待機なし・未指定なら自動マージ停止・slug のみの旧形式は自動マージ fail-closed）。 自動 squash merge は autoMerge: true + externalChecks 明示（全 App の信頼済み context 宣言込み）の opt-in で実行（merge-exec の自己取得再検証 + サーバー側 branch protection 実測が前提。既定 false はマージ可能状態で停止し人間がマージ。サーバー側 workflow サンプル（upstream の docs/implement-issue-tree/auto-merge-sample.yml 参照）+ branch protection への委譲も可）。並列度（parallel）と依存（dependsOn）で実行順を制御。 Phase 単位で厳密に直列化したい場合は phaseGate: true（opt-in。ルート直下の子〔Phase 親〕を sub-issues リスト順に直列化し、前 Phase の全子孫が merged/closed になるまで次 Phase 配下に着手しない。既定 false は現行の post-order 優先度のみ）。 着手できる件数・blocked になる件数を事前に知りたい場合は dryRun: true（何も書かずに見積りだけ返す）。 単一イシューの実装は implement-issue、PR レビューは implement-review-pr を参照。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide an existing Remotion pull request through automated checks and merge it when eligible. Resolve conflicts, investigate failed checks, fix genuine problems, and use the flake skill to rerun checks that fail intermittently.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Combine capabilities from multiple fine-tuned LLMs without retraining using mergekit. Choose a merging method, configure how models are blended, and evaluate the resulting model on tasks such as math, code generation, and conversation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Merge GitHub pull requests while preserving credit for the original contributors. Covers straightforward merges, conflict resolution, selective file inclusion, duplicate PR closure, and checks that confirm both attribution and working code after integration.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build Excel spreadsheets with merged titles and headers using openpyxl, a Python library for spreadsheet files. Follow a sequence for entering values, merging cells, and applying formatting, with guidance for updating existing merged ranges and checking saved results.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Reißverschluss-Verfahren (englisch: zipper merge) für sehr konfliktreiche Merges: Wenn zwei divergente Branches oder ein PR und sein Zielbranch BEIDE wertvolle, unvereinbar erscheinende Änderungen tragen, wird nicht pauschal eine Seite gewählt, sondern Abschnitt für Abschnitt verglichen, per Entscheidungstabelle (Nimm/Warum) die jeweils bessere Version übernommen, abschnittsweise committet und erst am Ende gepusht. Letzte Eskalationsstufe: Rebuild statt Merge — nur die Absicht/Funktionalität des Branches übernehmen und auf dem aktuellen Stand neu bauen. Nutzen bei: "Merge-Konflikt", "divergente Branches", "main vs. master", "konfliktreicher PR", "zipper merge", "Reißverschluss", "beide Seiten haben Recht", "PR ist zu alt zum Mergen".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Merge a Git source branch, including its still uncommitted changes, into a target branch through a regular merge, a rebase with fast-forward, or a squash merge, resolving merge conflicts semantically, check that the source branch landed, and emit a MERGED, CONFLICT, or FAILED verdict. Use when the user calls to "merge", "integrate", or "land" a branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing, reviewing, or troubleshooting Salesforce duplicate prevention, matching rules, duplicate rules, and merge governance. Covers cleaning up duplicates that already exist at ordinary volume: merge sequencing, survivorship, stewardship ownership. Also covers the deployable MatchingRule / DuplicateRule metadata, the Alert-vs-Block action pair, DuplicateRecordSet reporting, and the Apex DMLOptions.DuplicateRuleHeader.allowSave bypass. Triggers: 'duplicate rule', 'matching rule', 'merge strategy', 'dedupe', 'survivorship', 'D&B', 'same contact twice', 'clean up duplicate records', 'clean up duplicate accounts', 'DUPLICATES_DETECTED', 'allowSave', 'FindDuplicates'. NOT for cleanup at volume — hundreds of thousands of records, batch merge jobs, DemandTools/Cloudingo — use data/large-scale-deduplication. NOT for which field values and child records the platform keeps in a merge - use data/record-merge-implications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Carry out reviewed pull request plans, apply approved fixes, and preserve contributor credit. Validate the exact changes being merged, merge only explicitly authorized groups, and keep items on hold when required checks fail or remain unknown.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Take implementation work through small, independently mergeable pull requests. Use a separate working directory for each PR, record manual QA evidence, write English review descriptions, resolve CI and review findings, then merge and clean up.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Consolidate established lessons from domain memory files into reusable agent instructions. Review proposed additions before merging, preserve details while reducing duplication, and remove merged entries from the memory file afterward.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create fillable Word forms with text fields, date controls, dropdowns, and clickable checkboxes. Protect static document content while leaving designated fields editable, or prepare mail-merge placeholders for templates that receive data later.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize scattered concept notes into a map of recurring ideas. Merge duplicates, rank concepts into four tiers, trace how stronger ideas developed across sources, and assess which notes to keep, rewrite, merge, or remove.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide a pull request through conflict resolution, review feedback, and automated checks. The skill monitors progress, fixes failures, and completes a squash merge, combining the branch’s changes into one commit once checks and reviews are addressed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Decide whether a LoopX pull request is ready for approval or merge by checking review evidence for the current commit, required validation, and owner authorization. Record the decision and its supporting checks on the pull request.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide team Git work with consistent commit messages, branch naming, and review practices. Follow concrete steps for everyday development, urgent fixes, releases, merge conflicts, and version tags, including guidance on when to use merge or rebase.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Drive ONE already selected open pull request in microsoft/apm to mergeable. Classifies copilot-pull-request-reviewer[bot] inline review, runs autopilot-pr-review-worker, folds (by default) every recommendation inside the PR's stated scope, pushes to the head branch or a superseding PR that preserves authorship via commit trailers, watches CI to green (`agent-merge` when that skill or `<agent_merge_state>` is present; otherwise `gh pr checks --watch`), and iterates under fixed caps until ready-to-merge, advisory-with-deferred, superseded, or blocked. Plan before any fold, push, or reviewer request. Never spawned by autopilot-pr-review-scheduler. That scheduler is advisory only. Invoke this skill by name when the caller asked to drive a PR to merge.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Merge two pages that describe the same thing, preserving every distinct claim, redirecting inbound links, and recording the merge. Use this skill when the user approves a duplicate merge, says "these are the same page", "merge X into Y", or asks to clean up near-duplicates that a lint run proposed. Do NOT use to merge pages on your own judgement, to delete a page outright, or to split one page into several.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when a session's job is POST-MERGE VERIFICATION — taking merged PRs and establishing whether the change actually does what it claimed, then recording the result against its `pr_verifications` obligation. "validate the merged PRs", "work the verification backlog", "did that PR actually work", "run the post-merge E2E". It owns the obligation ledger the repo-pulse worker fills. Do NOT load it for building a change and opening its PR (that is `genesis-development`), or for driving open PRs to merge (that is `closing-session`).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write, open and — when allowed — merge a pull request for the current feature branch of a {{engine_name}} project, with or without a plan. Builds a plain-language PR text (one feature per line) from the plan's `## Modules` and task `WHY:` lines, or — without a plan — from the commits and the code changes themselves; pushes the current state (asking where to end when it stands inside a plan module), opens or updates the branch's single open PR through the GitHub MCP, and merges with a merge commit only when the merge brings nothing from the base branch. Levels: remind (text only), create, merge; capped by `git.pull_requests.max_level`. Trigger phrases: "pull request", "open a PR", "create PR", "PR description", "merge the PR". For commit messages use /unikit-commit; for reviewing a PR's code use /unikit-review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.