القائمة
Apply WorkCue branch naming, Korean commit message, push, and pull request rules for all work. Use inside this harness when the task requires this capability.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Plan, edit, and review scoped code changes in a dirty worktree without reverting user work. Use inside this harness when the task requires this capability.
Maintain date-based and domain-based WorkCue knowledge files in the Obsidian vault for every task, including decisions, failures, improvements, results, and reasons. Use inside this harness when the task requires this capability.
Select and run validation commands that match the risk and blast radius of a change. Use inside this harness when the task requires this capability.
Use the WorkCue product plan and local-first architecture constraints as required project context. Use inside this harness when the task requires this capability.
استنادا إلى تصنيف SOC المهني
| name | git-branch-pr-flow |
| description | Apply WorkCue branch naming, Korean commit message, push, and pull request rules for all work. Use inside this harness when the task requires this capability. |
Apply WorkCue branch naming, Korean commit message, push, and pull request rules for all work.
Format:
<type>/<short-kebab-summary>
Allowed types:
featurefixdocsharnesschorerefactortestcireleaseExamples:
harness/workcue-codex-rulesfeature/github-connectorfix/obsidian-task-parserdocs/scoring-contractFormat:
<prefix>: <한국어 제목>
<한국어 설명>
Allowed prefixes:
featfixdocsrefactortestchoreharnesscibuildreleaseStyle:
다, 습니다, 했다, 하였다.추가, 수정, 개선, 정리, 보강, 분리, 검증.Good:
harness: WorkCue 개발 하네스 규칙 추가
- Obsidian 기록 경로와 daily/domain 로그 규칙 정리
- 한국어 커밋과 PR 생성 규칙 보강
Bad:
docs: WorkCue 하네스를 추가했다
PR title follows the commit title style.
PR body must include:
## TL;DR
## 맥락
## 변경사항
## 검증
## 남은 위험
TL;DR, 맥락, 변경사항 are mandatory. 검증 and 남은 위험 are strongly expected.