cc-devflow 4.3.0 → 4.4.1

package/.claude/skills/tdd-enforcer/SKILL.md

@@ -1,192 +0,0 @@
----
-name: devflow-tdd-enforcer
-description: Enforces TDD order in TASKS.md - Tests MUST be marked complete before Implementation tasks. Blocks violations in real-time.
----
-
-# DevFlow TDD Enforcer
-
-## Purpose
-Enforce Test-First Development (TDD) order by preventing users from marking implementation tasks complete before their corresponding test tasks.
-
-**Trigger**: PreToolUse hook when editing `devflow/requirements/**/TASKS.md`
-
-## Enforcement Rule
-
-**Source**: Extracted from planner agent's TDD mandate + Constitution Article VI
-
-### ❌ BLOCKED Pattern (Violation)
-```markdown
-- [x] **T010** [US1] Implement user registration endpoint
-- [ ] **T011** [US1] Test user registration with valid data
-```
-**Problem**: Implementation marked done BEFORE test
-
-**Regex Pattern**: `\[x\].*Implementation.*\n.*\[ \].*Test`
-
-### ✅ CORRECT Pattern (TDD Sequence)
-```markdown
-- [ ] **T010** [US1] Test user registration with valid data (write FAILING test)
-- [ ] **T011** [US1] Implement user registration endpoint (make test PASS)
-```
-
-**Or after completion**:
-```markdown
-- [x] **T010** [US1] Test user registration with valid data
-- [x] **T011** [US1] Implement user registration endpoint
-```
-
-## Blocking Message
-
-When violation detected, PreToolUse hook returns **exit code 2** (blocks file save):
-
-```
-⚠️ BLOCKED - TDD Violation Detected
-
-📋 REQUIRED ACTION:
-1. Re-order TASKS.md to follow TDD sequence
-2. Mark test tasks [x] BEFORE implementation tasks
-3. Review Constitution Article VI - Test-First Development
-
-Reason: CC-DevFlow enforces TDD (Tests First → Implementation)
-Source: planner agent mandate + Constitution Article VI
-File: {file_path}
-
-Current Issue:
-  Line {N}: Implementation task marked complete
-  Line {N+1}: Test task NOT marked complete
-
-💡 SKIP: Add `@skip-tdd-check` comment or set SKIP_TDD_ENFORCER=1
-```
-
-## Constitutional Basis
-
-### Article VI: Test-First Development
-```yaml
-TDD MANDATE:
-  - Write test FIRST (must fail)
-  - Implement code SECOND (make test pass)
-  - No implementation without corresponding test
-  - Test coverage ≥80%
-```
-
-### planner agent enforces
-- Generates TASKS.md with correct TDD order
-- Phase 2: All tests listed first
-- Phase 3+: Each user story has Test task before Implementation task
-- Inserts "⚠️ TEST VERIFICATION CHECKPOINT" between Phase 2 and Phase 3
-
-### devflow-tdd-enforcer guardrail prevents
-- Users from manually reversing that order
-- Implementation tasks marked complete before test tasks
-- Real-time detection during file editing
-
-## Additional Violation Patterns
-
-### Pattern 2: Phase 3+ User Story TDD Order
-```markdown
-# ❌ BLOCKED
-- [x] **T020** [US2] Implement login endpoint
-- [ ] **T021** [US2] Test login with valid credentials
-
-# ✅ CORRECT
-- [x] **T020** [US2] Test login with valid credentials
-- [x] **T021** **T021** [US2] Implement login endpoint
-```
-
-**Regex Pattern**: `\[x\].*\[US\d+\].*Implement.*\n.*\[ \].*\[US\d+\].*Test`
-
-### Pattern 3: Implementation without Test
-```markdown
-# ❌ BLOCKED (if no corresponding test found)
-- [ ] **T030** [US3] Implement password reset endpoint
-# (No T029 or T031 test task found)
-
-# ✅ CORRECT
-- [ ] **T029** [US3] Test password reset with valid email
-- [ ] **T030** [US3] Implement password reset endpoint
-```
-
-## Skip Conditions
-
-Users can bypass TDD enforcer in specific scenarios:
-
-### 1. Session Skip (One-time per session)
-- **Mechanism**: `sessionSkillUsed: true` in skill-rules.json
-- **Behavior**: Guardrail only triggers once per Claude session
-- **Use case**: User acknowledged TDD violation, wants to continue
-
-### 2. File Marker (Permanent skip for specific file)
-- **Marker**: Add `@skip-tdd-check` comment anywhere in TASKS.md
-- **Example**:
-  ```markdown
-  <!-- @skip-tdd-check: Hotfix deployment, will add tests in follow-up -->
-  ```
-- **Use case**: Emergency hotfix, tests to be added later
-
-### 3. Environment Variable (Temporary global skip)
-- **Variable**: `SKIP_TDD_ENFORCER=1`
-- **Scope**: Current terminal session
-- **Use case**: Batch operations, automated scripts
-
-## Relationship with Other Components
-
-### mark-task-complete.sh (Script)
-- **Purpose**: Marks tasks complete in正常 workflow (via /flow-dev)
-- **Validation**: Batch validation at phase completion
-- **Timing**: After task execution
-
-### devflow-tdd-enforcer (Guardrail)
-- **Purpose**: Real-time prevention of manual TDD violations
-- **Validation**: Per-edit, blocks save if violation detected
-- **Timing**: During file editing (PreToolUse hook)
-
-**Relationship**: **Complementary (双重保险)**
-- Script ensures正常流程 follows TDD
-- Guardrail prevents手动编辑 from breaking TDD
-
-### Constitution Article VI
-- **Defines**: TDD philosophy and mandates
-- **Enforcement**: planner agent (generation time) + devflow-tdd-enforcer (edit time)
-
-## Configuration
-
-In `.claude/skills/skill-rules.json`:
-
-```json
-{
-  "devflow-tdd-enforcer": {
-    "type": "guardrail",
-    "enforcement": "block",
-    "priority": "critical",
-    "description": "Enforces TDD order, extracted from planner agent rules",
-    "fileTriggers": {
-      "pathPatterns": ["devflow/requirements/**/TASKS.md"],
-      "contentPatterns": [
-        "\\[x\\].*Implementation.*\\n.*\\[ \\].*Test",
-        "\\[x\\].*\\[US\\d+\\].*Implement.*\\n.*\\[ \\].*\\[US\\d+\\].*Test"
-      ]
-    },
-    "blockMessage": "⚠️ BLOCKED - TDD Violation\n\nTasks must follow TDD order:\n1. [ ] Test (write failing test)\n2. [ ] Implementation (make test pass)\n\n📋 ACTION: Re-order TASKS.md\nSource: planner agent mandate + Constitution Article VI\n\n💡 SKIP: @skip-tdd-check or SKIP_TDD_ENFORCER=1",
-    "skipConditions": {
-      "sessionSkillUsed": true,
-      "fileMarkers": ["@skip-tdd-check"],
-      "envOverride": "SKIP_TDD_ENFORCER"
-    }
-  }
-}
-```
-
-## Design Principle
-
-**This guardrail does NOT contain**:
-- ❌ Complete TDD methodology (that's in planner agent)
-- ❌ Task generation logic (that's in planner agent)
-- ❌ Full Constitution Article VI (that's in project-constitution.md)
-
-**This guardrail ONLY contains**:
-- ✅ Prohibition rule extraction (from planner agent)
-- ✅ Real-time violation detection (content pattern matching)
-- ✅ Blocking mechanism (PreToolUse hook, exit code 2)
-- ✅ Links to source documentation
-
-**Rationale**: Avoid duplication ("不重不漏" principle). planner agent owns TDD generation logic, guardrail owns real-time enforcement.

package/.claude/skills/utility/npm-release/CLAUDE.md

@@ -1,55 +0,0 @@
-# npm-release Skill
-
-Version management skill with semantic versioning enforcement.
-
-## Structure
-
-```
-npm-release/
-├── SKILL.md                           # Main workflow instructions
-├── scripts/
-│   ├── validate-version-sync.sh       # Check version consistency
-│   ├── version-decision-tree.sh       # Calculate next version
-│   └── atomic-version-bump.sh         # Atomic version update
-└── references/
-    └── version-decision-guide.md      # Detailed SemVer rules
-```
-
-## Purpose
-
-Prevents version chaos by enforcing:
-1. Semantic versioning rules (no arbitrary jumps)
-2. Atomic synchronization (package.json + CHANGELOG.md + git tags)
-3. Format consistency (vX.Y.Z everywhere)
-
-## Key Scripts
-
-### validate-version-sync.sh
-Checks that package.json, git tags, and CHANGELOG.md all have matching versions.
-
-### version-decision-tree.sh
-Enforces SemVer rules:
-- Breaking change → MAJOR (X.0.0)
-- New feature → MINOR (X.Y.0)
-- Bug fix → PATCH (X.Y.Z)
-
-### atomic-version-bump.sh
-Updates all version markers in one transaction, preventing inconsistencies.
-
-## Usage
-
-```bash
-# Validate current state
-bash scripts/validate-version-sync.sh
-
-# Calculate next version
-bash scripts/version-decision-tree.sh 4.2.0 minor
-# Output: 4.3.0
-
-# Atomic bump (recommended)
-bash scripts/atomic-version-bump.sh minor "Add export command"
-```
-
----
-
-**[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md

package/.claude/skills/utility/npm-release/SKILL.md

@@ -1,379 +0,0 @@
----
-name: npm-release
-description: Use when ready to publish a new version of cc-devflow npm package to npm registry. Enforces semantic versioning rules, prevents arbitrary version jumps (e.g., 3.0.1→7.0.0), and ensures atomic synchronization across package.json, CHANGELOG.md, and git tags.
----
-
-# NPM Release Workflow
-
-## Overview
-
-Standardized release process for cc-devflow npm package ensuring consistent versioning, changelog maintenance, and safe publishing.
-
-**Core Principles**:
-1. **Atomic release** - All version markers (package.json, CHANGELOG.md, git tag) stay in sync
-2. **Semantic versioning enforcement** - Prevents arbitrary jumps and format inconsistencies
-3. **Decision tree validation** - Every version bump follows explicit SemVer rules
-
-## When to Use
-
-Use this skill when:
-- ✅ Ready to release a new version of cc-devflow
-- ✅ All changes committed and pushed
-- ✅ On main branch with clean working directory
-- ✅ Need to publish to npm registry
-
-Don't use when:
-- ❌ Working directory has uncommitted changes
-- ❌ Not on main branch
-- ❌ Pre-release/beta versions (needs adaptation)
-
-## Version Decision Protocol
-
-**MANDATORY**: Before any version bump, determine change type using the decision tree.
-
-See [references/version-decision-guide.md](references/version-decision-guide.md) for detailed rules and examples.
-
-### Quick Decision Tree
-
-```
-Is this a breaking change?
-├─ YES → MAJOR bump (X.0.0)
-└─ NO → Is this a new feature?
-    ├─ YES → MINOR bump (X.Y.0)
-    └─ NO → PATCH bump (X.Y.Z)
-```
-
-### Release Types
-
-Follow [Semantic Versioning](https://semver.org/):
-
-| Type | Version Change | When |
-|------|---------------|------|
-| **Patch** | 4.2.0 → 4.2.1 | Bug fixes, minor improvements |
-| **Minor** | 4.2.1 → 4.3.0 | New features, backward compatible |
-| **Major** | 4.3.0 → 5.0.0 | Breaking changes |
-
-### Anti-Patterns (FORBIDDEN)
-
-❌ **Arbitrary jumps**: 3.0.1 → 7.0.0 (no justification)
-❌ **Skipping versions**: 4.2.0 → 4.4.0 (skipped 4.3.0)
-❌ **Inconsistent formats**: v1.0, 1.0.0, release-1.0 (mixed formats)
-
-## Complete Workflow
-
-### Phase 0: Version Validation (MANDATORY)
-
-**Before any changes**, validate current state and determine next version:
-
-```bash
-# 1. Validate version synchronization
-bash .claude/skills/utility/npm-release/scripts/validate-version-sync.sh
-
-# 2. Determine change type (patch/minor/major)
-# Use decision tree in references/version-decision-guide.md
-
-# 3. Calculate next version
-bash .claude/skills/utility/npm-release/scripts/version-decision-tree.sh $(grep -o '"version": *"[^"]*"' package.json | grep -o '[0-9]\+\.[0-9]\+\.[0-9]\+') <patch|minor|major>
-```
-
-**STOP if validation fails** - Fix inconsistencies before proceeding.
-
-### Phase 1: Pre-Release Checks
-
-```bash
-# 1. Verify git status
-git status
-# MUST show: "On branch main", "working tree clean"
-
-# 2. Check current version
-cat package.json | grep version
-# e.g., "version": "4.2.0"
-
-# 3. Review recent changes
-git log --oneline -10
-```
-
-**STOP if**:
-- Not on main branch
-- Uncommitted changes exist
-- Unpushed commits exist
-
-### Phase 2: Atomic Version Bump
-
-**Use the atomic bump script** (recommended):
-
-```bash
-# Automatically updates package.json + CHANGELOG.md
-bash .claude/skills/utility/npm-release/scripts/atomic-version-bump.sh <patch|minor|major> "Brief description"
-
-# Example:
-bash .claude/skills/utility/npm-release/scripts/atomic-version-bump.sh minor "Add export command"
-```
-
-**Or manual update** (if script unavailable):
-
-**Step 1: Update package.json**
-
-```bash
-npm version patch --no-git-tag-version  # For patch release
-npm version minor --no-git-tag-version  # For minor release
-npm version major --no-git-tag-version  # For major release
-```
-
-**Step 2: Update CHANGELOG.md**
-
-Add new version section at the top (after `---`):
-
-```markdown
-## [X.Y.Z] - YYYY-MM-DD
-
-### 🎯 Release Title
-
-Brief description of main changes.
-
-#### Changed / Added / Fixed
-- Bullet point 1
-- Bullet point 2
-
-#### Benefits
-- ✅ Benefit 1
-- ✅ Benefit 2
-```
-
-### Phase 3: Git Operations
-
-**Step 1: Create Release Commit**
-
-```bash
-git add CHANGELOG.md package.json
-
-git commit -m "$(cat <<'EOF'
-chore(release): bump version to X.Y.Z
-
-Release X.Y.Z - [Brief title]
-
-主要变更：
-- 变更点 1
-- 变更点 2
-
-Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
-EOF
-)"
-```
-
-**Step 2: Create Annotated Tag**
-
-```bash
-git tag -a vX.Y.Z -m "$(cat <<'EOF'
-Release vX.Y.Z - [Brief title]
-
-🎯 Main changes:
-- Change 1
-- Change 2
-
-Benefits:
-✅ Benefit 1
-✅ Benefit 2
-
-Full changelog: https://github.com/Dimon94/cc-devflow/blob/main/CHANGELOG.md
-EOF
-)"
-```
-
-**Step 3: Verify**
-
-```bash
-# Check commit
-git log --oneline -1
-
-# Check tag
-git tag -l "v2.4.*" | tail -3
-
-# Verify tag annotation
-git show vX.Y.Z
-```
-
-### Phase 4: Publish
-
-**Step 1: Push to GitHub**
-
-```bash
-# Push commits
-git push origin main
-
-# Push tags
-git push origin vX.Y.Z
-# Or push all tags: git push origin --tags
-```
-
-**Step 2: Create GitHub Release (Optional)**
-
-Via GitHub CLI:
-```bash
-gh release create vX.Y.Z \
-  --title "vX.Y.Z - [Title]" \
-  --notes-file <(sed -n '/## \[X.Y.Z\]/,/## \[/p' CHANGELOG.md | head -n -1)
-```
-
-Or manually at: https://github.com/Dimon94/cc-devflow/releases/new
-
-**Step 3: Publish to npm**
-
-```bash
-# Test publish first (dry-run)
-npm publish --dry-run
-
-# Actual publish
-npm publish
-
-# Verify publication
-npm view cc-devflow version
-```
-
-## Quick Reference
-
-| Step | Command | Purpose |
-|------|---------|---------|
-| **Validate sync** | `bash scripts/validate-version-sync.sh` | Check version consistency |
-| **Decide version** | `bash scripts/version-decision-tree.sh <current> <type>` | Calculate next version |
-| **Atomic bump** | `bash scripts/atomic-version-bump.sh <type> "desc"` | Update all markers |
-| Check status | `git status` | Verify clean state |
-| Check version | `grep version package.json` | Current version |
-| Create commit | `git commit -m "chore(release): ..."` | Commit version bump |
-| Create tag | `git tag -a vX.Y.Z -m "..."` | Tag release |
-| Push commits | `git push origin main` | Push to GitHub |
-| Push tags | `git push origin vX.Y.Z` | Push tag to GitHub |
-| Publish npm | `npm publish` | Publish to registry |
-
-## Version Management Scripts
-
-Three scripts enforce version discipline:
-
-1. **validate-version-sync.sh** - Checks package.json, git tags, CHANGELOG.md consistency
-2. **version-decision-tree.sh** - Calculates next version following SemVer rules
-3. **atomic-version-bump.sh** - Updates all version markers atomically
-
-**Usage**:
-```bash
-# Check current state
-bash .claude/skills/utility/npm-release/scripts/validate-version-sync.sh
-
-# Calculate next version
-bash .claude/skills/utility/npm-release/scripts/version-decision-tree.sh 4.2.0 minor
-# Output: 4.3.0
-
-# Atomic bump (recommended)
-bash .claude/skills/utility/npm-release/scripts/atomic-version-bump.sh minor "Add export command"
-```
-
-## Common Mistakes
-
-### ❌ Mistake 1: Arbitrary Version Jumps
-
-**Problem**: Version jumps from 3.0.1 to 7.0.0 without justification
-
-**Fix**: Use version-decision-tree.sh to calculate correct next version based on change type
-
-### ❌ Mistake 2: Inconsistent Version Numbers
-
-**Problem**: package.json shows 4.2.1 but CHANGELOG.md shows 4.2.0
-
-**Fix**: Use atomic-version-bump.sh to update all markers simultaneously
-
-### ❌ Mistake 3: Forgetting to Update CHANGELOG.md
-
-**Problem**: Version bumped but no changelog entry
-
-**Fix**: Always update CHANGELOG.md BEFORE committing (atomic-version-bump.sh does this automatically)
-
-### ❌ Mistake 4: Pushing Tag Before Commit
-
-**Problem**: Tag points to wrong commit
-
-**Fix**: Always commit first, then tag, then push both together
-
-### ❌ Mistake 5: Not Testing npm publish
-
-**Problem**: Published package is broken
-
-**Fix**: Run `npm publish --dry-run` first to catch issues
-
-### ❌ Mistake 6: Inconsistent Tag Format
-
-**Problem**: Mixed formats like v1.0, 1.0.0, release-1.0
-
-**Fix**: Always use vX.Y.Z format (e.g., v4.2.0). validate-version-sync.sh detects format inconsistencies
-
-## Network Troubleshooting
-
-If `git push` fails with timeout:
-
-1. **Check network connectivity**:
-   ```bash
-   curl -I https://github.com 2>&1 | head -5
-   ```
-
-2. **Try SSH instead of HTTPS**:
-   ```bash
-   git remote -v  # Check current remote URL
-   git remote set-url origin git@github.com:Dimon94/cc-devflow.git
-   ```
-
-3. **If SSH fails (publickey error)**:
-   - Check SSH key: `ssh -T git@github.com`
-   - Add SSH key to GitHub: https://github.com/settings/keys
-   - Or stay with HTTPS and retry later
-
-4. **Commits and tags are safe locally**:
-   - They won't be lost
-   - Push when network is available
-
-## Post-Release Verification
-
-After successful release:
-
-```bash
-# 1. Verify GitHub tag
-open https://github.com/Dimon94/cc-devflow/tags
-
-# 2. Verify npm package
-npm view cc-devflow version
-npm view cc-devflow time
-
-# 3. Test installation
-npm install -g cc-devflow@latest
-cc-devflow --version  # Should show new version
-```
-
-## Rollback (If Needed)
-
-If published version has critical bugs:
-
-```bash
-# 1. Unpublish from npm (within 72 hours)
-npm unpublish cc-devflow@X.Y.Z
-
-# 2. Delete git tag locally and remotely
-git tag -d vX.Y.Z
-git push origin :refs/tags/vX.Y.Z
-
-# 3. Revert commit
-git revert HEAD
-
-# 4. Fix bug and re-release with new patch version
-```
-
-**Note**: npm unpublish is only available within 72 hours of publication. After that, publish a new patch version instead.
-
-## Real-World Impact
-
-Following this workflow ensures:
-- ✅ **Consistency**: All version markers stay in sync
-- ✅ **Traceability**: Clear changelog and git history
-- ✅ **Safety**: Dry-run catches issues before publishing
-- ✅ **Recoverability**: Can rollback if needed
-- ✅ **Automation-ready**: Scriptable workflow for future CI/CD
-
----
-
-**[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md