codingbuddy-rules 3.1.1 → 3.1.2

package/.ai-rules/agents/technical-planner.json

@@ -1,12 +1,6 @@
 {
   "name": "Technical Planner",
   "description": "Low-level implementation planning with TDD and bite-sized tasks",
-
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Balanced for detailed planning and code generation"
-  },
-
   "role": {
     "title": "Technical Planner",
     "type": "primary",
@@ -25,12 +19,10 @@
       "Ensure plans are context-complete for engineers"
     ]
   },
-
   "context_files": [
     ".ai-rules/rules/core.md",
     ".ai-rules/rules/augmented-coding.md"
   ],
-
   "skills": {
     "required": [
       {
@@ -57,7 +49,6 @@
       }
     ]
   },
-
   "activation": {
     "trigger": "When detailed implementation planning with TDD is needed",
     "explicit_patterns": [
@@ -113,7 +104,6 @@
       "language": "All responses in Korean"
     }
   },
-
   "workflow": {
     "planning_task": {
       "approach": "TDD-First Planning",
@@ -129,7 +119,6 @@
       ]
     }
   },
-
   "plan_format": {
     "header": {
       "required": [
@@ -154,7 +143,6 @@
       ]
     }
   },
-
   "modes": {
     "planning": {
       "description": "Creating detailed implementation plans",
@@ -183,7 +171,6 @@
       ]
     }
   },
-
   "execution_options": {
     "subagent_driven": {
       "description": "Execute in current session with fresh subagent per task",
@@ -196,7 +183,6 @@
       "benefits": ["Parallel work possible", "Clear handoff points"]
     }
   },
-
   "communication": {
     "style": "Detailed and actionable plans, TDD-focused",
     "approach": [
@@ -206,7 +192,6 @@
       "Offer clear execution choice at end"
     ]
   },
-
   "reference": {
     "project_rules": ".ai-rules/rules/",
     "existing_agents": ".ai-rules/agents/*.json",

package/.ai-rules/agents/test-strategy-specialist.json

@@ -1,10 +1,6 @@
 {
   "name": "Test Strategy Specialist",
   "description": "Test strategy expert for Planning, Implementation, and Evaluation modes - unified specialist for TDD vs Test-After decisions, test coverage planning, and test quality assessment",
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Suitable model for test strategy planning"
-  },
   "role": {
     "title": "Test Strategy Engineer",
     "expertise": [

package/.ai-rules/agents/tooling-engineer.json

@@ -1,11 +1,6 @@
 {
   "name": "Tooling Engineer",
   "description": "Project configuration, build tools, and development environment specialist",
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Balanced for configuration tasks and tooling setup"
-  },
-
   "role": {
     "title": "Tooling Engineer",
     "type": "primary",
@@ -28,9 +23,7 @@
       "Integrate MCP tools with development workflow"
     ]
   },
-
   "context_files": [".ai-rules/rules/core.md", ".ai-rules/rules/project.md"],
-
   "activation": {
     "trigger": "When user works with config files, build tools, or development environment setup",
     "explicit_patterns": [
@@ -82,7 +75,6 @@
       "language": "All response text in Korean"
     }
   },
-
   "workflow": {
     "config_modification": {
       "approach": "Incremental change with validation",
@@ -134,7 +126,6 @@
       ]
     }
   },
-
   "config_patterns": {
     "typescript": {
       "tsconfig.json": "TypeScript compiler configuration",
@@ -157,7 +148,6 @@
       "engines": "Node.js version requirements"
     }
   },
-
   "best_practices": {
     "general": [
       "Use specific versions or version ranges (^, ~) appropriately",
@@ -185,7 +175,6 @@
       "Consider bundle size implications"
     ]
   },
-
   "code_quality_checklist": [
     "Configuration is valid and parseable",
     "All settings are documented or self-explanatory",
@@ -194,7 +183,6 @@
     "Lint and typecheck pass",
     "Development workflow still works correctly"
   ],
-
   "communication": {
     "language": "ko",
     "style": "Technical and precise, focusing on configuration details",
@@ -205,7 +193,6 @@
       "Verify changes work before completing"
     ]
   },
-
   "reference": {
     "project_rules": ".ai-rules/rules/",
     "config_schema_reference": "See project's package.json and existing configs",

package/.ai-rules/agents/ui-ux-designer.json

@@ -1,11 +1,6 @@
 {
   "name": "UI/UX Designer",
   "description": "UI/UX design specialist based on universal design principles and UX best practices - focuses on aesthetics, usability, and user experience rather than specific design system implementations",
-  "model": {
-    "preferred": "claude-sonnet-4-20250514",
-    "reason": "Suitable model for UI/UX design analysis"
-  },
-
   "role": {
     "title": "UI/UX Design Specialist",
     "expertise": [
@@ -25,9 +20,7 @@
       "Collaborate with Accessibility Specialist for inclusive design"
     ]
   },
-
   "context_files": [".ai-rules/rules/core.md", ".ai-rules/rules/project.md"],
-
   "modes": {
     "planning": {
       "activation": {
@@ -217,7 +210,6 @@
         }
       }
     },
-
     "implementation": {
       "activation": {
         "trigger": "When implementing UI components, user interfaces, or interaction patterns",
@@ -336,7 +328,6 @@
         }
       }
     },
-
     "evaluation": {
       "activation": {
         "trigger": "When evaluating UI/UX quality, design review is needed, or Code Reviewer identifies design concerns",
@@ -439,7 +430,6 @@
       }
     }
   },
-
   "shared_framework": {
     "design_principles_reference": {
       "visual_hierarchy": "Size, Color, Contrast, Spacing, Position to guide attention",
@@ -491,7 +481,6 @@
       "common_patterns": ["mobile-first", "desktop-first", "content-based"]
     }
   },
-
   "communication": {
     "approach": [
       "Start by understanding user goals and context",
@@ -502,7 +491,6 @@
       "Collaborate with other specialists (Accessibility, Frontend)"
     ]
   },
-
   "reference": {
     "design_theory": {
       "visual_design": "CRAP principles (Robin Williams), Gestalt principles",

package/.ai-rules/keyword-modes.json

@@ -8,7 +8,11 @@
       "delegates_to": "frontend-developer",
       "defaultSpecialists": [
         "architecture-specialist",
-        "test-strategy-specialist"
+        "test-strategy-specialist",
+        "event-architecture-specialist",
+        "integration-specialist",
+        "observability-specialist",
+        "migration-specialist"
       ]
     },
     "ACT": {
@@ -23,7 +27,9 @@
       "delegates_to": "frontend-developer",
       "defaultSpecialists": [
         "code-quality-specialist",
-        "test-strategy-specialist"
+        "test-strategy-specialist",
+        "event-architecture-specialist",
+        "integration-specialist"
       ]
     },
     "EVAL": {
@@ -36,7 +42,11 @@
         "security-specialist",
         "accessibility-specialist",
         "performance-specialist",
-        "code-quality-specialist"
+        "code-quality-specialist",
+        "event-architecture-specialist",
+        "integration-specialist",
+        "observability-specialist",
+        "migration-specialist"
       ]
     },
     "AUTO": {
@@ -52,8 +62,12 @@
       "defaultSpecialists": [
         "architecture-specialist",
         "test-strategy-specialist",
+        "security-specialist",
         "code-quality-specialist",
-        "security-specialist"
+        "event-architecture-specialist",
+        "integration-specialist",
+        "observability-specialist",
+        "migration-specialist"
       ]
     }
   },

package/.ai-rules/skills/README.md

@@ -14,6 +14,7 @@ Reusable workflows for consistent development practices.
 | executing-plans | Execute implementation plans with review checkpoints | Following written plans |
 | frontend-design | Create distinctive, production-grade frontend interfaces | Building web components/pages |
 | incident-response | Systematic organizational response to production incidents | Production incidents, alerts, service degradation |
+| pr-all-in-one | Unified commit and PR workflow with smart issue linking | `/pr-all-in-one [target] [issue]` |
 | pr-review | Systematic, evidence-based PR review with anti-sycophancy principles | Conducting manual PR reviews |
 | refactoring | Structured, test-driven refactoring workflow with Tidy First principles | Improving code structure without changing behavior |
 | subagent-driven-development | Execute plans with independent tasks in current session | In-session plan execution |
@@ -131,6 +132,11 @@ EOF
 ├── performance-optimization/
 │   ├── SKILL.md
 │   └── documentation-template.md
+├── pr-all-in-one/
+│   ├── SKILL.md
+│   ├── configuration-guide.md
+│   ├── issue-patterns.md
+│   └── pr-templates.md
 ├── pr-review/
 │   └── SKILL.md
 ├── refactoring/

package/.ai-rules/skills/pr-all-in-one/SKILL.md

@@ -0,0 +1,364 @@
+---
+name: pr-all-in-one
+description: Unified commit and PR workflow. Auto-commits changes, creates/updates PRs with smart issue linking and multi-language support.
+---
+
+# PR All-in-One
+
+## Overview
+
+Streamlines commit-to-PR workflow with auto-commit, smart issue linking, and multi-language support. Handles the complete flow from uncommitted changes to published PR with intelligent branch management, logical commit grouping, and context-aware PR descriptions.
+
+## When to Use
+
+- Any situation requiring PR creation
+- When uncommitted changes exist
+- When an existing PR needs updating
+- When you want to handle branch creation and PR in one step
+- When you want to auto-link Issue IDs to the PR
+
+## Usage
+
+```
+/pr-all-in-one [target-branch] [issue-id]
+```
+
+**Examples:**
+- `/pr-all-in-one` - PR to default branch, issue ID from branch name
+- `/pr-all-in-one develop` - PR to develop, issue ID from branch name
+- `/pr-all-in-one main ISSUE-12345` - PR to main with issue ID
+- `/pr-all-in-one ISSUE-12345` - PR to default branch with issue ID
+
+**Argument Parsing:**
+- `target-branch`: Branch name (main, develop, master, etc.)
+- `issue-id`: Matches configured issue pattern (JIRA-123, #456, ENG-789, etc.)
+- Arguments can be in any order
+- If only one argument provided, checks if it's an issue pattern first
+
+## Configuration
+
+**Location:** `.claude/pr-config.json`
+
+First-time run: Interactive setup flow guides you through configuration.
+
+See `configuration-guide.md` for:
+- All configuration options
+- Setup wizard walkthrough
+- Example configurations
+
+## Workflow (9 Steps)
+
+```
+┌─────────────────────────────────────────────────┐
+│              Workflow Execution                 │
+└─────────────────────────────────────────────────┘
+
+Step 1: Parse arguments
+├── Issue pattern → issue ID
+├── Branch name → target branch
+└── Defaults from config
+
+Step 2: Check git status & branch
+├── git status (uncommitted changes)
+└── git branch --show-current
+
+Step 3: Handle main branch case
+├── If on target branch with changes
+│   ├── Analyze changes for branch name
+│   ├── Create new branch: git checkout -b <type>/<description>
+│   └── Proceed to Step 4
+└── If on target branch without changes → Exit
+
+Step 4: Auto-commit changes
+├── Analyze with git diff
+├── Group by feature/purpose
+└── For each group:
+    ├── git add <related-files>
+    ├── Conventional commit message (English)
+    └── NO AI signature/Co-Authored-By
+
+Step 5: Push to remote
+└── git push -u origin <branch> (if needed)
+
+Step 6: Check existing PR
+└── gh pr view --json url,title,body
+
+Step 7: Update existing PR (if exists)
+├── Analyze all commits: git log <target>..HEAD
+├── Read prLanguage from .claude/pr-config.json
+├── Select template based on prLanguage:
+│   ├── "en" → English Template
+│   ├── "ko" → Korean Template
+│   └── "bilingual" → Bilingual Template
+├── Generate title:
+│   ├── "en"/"bilingual" → English title
+│   └── "ko" → 한국어 title
+├── Generate body with selected template
+├── Merge with .github/pull_request_template.md (if exists)
+├── NO AI signature
+└── gh pr edit --title --body
+
+Step 8: Create new PR (if not exists)
+├── Analyze all commits
+├── Read prLanguage from .claude/pr-config.json
+├── Select template based on prLanguage:
+│   ├── "en" → English Template
+│   ├── "ko" → Korean Template
+│   └── "bilingual" → Bilingual Template
+├── Generate title:
+│   ├── "en"/"bilingual" → English (e.g., "feat: add auth")
+│   └── "ko" → 한국어 (e.g., "feat: 인증 추가")
+├── Generate body with selected template + commit analysis
+├── Merge with project template if exists
+├── NO AI signature
+└── gh pr create --draft --base <target>
+
+Step 9: Return PR URL
+└── If UI changes detected → suggest screenshots
+```
+
+### Workflow Diagram
+
+```
+                    ┌─────────────────┐
+                    │  Check Config   │
+                    │ pr-config.json  │
+                    └────────┬────────┘
+                             │
+              ┌──────────────┴──────────────┐
+              │                             │
+              ▼                             ▼
+     ┌────────────────┐           ┌─────────────────┐
+     │  Config Exists │           │  No Config      │
+     └───────┬────────┘           └────────┬────────┘
+             │                             │
+             │                             ▼
+             │                    ┌─────────────────┐
+             │                    │ Interactive     │
+             │                    │ Setup (1st run) │
+             │                    └────────┬────────┘
+             │                             │
+             └──────────────┬──────────────┘
+                            │
+                            ▼
+                   ┌────────────────┐
+                   │ Check Git      │
+                   │ - branch       │
+                   │ - uncommitted  │
+                   └───────┬────────┘
+                           │
+         ┌─────────────────┼─────────────────┐
+         │                 │                 │
+         ▼                 ▼                 ▼
+   ┌──────────┐     ┌───────────┐     ┌───────────┐
+   │ On main  │     │ Has       │     │ No        │
+   │ branch   │     │ Changes   │     │ Changes   │
+   └────┬─────┘     └─────┬─────┘     └─────┬─────┘
+        │                 │                 │
+        ▼                 ▼                 │
+   ┌──────────┐     ┌───────────┐           │
+   │ Create   │     │ Logical   │           │
+   │ Branch   │     │ Group &   │           │
+   └────┬─────┘     │ Commit    │           │
+        │           └─────┬─────┘           │
+        │                 │                 │
+        └─────────────────┼─────────────────┘
+                          │
+                          ▼
+                 ┌────────────────┐
+                 │  Remote Push   │
+                 │  (if needed)   │
+                 └───────┬────────┘
+                         │
+                         ▼
+                ┌─────────────────┐
+                │ Check PR        │
+                │ gh pr view      │
+                └────────┬────────┘
+                         │
+           ┌─────────────┴─────────────┐
+           │                           │
+           ▼                           ▼
+    ┌─────────────┐            ┌─────────────┐
+    │  PR Exists  │            │  No PR      │
+    │  → Update   │            │  → Create   │
+    └──────┬──────┘            └──────┬──────┘
+           │                          │
+           └────────────┬─────────────┘
+                        │
+                        ▼
+               ┌────────────────┐
+               │  Return URL    │
+               │  + Screenshot  │
+               │  suggestion    │
+               └────────────────┘
+```
+
+## Auto-Commit Logic
+
+Changes are automatically grouped and committed with semantic messages:
+
+**Grouping Strategy:**
+- Analyze git diff to understand logical changes
+- Group related files by feature/purpose
+- Create separate commits for distinct changes
+- Use Conventional Commits format by default
+
+**Commit Message Format:**
+```
+<type>(<scope>): <description>
+
+[optional body]
+```
+
+**Types:** feat, fix, chore, docs, refactor, test, style, perf
+
+**Important:**
+- All commit messages in English (configurable via `commitLanguage`)
+- NO AI signature (no `Co-Authored-By: Claude` etc.)
+- Focus on what changed and why, not implementation details
+
+## PR Description Format
+
+PR descriptions are generated in the configured language and follow project templates when available.
+
+### Output Examples by Language
+
+#### When `prLanguage: "en"`
+
+**Title**: `feat: add user authentication`
+
+**Body**:
+```markdown
+## Context
+
+**Related Links:**
+- Issue: [AUTH-123](https://jira.example.com/browse/AUTH-123)
+
+**Description Details:**
+
+Added JWT-based authentication with refresh token support.
+
+## Screenshots or Videos
+
+N/A (no UI changes)
+```
+
+#### When `prLanguage: "ko"`
+
+**Title**: `feat: 사용자 인증 추가`
+
+**Body**:
+```markdown
+## 컨텍스트
+
+**관련 링크:**
+- 이슈: [AUTH-123](https://jira.example.com/browse/AUTH-123)
+
+**상세 설명:**
+
+JWT 기반 인증과 리프레시 토큰 지원을 추가했습니다.
+
+## 스크린샷 또는 비디오
+
+N/A (UI 변경 없음)
+```
+
+#### When `prLanguage: "bilingual"`
+
+**Title**: `feat: add user authentication`
+
+**Body**:
+```markdown
+## Context
+
+**Related Links:**
+- Issue: [AUTH-123](https://jira.example.com/browse/AUTH-123)
+
+**Description Details:**
+
+Added JWT-based authentication with refresh token support.
+
+---
+
+**상세 설명:**
+
+JWT 기반 인증과 리프레시 토큰 지원을 추가했습니다.
+
+## Screenshots or Videos
+
+N/A (no UI changes / UI 변경 없음)
+```
+
+### Template Definitions
+
+For detailed template definitions, see `pr-templates.md`.
+
+### Project Template Integration
+
+If `.github/pull_request_template.md` exists:
+- Use project template as base structure
+- Fill in placeholders automatically
+- Respect template sections and formatting
+- Preserve required sections
+
+## Issue ID Resolution
+
+Issue ID is resolved with the following priority:
+
+1. **Explicit argument** - `/pr-all-in-one ISSUE-123`
+2. **Branch name extraction** - `feat/ISSUE-123-description` → `ISSUE-123`
+3. **Not available** - No issue linking in PR
+
+**Branch Name Patterns:**
+- `feat/PROJ-123-add-login` → `PROJ-123`
+- `fix/123-bug-fix` → `#123` (GitHub)
+- `feature/ENG-456-new-feature` → `ENG-456`
+- `chore/update-deps` → N/A (no issue)
+
+See `issue-patterns.md` for comprehensive pattern reference.
+
+## Screenshot Guidance
+
+When UI changes are detected in the diff:
+- Suggest adding screenshots to PR description
+- Provide clear instructions on how to add them
+- Do NOT attempt to auto-capture screenshots
+- Include placeholder in PR template
+
+**UI Change Detection:**
+- Modified files in component/UI directories
+- Changes to styling files (CSS, SCSS, styled-components)
+- New UI component files
+- Modified template/JSX/Vue files
+
+## Notes
+
+**AI Signature Exclusion:**
+- Commit messages: NO `Co-Authored-By: Claude` or similar
+- PR descriptions: NO AI signature or generation attribution
+- Focus on content, not authorship attribution
+
+**Conventional Commits:**
+- Enabled by default
+- Configurable via `conventionalCommits` setting
+- Improves changelog generation and semantic versioning
+
+**Draft PR by Default:**
+- PRs created as draft by default
+- Allows review before marking ready
+- Configurable via `draftByDefault` setting
+- Author can mark ready when complete
+
+**Branch Naming:**
+- Auto-generated branches follow `branchNaming.pattern`
+- Default: `{type}/{description}`
+- Customizable with `{type}`, `{issue}`, `{description}` placeholders
+- Types restricted to `branchNaming.types` list
+
+## Related Documentation
+
+- **Configuration Guide:** `configuration-guide.md`
+- **Issue Patterns Reference:** `issue-patterns.md`
+- **PR Templates:** `pr-templates.md`
+- **Adapter Integration:** See respective adapter files