universal-dev-standards 3.5.1-beta.1 → 3.5.1-beta.11

package/bundled/skills/claude-code/code-review-assistant/checkin-checklist.md

@@ -0,0 +1,249 @@
+# Pre-Commit Checklist
+
+> **Language**: English | [繁體中文](../../../locales/zh-TW/skills/claude-code/code-review-assistant/checkin-checklist.md)
+
+**Version**: 1.0.0
+**Last Updated**: 2025-12-24
+**Applicability**: Claude Code Skills
+
+---
+
+## Purpose
+
+This document provides a checklist for developers to verify before committing code changes.
+
+---
+
+## Mandatory Checks
+
+### 1. Build Verification
+
+- [ ] **Code compiles successfully**
+  - Zero build errors
+  - Zero build warnings (or documented exceptions)
+
+- [ ] **Dependencies are satisfied**
+  - All package dependencies installed
+  - Dependency versions locked
+  - No missing imports
+
+---
+
+### 2. Test Verification
+
+- [ ] **All existing tests pass**
+  - Unit tests: 100% pass rate
+  - Integration tests: 100% pass rate
+
+- [ ] **New code is tested**
+  - New features have corresponding tests
+  - Bug fixes include regression tests
+
+- [ ] **Test coverage maintained**
+  - Coverage percentage not decreased
+  - Critical paths tested
+
+---
+
+### 3. Code Quality
+
+- [ ] **Follows coding standards**
+  - Naming conventions adhered to
+  - Code formatting consistent
+  - Comments present where needed
+
+- [ ] **No code smells**
+  - Methods ≤50 lines
+  - Nesting depth ≤3 levels
+  - Cyclomatic complexity ≤10
+  - No duplicated code blocks
+
+- [ ] **Security checked**
+  - No hardcoded secrets
+  - No SQL injection vulnerabilities
+  - No XSS vulnerabilities
+  - No insecure dependencies
+
+---
+
+### 4. Documentation
+
+- [ ] **API documentation updated**
+  - Public APIs have doc comments
+  - Parameters explained
+  - Return values documented
+
+- [ ] **README updated (if needed)**
+  - New features documented
+  - Breaking changes noted
+
+- [ ] **CHANGELOG updated (if applicable)**
+  - User-facing changes added to `[Unreleased]`
+  - Breaking changes marked
+
+---
+
+### 5. Workflow Compliance
+
+- [ ] **Branch naming correct**
+  - Follows project convention (`feature/`, `fix/`)
+
+- [ ] **Commit message formatted**
+  - Follows conventional commits or project standard
+
+- [ ] **Synchronized with target branch**
+  - Merged latest changes from target branch
+  - No merge conflicts
+
+---
+
+## Commit Timing Guidelines
+
+### ✅ Appropriate Times to Commit
+
+1. **Completed Functional Unit**
+   - Feature fully implemented
+   - Tests written and passing
+   - Documentation updated
+
+2. **Specific Bug Fixed**
+   - Bug reproduced and fixed
+   - Regression test added
+
+3. **Independent Refactor**
+   - Refactoring complete
+   - No functional changes
+   - All tests still pass
+
+4. **Runnable State**
+   - Code compiles without errors
+   - Application can run/start
+   - Core functionality not broken
+
+### ❌ Inappropriate Times to Commit
+
+1. **Build Failures**
+   - Compilation errors present
+   - Unresolved dependencies
+
+2. **Test Failures**
+   - One or more tests failing
+   - Tests not yet written for new code
+
+3. **Incomplete Features**
+   - Feature partially implemented
+   - Would break existing functionality
+
+4. **Experimental Code**
+   - TODO comments scattered
+   - Debugging code left in
+   - Commented-out code blocks
+
+---
+
+## Commit Granularity
+
+### Ideal Commit Size
+
+| Metric | Recommended |
+|--------|-------------|
+| File Count | 1-10 files |
+| Lines Changed | 50-300 lines |
+| Scope | Single concern |
+
+### Splitting Principles
+
+**Combine into one commit**:
+- Feature implementation + corresponding tests
+- Tightly related multi-file changes
+
+**Separate commits**:
+- Feature A + Feature B → separate
+- Refactoring + new feature → separate
+- Bug fix + incidental refactoring → separate
+
+---
+
+## Special Scenarios
+
+### Emergency Leave (WIP)
+
+**Option 1: Git Stash (Recommended)**
+```bash
+git stash save "WIP: description of incomplete work"
+# Resume later
+git stash pop
+```
+
+**Option 2: WIP Branch**
+```bash
+git checkout -b wip/feature-temp
+git commit -m "WIP: progress save (do not merge)"
+```
+
+### Hotfix
+
+1. Create hotfix branch from main
+2. Minimize changes (only fix the problem)
+3. Quick verification (ensure tests pass)
+4. Mark urgency in commit message:
+   ```
+   fix(module): [URGENT] fix critical issue
+   ```
+
+---
+
+## Common Violations
+
+### ❌ "WIP" Commits
+
+```
+git commit -m "WIP"
+git commit -m "save work"
+git commit -m "trying stuff"
+```
+
+**Solution**: Use `git stash` or squash before merging
+
+### ❌ Commented-Out Code
+
+**Problem**: Clutters codebase, confuses future developers
+
+**Solution**: Delete it. Git history preserves old code.
+
+### ❌ Mixing Concerns
+
+```
+git commit -m "fix bug and refactor and add feature"
+```
+
+**Solution**: Separate into multiple commits:
+```
+git commit -m "fix(module-a): resolve null pointer error"
+git commit -m "refactor(module-b): extract validation logic"
+git commit -m "feat(module-c): add export feature"
+```
+
+---
+
+## Related Standards
+
+- [Checkin Standards](../../../core/checkin-standards.md)
+- [Code Review Checklist](./review-checklist.md)
+- [Commit Message Guide](../../../core/commit-message-guide.md)
+
+---
+
+## Version History
+
+| Version | Date | Changes |
+|---------|------|---------|
+| 1.0.0 | 2025-12-24 | Added: Standard sections (Purpose, Related Standards, Version History, License) |
+
+---
+
+## License
+
+This document is released under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
+
+**Source**: [universal-dev-standards](https://github.com/AsiaOstrich/universal-dev-standards)

package/bundled/skills/claude-code/code-review-assistant/review-checklist.md

@@ -0,0 +1,238 @@
+# Code Review Checklist
+
+> **Language**: English | [繁體中文](../../../locales/zh-TW/skills/claude-code/code-review-assistant/review-checklist.md)
+
+**Version**: 1.0.0
+**Last Updated**: 2025-12-24
+**Applicability**: Claude Code Skills
+
+---
+
+## Purpose
+
+This document provides a comprehensive checklist for code review to ensure code quality and standards compliance.
+
+---
+
+## 1. Functionality
+
+- [ ] **Code does what it's supposed to do**
+  - Requirement/spec alignment verified
+  - Acceptance criteria met
+  - Edge cases handled
+
+- [ ] **No obvious bugs**
+  - Null/undefined checks present
+  - Array bounds checked
+  - Error conditions handled
+
+- [ ] **Logic is correct**
+  - Conditions make sense
+  - Loops terminate properly
+  - Calculations are accurate
+
+---
+
+## 2. Design & Architecture
+
+- [ ] **Follows project architecture**
+  - Layering respected
+  - Separation of concerns maintained
+  - Dependency direction correct
+
+- [ ] **Appropriate design patterns used**
+  - Not over-engineered
+  - Not under-engineered
+  - Patterns applied correctly
+
+- [ ] **Code is in the right place**
+  - Files organized logically
+  - Related code grouped together
+
+---
+
+## 3. Code Quality
+
+- [ ] **Follows coding standards**
+  - Naming conventions adhered to
+  - Formatting consistent
+  - Style guide followed
+
+- [ ] **No code smells**
+  - Methods ≤50 lines
+  - Classes have single responsibility
+  - Cyclomatic complexity ≤10
+  - No deeply nested conditionals (≤3 levels)
+
+- [ ] **DRY principle applied**
+  - No duplicated code blocks
+  - Common logic extracted
+
+---
+
+## 4. Readability
+
+- [ ] **Code is easy to understand**
+  - Variable names are descriptive
+  - Function names reveal intent
+  - Logic flows naturally
+
+- [ ] **Comments are helpful**
+  - Complex logic explained
+  - WHY documented, not WHAT
+  - No commented-out code
+
+---
+
+## 5. Testing
+
+- [ ] **Tests are present**
+  - New code has tests
+  - Tests cover happy path
+  - Tests cover error cases
+  - Edge cases tested
+
+- [ ] **Tests are good quality**
+  - Tests are readable
+  - Test names describe scenarios
+  - Assertions are clear
+  - No flaky tests
+
+- [ ] **Test coverage maintained**
+  - Coverage not decreased
+  - Critical paths covered
+
+---
+
+## 6. Security
+
+- [ ] **No security vulnerabilities**
+  - No SQL injection risks
+  - No XSS vulnerabilities
+  - No hardcoded secrets
+  - No insecure dependencies
+
+- [ ] **Input validation present**
+  - User input sanitized
+  - Type checking performed
+  - Size limits enforced
+
+- [ ] **Auth/Authorization correct**
+  - Proper auth checks
+  - Role-based access enforced
+  - Sensitive data protected
+
+---
+
+## 7. Performance
+
+- [ ] **No obvious performance issues**
+  - No N+1 queries
+  - No unnecessary loops
+  - No blocking operations in hot paths
+
+- [ ] **Efficient algorithms used**
+  - Complexity considered
+  - Appropriate data structures
+  - Caching where beneficial
+
+- [ ] **Resource management proper**
+  - Connections closed
+  - Memory leaks prevented
+  - File handles released
+
+---
+
+## 8. Error Handling
+
+- [ ] **Errors handled appropriately**
+  - Try-catch blocks present
+  - Specific exceptions caught
+  - Generic catch avoided
+
+- [ ] **Error messages helpful**
+  - Messages are descriptive
+  - Actionable information included
+  - No sensitive data exposed
+
+- [ ] **Logging is adequate**
+  - Errors logged with context
+  - Log levels appropriate
+  - No excessive logging
+
+---
+
+## 9. Documentation
+
+- [ ] **API documentation present**
+  - Public methods documented
+  - Parameters explained
+  - Return values described
+  - Exceptions documented
+
+- [ ] **README updated if needed**
+  - New features documented
+  - Setup instructions current
+
+- [ ] **CHANGELOG updated (if applicable)**
+  - User-facing changes added to `[Unreleased]`
+  - Breaking changes marked with **BREAKING**
+
+---
+
+## 10. Dependencies
+
+- [ ] **Dependencies justified**
+  - New dependencies necessary
+  - License compatible
+  - No security vulnerabilities
+  - Actively maintained
+
+- [ ] **Dependency versions locked**
+  - Exact versions specified
+  - Lock file updated
+
+---
+
+## Quick Reference Card
+
+```
+┌─────────────────────────────────────────┐
+│ Code Review Quick Checklist            │
+├─────────────────────────────────────────┤
+│ ✓ Functionality - Does it work?        │
+│ ✓ Design - Right architecture?         │
+│ ✓ Quality - Clean code?                │
+│ ✓ Readability - Easy to understand?    │
+│ ✓ Tests - Adequate coverage?           │
+│ ✓ Security - No vulnerabilities?       │
+│ ✓ Performance - Efficient?             │
+│ ✓ Errors - Properly handled?           │
+│ ✓ Docs - Updated?                      │
+│ ✓ Dependencies - Necessary?            │
+└─────────────────────────────────────────┘
+```
+
+---
+
+## Related Standards
+
+- [Code Review Checklist](../../../core/code-review-checklist.md)
+- [Checkin Standards](../../../core/checkin-standards.md)
+- [Pre-Commit Checklist](./checkin-checklist.md)
+
+---
+
+## Version History
+
+| Version | Date | Changes |
+|---------|------|---------|
+| 1.0.0 | 2025-12-24 | Added: Standard sections (Purpose, Related Standards, Version History, License) |
+
+---
+
+## License
+
+This document is released under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
+
+**Source**: [universal-dev-standards](https://github.com/AsiaOstrich/universal-dev-standards)

package/bundled/skills/claude-code/commands/README.md

@@ -0,0 +1,78 @@
+# Claude Code Custom Commands
+
+Custom slash commands for Universal Development Standards.
+
+## Available Commands | 可用命令
+
+### Standards Management | 標準管理
+
+Commands for managing Universal Development Standards in your project.
+
+| Command | Description | 說明 |
+|---------|-------------|------|
+| [`/init`](./init.md) | Initialize standards in project | 初始化專案標準 |
+| [`/update`](./update.md) | Update standards to latest version | 更新標準至最新版本 |
+| [`/check`](./check.md) | Verify adoption status | 檢查採用狀態 |
+| [`/config`](./config.md) | Configure standards settings | 配置標準設定 |
+
+### Development Workflow | 開發工作流程
+
+Commands for development workflow automation.
+
+| Command | Description | 說明 |
+|---------|-------------|------|
+| [`/commit`](./commit.md) | Generate conventional commit messages | 產生 commit message |
+| [`/review`](./review.md) | Perform systematic code review | 執行程式碼審查 |
+| [`/release`](./release.md) | Guide through release process | 引導發布流程 |
+| [`/changelog`](./changelog.md) | Update CHANGELOG.md | 更新 CHANGELOG |
+| [`/requirement`](./requirement.md) | Write user stories and requirements | 撰寫需求文件 |
+| [`/spec`](./spec.md) | Create specification documents | 建立規格文件 |
+| [`/docs`](./docs.md) | Create/update documentation | 建立/更新文件 |
+| [`/coverage`](./coverage.md) | Analyze test coverage | 分析測試覆蓋率 |
+
+### Methodology | 方法論
+
+Commands for development methodology workflows.
+
+| Command | Description | 說明 |
+|---------|-------------|------|
+| [`/methodology`](./methodology.md) | Manage active methodology | 管理開發方法論 |
+| [`/tdd`](./tdd.md) | Test-Driven Development workflow | TDD 開發流程 |
+| [`/bdd`](./bdd.md) | Behavior-Driven Development workflow | BDD 開發流程 |
+
+## Commands vs Skills | 命令與技能
+
+| Aspect | Commands | Skills |
+|--------|----------|--------|
+| **Trigger** | Manual (`/command`) | Automatic (context-based) |
+| **Location** | `commands/` | `skills/` or root |
+| **Use Case** | Explicit action | Background assistance |
+
+## Adding Custom Commands | 新增自訂命令
+
+Create a `.md` file in the `commands/` directory:
+
+```markdown
+---
+description: Brief description of the command
+allowed-tools: Read, Write, Bash(git:*)
+argument-hint: "[optional arguments]"
+---
+
+# Command Name
+
+Instructions for Claude...
+```
+
+## Installation | 安裝
+
+Commands are automatically available after installing the plugin:
+
+```bash
+/plugin marketplace add AsiaOstrich/universal-dev-standards
+/plugin install universal-dev-standards@asia-ostrich
+```
+
+## License | 授權
+
+Dual-licensed: CC BY 4.0 (documentation) + MIT (code)

package/bundled/skills/claude-code/commands/bdd.md

@@ -0,0 +1,142 @@
+---
+description: Guide through Behavior-Driven Development workflow
+allowed-tools: Read, Write, Grep, Glob, Bash(npm test:*), Bash(npx:*)
+argument-hint: "[behavior or scenario to implement | 要實作的行為或場景]"
+status: experimental
+---
+
+# BDD Assistant | BDD 助手
+
+> [!WARNING]
+> **Experimental Feature / 實驗性功能**
+>
+> This feature is under active development and may change significantly in v4.0.
+> 此功能正在積極開發中，可能在 v4.0 中有重大變更。
+
+Guide through the Behavior-Driven Development (BDD) workflow using Given-When-Then format.
+
+引導行為驅動開發（BDD）流程，使用 Given-When-Then 格式。
+
+## Methodology Integration | 方法論整合
+
+When `/bdd` is invoked:
+1. **Automatically activate BDD methodology** if not already active
+2. **Set current phase to DISCOVERY** (exploring behavior)
+3. **Track phase transitions** as work progresses
+4. **Show phase indicators** in responses (🔍 Discovery, 📝 Formulation, 🤖 Automation, 📚 Living Docs)
+
+當調用 `/bdd` 時：
+1. **自動啟用 BDD 方法論**（如果尚未啟用）
+2. **將當前階段設為探索**（探索行為）
+3. **追蹤階段轉換**隨著工作進展
+4. **在回應中顯示階段指示器**（🔍 探索、📝 制定、🤖 自動化、📚 活文件）
+
+See [methodology-system](../methodology-system/SKILL.md) for full methodology tracking.
+
+## BDD Cycle | BDD 循環
+
+```
+┌───────────────────────────────────────────────────────┐
+│                                                       │
+│  ┌─────────┐   ┌───────────┐   ┌──────────┐   ┌────┐ │
+│  │DISCOVERY│ ► │FORMULATION│ ► │AUTOMATION│ ► │DOCS│ │
+│  └─────────┘   └───────────┘   └──────────┘   └────┘ │
+│       ▲                                    │          │
+│       └────────────────────────────────────┘          │
+│                                                       │
+└───────────────────────────────────────────────────────┘
+```
+
+## Workflow | 工作流程
+
+### 1. DISCOVERY - Explore Behavior | 探索行為
+- Discuss with stakeholders
+- Identify examples and edge cases
+- Understand the "why" behind features
+
+### 2. FORMULATION - Write Scenarios | 制定場景
+- Write Gherkin scenarios (Given-When-Then)
+- Use ubiquitous language
+- Make scenarios concrete and specific
+
+### 3. AUTOMATION - Implement Tests | 自動化測試
+- Implement step definitions
+- Write minimal code to pass
+- Follow the TDD cycle within automation
+
+### 4. LIVING DOCUMENTATION - Maintain | 活文件維護
+- Keep scenarios up to date
+- Use as documentation
+- Share with stakeholders
+
+## Gherkin Format | Gherkin 格式
+
+```gherkin
+Feature: User Login
+  As a registered user
+  I want to log in to my account
+  So that I can access my personal dashboard
+
+  Scenario: Successful login with valid credentials
+    Given I am on the login page
+    And I have a registered account with email "user@example.com"
+    When I enter my email "user@example.com"
+    And I enter my password "correctpassword"
+    And I click the login button
+    Then I should be redirected to my dashboard
+    And I should see a welcome message
+
+  Scenario: Failed login with invalid password
+    Given I am on the login page
+    When I enter my email "user@example.com"
+    And I enter my password "wrongpassword"
+    And I click the login button
+    Then I should see an error message "Invalid credentials"
+    And I should remain on the login page
+```
+
+## Three Amigos | 三劍客會議
+
+BDD works best with collaboration:
+
+| Role | Focus | 角色 | 關注點 |
+|------|-------|------|--------|
+| Business | What & Why | 業務 | 什麼和為什麼 |
+| Development | How | 開發 | 如何實現 |
+| Testing | What if | 測試 | 假設情況 |
+
+## Usage | 使用方式
+
+- `/bdd` - Start interactive BDD session
+- `/bdd "user can reset password"` - BDD for specific feature
+- `/bdd login-feature.feature` - Work with existing feature file
+
+## Phase Checklist | 階段檢查清單
+
+### Discovery Phase
+- [ ] Stakeholders identified
+- [ ] User stories discussed
+- [ ] Examples collected
+- [ ] Edge cases identified
+
+### Formulation Phase
+- [ ] Scenarios follow Given-When-Then
+- [ ] Language is ubiquitous (shared vocabulary)
+- [ ] Scenarios are specific and concrete
+- [ ] No implementation details in scenarios
+
+### Automation Phase
+- [ ] Step definitions implemented
+- [ ] Tests are executable
+- [ ] Code passes all scenarios
+- [ ] Refactoring complete
+
+### Living Documentation Phase
+- [ ] Scenarios are current
+- [ ] Documentation is accessible
+- [ ] Stakeholders can read and understand
+
+## Reference | 參考
+
+- Methodology: [bdd.methodology.yaml](../../../../methodologies/bdd.methodology.yaml)
+- Methodology System: [methodology-system](../methodology-system/SKILL.md)