1.5천건 · 관련도순
AC branch pi-model power flow equations (P/Q and |S|) with transformer tap ratio and phase shift, matching `acopf-math-model.md` and MATPOWER branch fields. Use when computing branch flows in either direction, aggregating bus injections for nodal balance, checking MVA (rateA) limits, computing branch loading %, or debugging sign/units issues in AC power flow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when user asks to "clean gone branches", "remove deleted local branches", "prune branches removed from remote", or explicitly invokes "clean-gone-branches".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigates and creates Git branches. Triggered when: branch status check, new branch creation, branch-related errors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Delete the `-bak` backup branches that `/prepare-merge` leaves behind, local and on origin, once the work they back up has merged. Use when the user says "remove my bak branches", "clean up bak branches", "delete the backups", or "/clean-bak-branches".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rebases every local branch of a fork onto a moved upstream, flags the ones upstream has superseded, and rebuilds the mixdown branch that combines them. Use after fetching a fork's upstream and finding it has advanced far, been force-pushed, or rewritten its history; when several stacked or sibling branches all need bringing forward at once; when a branch was cut from a mixdown and now carries merge commits it should not have; or when asked to rebase all branches, re-mix, or bring a whole worktree set up to date.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify that the current Git branch, upstream state, and dirty working tree match the user's intended task before staging, committing, pushing, or continuing work from another session. Use this to detect stale branch reuse, leftover dirty files from previous sessions, unrelated commits on the current branch, cases where work should be split into a new branch or worktree, and post-publish cleanup decisions after push, PR creation, or PR merge.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Intelligent Git Flow branch creator that analyzes git status/diff and creates appropriate branches following the nvie Git Flow branching model. Use when starting a feature, release, or hotfix branch in a repository that follows Git Flow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run Tamanu pre-release verification checks: verify that hotfixes on the current release branch are merged forward to main, and that hotfixes from prior release branches are included in the current release. Use when the user wants to run "pre-release checks", verify hotfix integrity before cutting or shipping a Tamanu release, confirm a release/X.YY branch is safe to release, or check that no hotfix has been orphaned (left on neither main nor the current release). Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for deciding which tests to run (see scope-tamanu-release-tests).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cascade merge changes through a chain of dependent branches. Use when updating stacked/chained PRs, propagating changes from a parent branch to all downstream branches, or when the user mentions "cascade merge", "propagate changes", "update dependent branches", or "merge to downstream branches".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a feature branch from an Azure DevOps ticket. Fetches ticket title, slugifies, creates `feature/<id>-<slug>`, and optionally transitions ticket to Active. Trigger when user says "feature branch", "create branch", "/dev-azdo:feature-branch", or provides a ticket id/URL to start work on.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
여러 AI 에이전트에 담당 범위와 완료 조건을 배정하고 병렬 작업을 관리합니다. 칸반으로 진행 상황과 장애 요인을 공유하며 테스트와 검토를 거쳐 결과를 통합합니다.
팀에 맞는 Git 브랜치 전략을 선택하고 커밋과 풀 리퀘스트 작성 방식을 정리합니다. 이력 정리, 충돌 해결, 버전 태그와 릴리스 관리 절차도 다룹니다.
이전에 저장한 작업 상태를 읽어 중단한 지점부터 이어갈 수 있도록 맥락을 복원합니다. 현재 브랜치를 우선하며 다른 브랜치와 Conductor 작업 공간 인계도 지원합니다.
Ant Design 브랜치 전체의 변경을 읽고 공식 템플릿에 맞춰 PR의 영어 제목, 본문, 대상 브랜치를 정리한 뒤 사용자 확인 후 생성합니다.
Storybook의 특정 브랜치에 해당하는 시험용 패키지를 찾고 필요하면 게시합니다. 게시 상태를 확인하고 설치나 업데이트에 쓸 명령을 안내합니다.
Manage Git branches, resolve conflicts, and coordinate pull requests, which propose code changes. Check change risks and automated test status before merging, and inspect metrics such as merge frequency and review time.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Bring one approved community pull request into a release branch while preserving authorship and contribution credit. Review the changes, check for conflicts, run focused tests, and post a specific thank-you to the contributor.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare batches of merged SGLang pull requests for a release branch. It checks conflicts and previous attempts, starts the cherry-pick workflow, monitors completion, and reports created pull requests or failure reasons.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review all changes in a pull request or branch against its base branch. Use a knowledge graph, a map of code relationships, to report affected files and functions, test coverage, API compatibility issues, and recommended actions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.