Skip to main content

pr-creation

**EXECUTION (runbook) SKILL** — Prepare a Git Extensions change for a pull request so it passes CI. USE FOR: "create a PR", "get this ready to push", pre-commit/pre-push checklist, writing a conventional-commit message. DO NOT USE FOR: designing the change itself or explaining code. Triggers: "prepare a PR", "ready to commit", "pre-PR checklist", "write the commit message".

소스 정보

저장소
gitextensions/gitextensions
최근 소스 활동
2026년 8월 5일 14:11
감지된 SKILL.md 언어
영어
스타
8,615
포크
2,226

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
pr-creation
description
**EXECUTION (runbook) SKILL** — Prepare a Git Extensions change for a pull request so it passes CI. USE FOR: "create a PR", "get this ready to push", pre-commit/pre-push checklist, writing a conventional-commit message. DO NOT USE FOR: designing the change itself or explaining code. Triggers: "prepare a PR", "ready to commit", "pre-PR checklist", "write the commit message".
# PR Creation (runbook) A deterministic checklist to make a change merge-ready. Do the steps in order; STOP on any failure. ## Prechecks 1. Confirm you're on a feature branch (not `master`) with a descriptive name. 2. Confirm the working tree contains only intended changes (`git status`). ## Build & test (gates) 3. **Build clean:** `dotnet build /v:q` — no errors, no new analyzer/StyleCop warnings. 4. **Run the associated tests locally — MANDATORY before any push.** Identify the tests covering your change and run them (`dotnet test <project> --filter "FullyQualifiedName~<Type>"`), then run the affected project(s) in full. All green. **NEVER** push untested changes and let CI be the first run — it wastes CI compute and slows feedback. If some path can't be exercised locally (e.g. an arch-specific case), state explicitly what was and wasn't verified. See [testing-guide](../../copilot-docs/L2-core-platform/testing-guide.md). ## Localization gate (MUST if UI changed) 5. If you added/changed any form, control, menu/toolbar item, or `TranslationString`: run `.\update-loc.cmd` from the repo root and stage the regenerated [English.xlf](../../../src/app/GitUI/Translation/English.xlf). **CI fails if it's stale.** See [translation-system](../../copilot-docs/L2-core-platform/translation-system.md). ## Commit 6. Use **Conventional Commits** (e.g. `feat:`, `fix:`, `docs:`, `perf:`, `refactor:`). 7. If any file under `src/app/GitExtensions.Extensibility/` changed, **note the plugin interface version impact** in the commit message. 8. Create a **new** commit (do not amend published commits). ## Postchecks (STOP conditions) - **NEVER** leave `fixup!` / `squash!` commits on the branch — the `git` workflow blocks merge. Autosquash locally. - Ensure the CLA is signed (the `cla-check` workflow gates it). - Files MUST be CRLF and satisfy `.editorconfig`/StyleCop. - Do **not** use `--no-verify` or disable CI checks to force a pass — fix the cause. ## Do NOT push unless explicitly asked Prepare the commit(s); only run `git push` when the user explicitly requests it.
GitHub에서 보기