Git Workflow

Commit Message Format

1<type>: <description>
2
3<optional body>
4
5<optional trailers>

Types: feat, fix, refactor, docs, test, chore, perf, ci

Note: Attribution disabled globally via ~/.claude/settings.json.

Git Trailers (prototypes/ 작업 전용)

prototypes/ 디렉토리의 코드 변경 커밋에만 git trailer를 추가한다. 문서 작업(knowledges/, general-docs/ 등)에는 사용하지 않는다.

1feat: add login page with email auth
2
3Implement email/password login with Zod validation.
4
5Constraint: Design System 토큰만 사용 (globals.css 정의)
6Rejected: shadcn/ui 기본 색상 팔레트 직접 사용
7Scope-risk: auth 모듈 신규, 기존 영향 없음
8Confidence: high

사용 가능한 trailer:

  • Constraint: 적용된 제약 조건
  • Rejected: 거부한 대안과 이유
  • Scope-risk: 변경 영향 범위 (low/medium/high)
  • Confidence: 구현 신뢰도 (high/medium/low)
  • Not-tested: 미검증 항목 (있을 경우만)

모든 trailer가 필수는 아니다. 의사결정 맥락이 중요한 커밋에만 해당 trailer를 선택적으로 사용한다.

Pull Request Workflow

When creating PRs:

  1. Analyze full commit history (not just latest commit)
  2. Use git diff [base-branch]...HEAD to see all changes
  3. Draft comprehensive PR summary
  4. Include test plan with TODOs
  5. Push with -u flag if new branch

Feature Implementation Workflow

  1. Plan First

    • Use planner agent to create implementation plan
    • Identify dependencies and risks
    • Break down into phases

  2. TDD Approach

    • Use tdd-guide agent
    • Write tests first (RED)
    • Implement to pass tests (GREEN)
    • Refactor (IMPROVE)
    • Verify 80%+ coverage

  3. Code Review

    • Use code-reviewer agent immediately after writing code
    • Address CRITICAL and HIGH issues
    • Fix MEDIUM issues when possible

  4. Commit & Push

    • Detailed commit messages
    • Follow conventional commits format