1.4천건 · 관련도순
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform a full InDesign data merge from a CSV/TSV and an .indd template (or a PDF that gets converted to .indd automatically). Use this skill whenever the user wants to merge a data file with a layout template — including visiting cards, certificates, badges, catalogs, mailers, labels, invoices, or any per-row personalisation. Triggers on: "data merge", "InDesign merge", "merge my CSV with InDesign", "batch export PDF from template", "variable data InDesign", "personalise each row", or any request combining an .indd / PDF template with a data file. Use this skill even when only two of the three inputs (template, data, images) are mentioned — and even when the user never uses the phrase "data merge".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
팀에 맞는 Git 브랜치 전략을 선택하고 커밋과 풀 리퀘스트 작성 방식을 정리합니다. 이력 정리, 충돌 해결, 버전 태그와 릴리스 관리 절차도 다룹니다.
두 에이전트가 각각 수정한 브랜치의 Git 충돌을 양쪽 변경 내용과 의도에 따라 중립적으로 해결합니다. 충돌별 판단 이유를 기록하고 빌드나 테스트로 통합 결과를 확인합니다.
Manage GitHub pull requests from creation through review and merge. Using GitHub CLI, the skill prepares descriptions, coordinates reviewers, tracks automated checks, helps resolve conflicts, and selects merge approaches suited to the branch history.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Scan recent merges to main for unfinished tasks, deprecated APIs, broken documentation links, and obsolete feature flags. Get a concise report with file locations, risk, effort, and suggested follow-up actions for each merge.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Assess a fixed code patch for behavior changes, regression risks, test coverage, and recovery options. Receive an evidence-based report and structured assessment indicating whether it is ready to merge and qualifies as an automatic merge candidate.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Resolve merge conflicts in generated workflow lock files by rebuilding them from merged Markdown sources. The skill checks for leftover conflict markers, stages regenerated files, and verifies that unresolved paths and whitespace errors are cleared.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Land the winning experiment from an evo run as a clean, mergeable change -- open a PR when the repo has a remote, otherwise merge into the working branch. Distills the best-scoring experiment down to the minimal diff that reproduces its behaviour, shaped for the qualities a maintainer merges on (scope discipline, test integrity, style adherence), then attaches an advisory mergeability report. Use when the user invokes /evo:ship, asks to land/merge/ship the best result, or wants to turn a finished optimization into a pull request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix ClickHouse query errors when querying AggregatingMergeTree tables that use state functions. Use when: (1) Query fails with type mismatch on AggregateFunction columns, (2) Using sum/count on columns created with sumState/countState/uniqState, (3) Creating views that JOIN with materialized views using AggregatingMergeTree, (4) Getting unexpected results from aggregate columns that show as AggregateFunction(sum, ...) type. The *State() functions store intermediate aggregate states, not final values - you must use *Merge() functions to finalize them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Git is deceptively simple to learn and incredibly hard to master. The difference between a team that ships and a team that fights merge conflicts all day comes down to workflow discipline. Your git history is documentation - make it tell a story future you can understand. This skill covers branching strategies (trunk-based, gitflow, GitHub flow), commit hygiene, merge vs rebase, conflict resolution, and the commands you actually need. Key insight: most git disasters come from not understanding what you're about to do. 2025 lesson: Trunk-based development with short-lived branches has won. Long-lived feature branches are a code smell. If a branch lives more than a few days, something is wrong with your architecture or process. Use when "git workflow, branching strategy, git merge, git rebase, merge conflict, git commit, trunk-based, gitflow, git history, git revert, git reset, git, version-control, workflow, branching, commits, merge, rebase, collaboration" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when a session's job is to DRIVE OPEN PRs TO MERGE rather than to write new code — "close out the open PRs", "review and fix the open PRs", "what's blocking our PRs", "which PRs are mergeable". It owns the In Review column: it reads each PR's gate status, verifies and fixes review findings on PRs OTHER sessions built, replies in-thread, and stops at the merge gate for the user's per-PR approval. Do NOT load it for building a feature and opening its PR — that is a build session (`genesis-development`).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Emergency fund analyzer. Calculates the right emergency fund size based on job stability, family structure, fixed expenses, dependents, and employee vs. business-owner status. Recommends where to keep it (HYSA, money market, T-bills, I-Bonds), how fast to build it, what counts as a true emergency, and how to replenish after use. Produces FINANCE-EMERGENCY.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safely merge GitHub pull requests using comprehensive pre-merge validation. Use this skill when the user asks to merge a PR, complete a PR workflow, or check if a PR is ready to merge. Validates CI/CD status, reviews, and conflicts before merging with the appropriate strategy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fetch the latest upstream branch and merge it into the current branch, in the pitwall repo — feature branches (`dev-<feature>`) sync from `dev`, and `dev` itself syncs from `master`. Stages the merge, walks through any conflicts interactively, then creates the merge commit directly (signed when the user signs commits). Use whenever the user says "sync", "pull dev", "pull master", "update branch", "merge dev", "merge master", "get latest", or anything about bringing upstream changes into their working branch — even if they don't say the word "skill".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for pull-request, merge, version and release mechanics in the Syntropic137 repo, and for CI or release-pipeline failures. Trigger phrases include "open a PR", "submit my changes", "address the review comments", "Copilot left comments", "merge this PR", "push this nit straight to main", "CI is red", "the release gate failed", "smoke test broke", "why is this PR BLOCKED", "bump the version", "cut a release", "release v1.x", "write the release notes", "main -> release PR", "approve the release gate", "the release published a bad asset", "triage the open PRs", "PR backlog", "which PRs are ready to merge", "merge order", "DORA metrics", "deploy frequency", "lead time", "change failure rate", "time to restore", "why didn't the issue auto-close". Covers trunk-based `main`, the `release` branch, local gates (`just qa-ci`, `just preflight`), GitHub Actions gates, review and merge policy, and post-release verification. Do NOT use for deciding what to dispatch, running the orchestrator loop, or deciding when to deploy a beta or run a pit stop (see `orchestrating`); for whether a task belongs in a workspace or locally (see `dogfooding`); for using the `syn` CLI as an end user (see the syntropic137 plugin skills).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
stacked PRの下位PRがマージされた後に上位branchをrestack（rebase/cherry-pick再構成）する際に使用。「restackして」「上位PRを更新して」「restack after merge」「PRのbaseを更新」「スタックを整理」という依頼でトリガーする。対象sliceの特定→rebase→変更ファイル確認と代表テスト実行→force-with-leaseでpush→PR base更新→auto-merge判定の順で進める。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clean up the local workspace after a dev branch has been merged into main. Verifies the current dev branch is fully merged into origin/main, then switches to main, pulls the latest, deletes the local dev branch, and deletes the remote dev branch if it still exists. STOPS and warns the user if the current branch is not yet merged. Triggers: cleanup workspace, cleanup branch, delete merged branch, finish dev branch, post-merge cleanup
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
대규모 기능의 설계 제안을 의존 관계와 통과 기준이 있는 작업으로 나눕니다. 여러 에이전트의 조사, 구현, 테스트, 검토부터 통합과 최종 검증까지 정리합니다.
Prepare a selected batch of pull requests, or proposed code changes, by reviewing overlaps, diagnosing conflicts, and preserving contributor credit. Check the exact version and required authorization before each merge, then report completed work and remaining holds.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Model how an acquisition changes the buyer’s earnings per share. Compare purchase prices, cash and stock payment mixes, and synergy assumptions, then produce an Excel workbook and a one-page summary of the deal’s financial effects.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Update a working Git branch with the latest origin/main through a merge. The skill checks branch state, resolves conflicting edits with attention to both changes’ intent, runs project checks, and summarizes the resolution.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.