cc-devflow 4.3.0 → 4.4.1

package/.claude/skills/utility/npm-release/references/version-decision-guide.md

@@ -1,134 +0,0 @@
-# Version Decision Reference
-
-## Semantic Versioning Rules
-
-**Format**: `MAJOR.MINOR.PATCH` (e.g., 4.2.0)
-
-### When to Bump Each Number
-
-| Version | Increment When | Examples |
-|---------|---------------|----------|
-| **MAJOR** | Breaking changes that require user action | API redesign, removed features, incompatible changes |
-| **MINOR** | New features, backward compatible | New commands, new options, enhanced functionality |
-| **PATCH** | Bug fixes, minor improvements | Fix crashes, improve error messages, documentation |
-
-### 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)
-```
-
-## Common Scenarios
-
-### Scenario 1: Bug Fix
-**Current**: 4.2.0
-**Change**: Fix login crash
-**Decision**: PATCH → **4.2.1**
-
-### Scenario 2: New Feature (Compatible)
-**Current**: 4.2.1
-**Change**: Add `/flow:export` command
-**Decision**: MINOR → **4.3.0**
-
-### Scenario 3: Breaking Change
-**Current**: 4.3.0
-**Change**: Remove deprecated `/flow-new` command
-**Decision**: MAJOR → **5.0.0**
-
-### Scenario 4: Multiple Changes
-**Current**: 4.3.0
-**Changes**:
-- Fix 3 bugs (PATCH)
-- Add 2 new features (MINOR)
-- No breaking changes
-
-**Decision**: Take highest level → MINOR → **4.4.0**
-
-## Anti-Patterns (FORBIDDEN)
-
-### ❌ Arbitrary Jumps
-```
-3.0.1 → 7.0.0  # WRONG: No justification for jumping 4 major versions
-```
-
-**Correct**:
-```
-3.0.1 → 4.0.0  # If breaking change
-3.0.1 → 3.1.0  # If new feature
-3.0.1 → 3.0.2  # If bug fix
-```
-
-### ❌ Skipping Versions
-```
-4.2.0 → 4.4.0  # WRONG: Skipped 4.3.0
-```
-
-**Correct**:
-```
-4.2.0 → 4.3.0 → 4.4.0  # Sequential
-```
-
-### ❌ Inconsistent Formats
-```
-v1.0          # WRONG: Missing patch
-1.0.0         # WRONG: Missing 'v' prefix in git tag
-release-1.0   # WRONG: Non-standard format
-```
-
-**Correct**:
-```
-Git tag:      v4.2.0
-package.json: "version": "4.2.0"
-CHANGELOG:    ## [4.2.0] - 2026-03-12
-```
-
-## Version Validation Checklist
-
-Before bumping version, verify:
-
-- [ ] Change type is clear (patch/minor/major)
-- [ ] Version increment follows SemVer rules
-- [ ] No arbitrary jumps (e.g., 3.x → 7.x)
-- [ ] All version markers will be updated atomically
-- [ ] CHANGELOG.md entry prepared
-- [ ] Git tag format will be `vX.Y.Z`
-
-## Breaking Change Examples
-
-**Breaking changes require MAJOR bump**:
-
-- Removing commands or options
-- Changing command syntax
-- Changing output format (breaking scripts)
-- Removing configuration options
-- Changing default behavior significantly
-- Requiring new dependencies
-- Dropping support for Node versions
-
-**NOT breaking changes** (MINOR or PATCH):
-
-- Adding new commands (MINOR)
-- Adding new options with defaults (MINOR)
-- Deprecation warnings (MINOR)
-- Bug fixes (PATCH)
-- Performance improvements (PATCH)
-- Documentation updates (PATCH)
-
-## Version History Analysis
-
-Use this to understand past version decisions:
-
-```bash
-# View version history
-git tag --sort=v:refname
-
-# View changes between versions
-git log v4.1.0..v4.2.0 --oneline
-
-# Check CHANGELOG for version rationale
-grep -A 10 "## \[4.2.0\]" CHANGELOG.md
-```

package/.claude/skills/utility/npm-release/scripts/atomic-version-bump.sh

@@ -1,95 +0,0 @@
-#!/usr/bin/env bash
-# Atomic Version Bump - Updates all version markers in one transaction
-# Ensures package.json, CHANGELOG.md stay in sync
-
-set -euo pipefail
-
-CHANGE_TYPE="${1:-}"
-CHANGE_DESCRIPTION="${2:-}"
-
-if [[ -z "$CHANGE_TYPE" ]]; then
-    echo "Usage: $0 <patch|minor|major> [description]"
-    echo ""
-    echo "Examples:"
-    echo "  $0 patch 'Fix login bug'"
-    echo "  $0 minor 'Add user dashboard'"
-    echo "  $0 major 'Redesign API'"
-    exit 1
-fi
-
-# Get script directory
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-
-# 1. Get current version
-CURRENT_VERSION=$(grep -o '"version": *"[^"]*"' package.json | grep -o '[0-9]\+\.[0-9]\+\.[0-9]\+')
-echo "📦 Current version: $CURRENT_VERSION"
-
-# 2. Calculate next version using decision tree
-NEXT_VERSION=$("$SCRIPT_DIR/version-decision-tree.sh" "$CURRENT_VERSION" "$CHANGE_TYPE")
-echo "🎯 Next version: $NEXT_VERSION"
-
-# 3. Validate version sync before proceeding
-echo ""
-echo "🔍 Pre-flight validation..."
-if ! "$SCRIPT_DIR/validate-version-sync.sh"; then
-    echo ""
-    echo "❌ Version sync validation failed. Fix inconsistencies before bumping."
-    exit 1
-fi
-
-# 4. Update package.json
-echo ""
-echo "📝 Updating package.json..."
-sed -i.bak "s/\"version\": \"$CURRENT_VERSION\"/\"version\": \"$NEXT_VERSION\"/" package.json
-rm package.json.bak
-
-# 5. Prepare CHANGELOG.md entry
-CURRENT_DATE=$(date +%Y-%m-%d)
-CHANGELOG_ENTRY="## [$NEXT_VERSION] - $CURRENT_DATE
-
-### 🎯 ${CHANGE_DESCRIPTION:-Version $NEXT_VERSION}
-
-#### Changed
-- TODO: Add change details
-
----
-
-"
-
-# Insert after the first "---" line in CHANGELOG.md
-if [[ -f "CHANGELOG.md" ]]; then
-    echo "📝 Updating CHANGELOG.md..."
-    # Create temp file with new entry
-    awk -v entry="$CHANGELOG_ENTRY" '
-        /^---$/ && !inserted {
-            print
-            print entry
-            inserted=1
-            next
-        }
-        {print}
-    ' CHANGELOG.md > CHANGELOG.md.tmp
-    mv CHANGELOG.md.tmp CHANGELOG.md
-else
-    echo "⚠️  CHANGELOG.md not found, skipping"
-fi
-
-# 6. Validate post-update
-echo ""
-echo "🔍 Post-update validation..."
-UPDATED_VERSION=$(grep -o '"version": *"[^"]*"' package.json | grep -o '[0-9]\+\.[0-9]\+\.[0-9]\+')
-
-if [[ "$UPDATED_VERSION" != "$NEXT_VERSION" ]]; then
-    echo "❌ Version update failed: expected $NEXT_VERSION, got $UPDATED_VERSION"
-    exit 1
-fi
-
-echo ""
-echo "✅ Version bumped successfully: $CURRENT_VERSION → $NEXT_VERSION"
-echo ""
-echo "📋 Next steps:"
-echo "   1. Edit CHANGELOG.md to add detailed changes"
-echo "   2. Review changes: git diff"
-echo "   3. Commit: git add package.json CHANGELOG.md && git commit -m 'chore(release): bump version to $NEXT_VERSION'"
-echo "   4. Tag: git tag -a v$NEXT_VERSION -m 'Release v$NEXT_VERSION'"
-echo "   5. Push: git push origin main && git push origin v$NEXT_VERSION"

package/.claude/skills/utility/npm-release/scripts/validate-version-sync.sh

@@ -1,82 +0,0 @@
-#!/usr/bin/env bash
-# Version Sync Validator - Ensures all version markers are consistent
-# Checks: package.json, git tags, CHANGELOG.md
-
-set -euo pipefail
-
-# Colors
-RED='\033[0;31m'
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-NC='\033[0m' # No Color
-
-ERRORS=0
-
-echo "🔍 Validating version synchronization..."
-echo ""
-
-# 1. Extract version from package.json
-if [[ ! -f "package.json" ]]; then
-    echo -e "${RED}❌ package.json not found${NC}"
-    exit 1
-fi
-
-PKG_VERSION=$(grep -o '"version": *"[^"]*"' package.json | grep -o '[0-9]\+\.[0-9]\+\.[0-9]\+')
-echo "📦 package.json version: $PKG_VERSION"
-
-# 2. Check latest git tag
-LATEST_TAG=$(git tag --sort=-v:refname | head -1 || echo "")
-if [[ -z "$LATEST_TAG" ]]; then
-    echo -e "${YELLOW}⚠️  No git tags found${NC}"
-else
-    TAG_VERSION="${LATEST_TAG#v}"  # Remove 'v' prefix
-    echo "🏷️  Latest git tag: $LATEST_TAG ($TAG_VERSION)"
-
-    if [[ "$PKG_VERSION" != "$TAG_VERSION" ]]; then
-        echo -e "${RED}❌ Version mismatch: package.json ($PKG_VERSION) != git tag ($TAG_VERSION)${NC}"
-        ((ERRORS++))
-    else
-        echo -e "${GREEN}✅ package.json and git tag match${NC}"
-    fi
-fi
-
-# 3. Check CHANGELOG.md
-if [[ ! -f "CHANGELOG.md" ]]; then
-    echo -e "${YELLOW}⚠️  CHANGELOG.md not found${NC}"
-else
-    # Extract first version from CHANGELOG (after the header)
-    # macOS grep doesn't support -P, use sed instead
-    CHANGELOG_VERSION=$(sed -n 's/^## \[\([0-9]\+\.[0-9]\+\.[0-9]\+\)\].*/\1/p' CHANGELOG.md | head -1)
-
-    if [[ -z "$CHANGELOG_VERSION" ]]; then
-        echo -e "${YELLOW}⚠️  No version found in CHANGELOG.md${NC}"
-    else
-        echo "📝 CHANGELOG.md latest: $CHANGELOG_VERSION"
-
-        if [[ "$PKG_VERSION" != "$CHANGELOG_VERSION" ]]; then
-            echo -e "${RED}❌ Version mismatch: package.json ($PKG_VERSION) != CHANGELOG.md ($CHANGELOG_VERSION)${NC}"
-            ((ERRORS++))
-        else
-            echo -e "${GREEN}✅ package.json and CHANGELOG.md match${NC}"
-        fi
-    fi
-fi
-
-# 4. Check for version format consistency in git tags
-echo ""
-echo "🔍 Checking git tag format consistency..."
-INCONSISTENT_TAGS=$(git tag | grep -v '^v[0-9]\+\.[0-9]\+\.[0-9]\+$' || true)
-if [[ -n "$INCONSISTENT_TAGS" ]]; then
-    echo -e "${YELLOW}⚠️  Found tags with inconsistent format:${NC}"
-    echo "$INCONSISTENT_TAGS" | sed 's/^/   /'
-    echo -e "${YELLOW}   Expected format: vX.Y.Z (e.g., v4.2.0)${NC}"
-fi
-
-echo ""
-if [[ $ERRORS -eq 0 ]]; then
-    echo -e "${GREEN}✅ All version markers are synchronized${NC}"
-    exit 0
-else
-    echo -e "${RED}❌ Found $ERRORS version synchronization error(s)${NC}"
-    exit 1
-fi

package/.claude/skills/utility/npm-release/scripts/version-decision-tree.sh

@@ -1,44 +0,0 @@
-#!/usr/bin/env bash
-# Version Decision Tree - Semantic Versioning Enforcer
-# Prevents arbitrary version jumps by enforcing SemVer rules
-
-set -euo pipefail
-
-CURRENT_VERSION="${1:-}"
-CHANGE_TYPE="${2:-}"
-
-if [[ -z "$CURRENT_VERSION" || -z "$CHANGE_TYPE" ]]; then
-    echo "Usage: $0 <current-version> <patch|minor|major>"
-    exit 1
-fi
-
-# Parse current version
-if [[ ! "$CURRENT_VERSION" =~ ^([0-9]+)\.([0-9]+)\.([0-9]+)$ ]]; then
-    echo "❌ Invalid version format: $CURRENT_VERSION"
-    echo "   Expected: X.Y.Z (e.g., 4.2.0)"
-    exit 1
-fi
-
-MAJOR="${BASH_REMATCH[1]}"
-MINOR="${BASH_REMATCH[2]}"
-PATCH="${BASH_REMATCH[3]}"
-
-# Calculate next version based on change type
-case "$CHANGE_TYPE" in
-    patch)
-        NEXT_VERSION="$MAJOR.$MINOR.$((PATCH + 1))"
-        ;;
-    minor)
-        NEXT_VERSION="$MAJOR.$((MINOR + 1)).0"
-        ;;
-    major)
-        NEXT_VERSION="$((MAJOR + 1)).0.0"
-        ;;
-    *)
-        echo "❌ Invalid change type: $CHANGE_TYPE"
-        echo "   Expected: patch, minor, or major"
-        exit 1
-        ;;
-esac
-
-echo "$NEXT_VERSION"

package/.claude/skills/verification/SKILL.md

@@ -1,158 +0,0 @@
----
-name: verification-before-completion
-description: "Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always"
----
-
-# Verification Before Completion
-
-## Overview
-
-This skill enforces a critical discipline: **never claim completion without fresh verification evidence**.
-
-The most common failure mode for AI agents is claiming success without actually verifying. This skill prevents that by requiring explicit verification steps before any completion claim.
-
-## The Iron Law
-
-```
-NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
-```
-
-## The Process
-
-### Before ANY Completion Claim
-
-```
-1. IDENTIFY: What command proves this claim?
-   → "Tests pass" requires: npm test / pytest / go test
-   → "Build succeeds" requires: npm run build / make
-   → "Lint clean" requires: npm run lint / eslint
-   → "Type check passes" requires: tsc --noEmit / mypy
-
-2. RUN: Execute the FULL command (fresh, complete)
-   → Not cached results
-   → Not partial output
-   → Not "I ran it earlier"
-
-3. READ: Full output, check exit code, count failures
-   → Exit code 0 = success
-   → Exit code non-zero = failure
-   → Count actual pass/fail numbers
-
-4. VERIFY: Does output confirm the claim?
-   → "All tests pass" = 0 failures in output
-   → "Build succeeds" = no errors, artifacts created
-   → "No lint errors" = 0 problems found
-
-5. ONLY THEN: Make the claim with evidence
-   → Quote the relevant output
-   → Include exit code
-   → Show pass/fail counts
-```
-
-## Verification Commands by Context
-
-### Flow Exit Gates
-
-| Flow | Verification Command | Success Criteria |
-|------|---------------------|------------------|
-| /flow-prd | `validate-constitution --type prd` | Exit 0, no violations |
-| /flow-epic | `validate-constitution --type epic` | Exit 0, no violations |
-| /flow-dev | `npm test && npm run build` | All tests pass, build succeeds |
-| /flow-qa | `npm test && npm run lint` | All pass, no blockers |
-| /flow-release | `gh pr checks` | All checks pass |
-
-### Common Development Tasks
-
-| Claim | Required Verification |
-|-------|----------------------|
-| "Tests pass" | Run full test suite, show output |
-| "Build succeeds" | Run build command, show output |
-| "Lint clean" | Run linter, show 0 errors |
-| "Type check passes" | Run type checker, show output |
-| "No regressions" | Run affected tests, compare before/after |
-| "Bug fixed" | Show failing test → fix → passing test |
-
-## Rationalization Prevention
-
-| Excuse | Reality |
-|--------|---------|
-| "I just ran it" | Run it again. Fresh evidence required. |
-| "It was passing before" | Before ≠ now. Verify current state. |
-| "The change is trivial" | Trivial changes break things. Verify. |
-| "I'm confident it works" | Confidence ≠ evidence. Run the command. |
-| "Tests are slow" | Slow tests > broken production. Run them. |
-| "I'll verify after commit" | Verify BEFORE commit. Always. |
-| "The CI will catch it" | You catch it first. Don't waste CI cycles. |
-| "It's just documentation" | Doc changes can break builds. Verify. |
-
-## Red Flags - STOP
-
-If you find yourself:
-- Saying "should work" without running verification
-- Claiming "tests pass" without showing output
-- Saying "I believe" instead of "I verified"
-- Skipping verification "just this once"
-- Trusting cached or stale results
-
-**STOP. Run the verification command. Show the evidence.**
-
-## Evidence Format
-
-When claiming completion, always include:
-
-```markdown
-## Verification Evidence
-
-**Command**: `npm test`
-**Exit Code**: 0
-**Output Summary**:
-- Tests: 42 passed, 0 failed
-- Coverage: 85%
-- Duration: 12.3s
-
-**Conclusion**: All tests pass. Ready for commit.
-```
-
-## Integration with CC-DevFlow
-
-### Every Flow Exit Gate
-
-```yaml
-Exit Gate Verification:
-  1. Identify required verification commands
-  2. Run each command fresh
-  3. Capture full output
-  4. Verify success criteria met
-  5. Document evidence in EXECUTION_LOG.md
-  6. Only then proceed to next stage
-```
-
-### Task Completion
-
-```yaml
-Task Completion Verification:
-  1. Run task-specific tests
-  2. Verify acceptance criteria met
-  3. Show evidence in task completion message
-  4. Mark task complete only with evidence
-```
-
-## The Discipline
-
-This skill is about **intellectual honesty**. It's easy to believe something works. It's harder to prove it.
-
-The discipline is:
-1. **Assume nothing** - Don't trust memory or intuition
-2. **Verify everything** - Run the actual commands
-3. **Show evidence** - Quote output, not beliefs
-4. **Fresh results only** - No stale or cached data
-
-## Cross-Reference
-
-- Constitution Article I: Quality First (complete implementation)
-- Constitution Article VI: Test-First Development (TDD)
-- rationalization-library.md: Cross-Article rationalizations
-
----
-
-**[PROTOCOL]**: 变更时更新此头部，然后检查 CLAUDE.md