davenov-cc 1.0.9 → 1.0.10

package/README.md

@@ -8,6 +8,7 @@ A personal collection of Claude Code customizations including skills and slash c
 
 Slash commands that can be invoked with `/<command-name>`:
 
+- **davenov:cc:changelog** - Initialize or manage a CHANGELOG.md following Keep a Changelog format
 - **davenov:cc:interview** - Interview mode for expanding specifications
 - **davenov:cc:rule** - Create or modify Claude Code rules
 

package/bin/cli.js

@@ -11,6 +11,7 @@ const SOURCE_DIR = path.join(__dirname, "..");
 // Parse command line arguments
 const args = process.argv.slice(2);
 const AUTO_OVERRIDE = args.includes("--auto-override");
+const UPDATE = args.includes("--update");
 const UNINSTALL = args.includes("--uninstall");
 
 // Directories to install/uninstall
@@ -145,7 +146,11 @@ async function uninstall(rl) {
 }
 
 async function install(rl) {
-  console.log("\n✨ Davenov CC Collection\n");
+  if (UPDATE) {
+    console.log("\n🔄 Updating Davenov CC Collection...\n");
+  } else {
+    console.log("\n✨ Davenov CC Collection\n");
+  }
 
   // Check what we have to install
   const available = CUSTOMIZATION_DIRS.filter((dir) =>
@@ -168,26 +173,25 @@ async function install(rl) {
   // Check for actual file conflicts (not just directory existence)
   const itemsToOverwrite = getItemsToOverwrite();
 
-  if (itemsToOverwrite.length > 0) {
+  // Skip confirmation if updating or auto-override is enabled
+  const skipConfirmation = UPDATE || AUTO_OVERRIDE;
+
+  if (itemsToOverwrite.length > 0 && !skipConfirmation) {
     console.log("⚠️  Heads up! These will be overwritten:");
     for (const { dir, item } of itemsToOverwrite) {
       console.log(`   ${dir}/${item}`);
     }
     console.log();
 
-    if (AUTO_OVERRIDE) {
-      console.log("Auto-override enabled, let's go...");
-    } else {
-      const answer = await prompt(
-        rl,
-        "Cool with that? (y/N): "
-      );
-
-      if (answer.toLowerCase() !== "y") {
-        console.log("\nNo worries, nothing changed. Catch you later! 👋");
-        rl.close();
-        process.exit(0);
-      }
+    const answer = await prompt(
+      rl,
+      "Cool with that? (y/N): "
+    );
+
+    if (answer.toLowerCase() !== "y") {
+      console.log("\nNo worries, nothing changed. Catch you later! 👋");
+      rl.close();
+      process.exit(0);
     }
   }
 
@@ -197,7 +201,11 @@ async function install(rl) {
   }
 
   // Install each directory
-  console.log("Installing the good stuff...\n");
+  if (UPDATE) {
+    console.log("Syncing latest files...\n");
+  } else {
+    console.log("Installing the good stuff...\n");
+  }
 
   for (const dir of available) {
     const srcPath = path.join(SOURCE_DIR, dir);
@@ -207,7 +215,11 @@ async function install(rl) {
     copyRecursive(srcPath, destPath);
   }
 
-  console.log("\n🚀 You're all set! Go build something!\n");
+  if (UPDATE) {
+    console.log("\n✅ Updated to the latest version!\n");
+  } else {
+    console.log("\n🚀 You're all set! Go build something!\n");
+  }
 }
 
 async function main() {

package/commands/davenov:cc:changelog.md

@@ -0,0 +1,222 @@
+---
+description: Initialize or manage a CHANGELOG.md following Keep a Changelog format
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - AskUserQuestion
+---
+
+# Changelog Management Command
+
+Initialize and manage a CHANGELOG.md file following the [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) specification.
+
+## Workflow
+
+### Step 1: Detect Current State
+
+Check if CHANGELOG.md already exists:
+
+```bash
+ls -la CHANGELOG.md 2>/dev/null || echo "NO_CHANGELOG"
+```
+
+Also check for existing CLAUDE.md:
+
+```bash
+ls -la CLAUDE.md 2>/dev/null || echo "NO_CLAUDE_MD"
+```
+
+### Step 2: Handle Existing Changelog
+
+**If CHANGELOG.md exists:**
+
+Use AskUserQuestion:
+- header: "Action"
+- question: "A CHANGELOG.md already exists. What would you like to do?"
+- options:
+  - "View current state" — Show the changelog and [Unreleased] section
+  - "Prepare for release" — Move [Unreleased] entries to a new version
+  - "Add entry" — Add a new entry to [Unreleased]
+  - "Replace entirely" — Create fresh CHANGELOG.md (destructive)
+
+**If CHANGELOG.md does not exist:** Proceed to Step 3.
+
+### Step 3: Gather Project Info
+
+If creating a new changelog, gather:
+
+1. **Repository URL** — Try to detect from git:
+   ```bash
+   git remote get-url origin 2>/dev/null | sed 's/\.git$//' | sed 's/git@github.com:/https:\/\/github.com\//'
+   ```
+
+2. **Current version** — Try to detect from package.json or ask:
+   ```bash
+   node -p "require('./package.json').version" 2>/dev/null || echo "0.1.0"
+   ```
+
+If auto-detection fails, use AskUserQuestion to gather missing info.
+
+### Step 4: Create CHANGELOG.md
+
+Create the changelog following Keep a Changelog format:
+
+```markdown
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+<!--
+Add changes here as you work. Use these categories:
+### Added - New features
+### Changed - Changes to existing functionality
+### Deprecated - Features marked for removal
+### Removed - Deleted features
+### Fixed - Bug fixes
+### Security - Vulnerability fixes
+-->
+
+## [VERSION] - YYYY-MM-DD
+
+### Added
+
+- Initial release
+
+[Unreleased]: REPO_URL/compare/vVERSION...HEAD
+[VERSION]: REPO_URL/releases/tag/vVERSION
+```
+
+Replace `VERSION`, `YYYY-MM-DD`, and `REPO_URL` with actual values.
+
+### Step 5: Update CLAUDE.md
+
+Check if CLAUDE.md contains changelog instructions:
+
+```bash
+grep -l "Changelog Management" CLAUDE.md 2>/dev/null || echo "NO_CHANGELOG_SECTION"
+```
+
+**If no changelog section exists**, ask user if they want to add changelog workflow to CLAUDE.md:
+
+Use AskUserQuestion:
+- header: "CLAUDE.md"
+- question: "Should I add changelog management instructions to CLAUDE.md?"
+- options:
+  - "Yes (Recommended)" — Add instructions for maintaining the changelog
+  - "No" — Skip, I'll manage it manually
+
+**If user agrees**, add this section to CLAUDE.md:
+
+```markdown
+## Changelog Management
+
+**Keep the CHANGELOG.md updated** following [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) format.
+
+### During Development
+
+When making changes, add entries to the `[Unreleased]` section using the appropriate category:
+
+- **Added** — New features
+- **Changed** — Changes to existing functionality
+- **Deprecated** — Features marked for removal
+- **Removed** — Deleted features
+- **Fixed** — Bug fixes
+- **Security** — Vulnerability fixes
+
+### Before Releasing a New Version
+
+1. Review commits since last version:
+   ```bash
+   git log $(git describe --tags --abbrev=0)..HEAD --oneline
+   ```
+
+2. Ensure all notable changes are captured in `[Unreleased]`
+
+3. Move `[Unreleased]` entries to a new version section:
+   - Create new heading: `## [X.Y.Z] - YYYY-MM-DD`
+   - Use today's date in ISO 8601 format
+   - Move all category sections under the new version
+
+4. Update comparison links at the bottom of CHANGELOG.md:
+   - Add new version link
+   - Update `[Unreleased]` link to compare from new version
+
+5. Commit the changelog update with version bump
+```
+
+### Step 6: "Add Entry" Flow
+
+If user selected "Add entry":
+
+1. Use AskUserQuestion:
+   - header: "Category"
+   - question: "What type of change is this?"
+   - options:
+     - "Added" — New feature
+     - "Changed" — Modified existing functionality
+     - "Fixed" — Bug fix
+     - "Removed" — Deleted feature
+
+2. Use AskUserQuestion:
+   - header: "Description"
+   - question: "Describe the change in one line (imperative mood, e.g., 'Add user authentication')"
+   - Allow free text via "Other" option
+
+3. Add the entry to the appropriate section under `[Unreleased]`, creating the category heading if needed.
+
+### Step 7: "Prepare for Release" Flow
+
+If user selected "Prepare for release":
+
+1. Show current `[Unreleased]` contents
+
+2. If empty, warn: "No unreleased changes found. Add entries first."
+
+3. Use AskUserQuestion:
+   - header: "Version"
+   - question: "What version number should this release be?"
+   - options:
+     - "Patch (x.y.Z)" — Bug fixes, minor changes
+     - "Minor (x.Y.0)" — New features, backwards compatible
+     - "Major (X.0.0)" — Breaking changes
+
+4. Calculate new version number based on selection and current version
+
+5. Move `[Unreleased]` content to new version section with today's date
+
+6. Update comparison links at bottom of file
+
+7. Clear `[Unreleased]` section (keep heading and comment)
+
+## Output
+
+Report what was created/modified:
+
+```
+Changelog: [created | updated]
+- Path: ./CHANGELOG.md
+- Current version: X.Y.Z
+- Unreleased changes: [count] entries
+
+CLAUDE.md: [updated | unchanged]
+- Changelog instructions: [added | already present | skipped]
+```
+
+## Key Principles (Keep a Changelog)
+
+1. **For humans, not machines** — Write clear, readable entries
+2. **One entry per version** — Group changes by release
+3. **Newest first** — Latest version at top
+4. **ISO 8601 dates** — Use YYYY-MM-DD format
+5. **Linkable** — Version headers link to diffs
+6. **Track unreleased** — Always maintain [Unreleased] section
+7. **Use standard categories** — Added, Changed, Deprecated, Removed, Fixed, Security

package/commands/davenov:cc:update.md

@@ -10,12 +10,13 @@ This command updates the **davenov-cc** npm package — a collection of Claude C
 
 ## Instructions
 
-Run the npx command to fetch and install the latest version:
+Run the npx command with the `--update` flag to fetch and install the latest version:
 
 ```bash
-npx davenov-cc@latest
+npx davenov-cc@latest --update
 ```
 
-The `@latest` tag ensures npm fetches the newest version, bypassing any cached versions.
+- The `@latest` tag ensures npm fetches the newest version, bypassing any cached versions
+- The `--update` flag skips confirmation prompts since we're updating existing files
 
 Report the results to the user.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "davenov-cc",
-  "version": "1.0.9",
+  "version": "1.0.10",
   "description": "Claude Code customizations - skills and slash commands for enhanced AI-assisted development",
   "bin": {
     "davenov-cc": "./bin/cli.js"