docguard-cli 0.5.1

package/templates/commands/docguard.init.md

@@ -0,0 +1,62 @@
+# /docguard.init — Set up CDD documentation for this project
+
+You are an AI agent initializing Canonical-Driven Development (CDD) for a new or existing project using DocGuard.
+
+## Step 1: Initialize Skeleton Files
+
+```bash
+npx docguard init
+```
+
+This creates the folder structure and template files. But the templates are EMPTY — they need real content.
+
+## Step 2: Detect and Configure Project Type
+
+Create `.docguard.json` based on what you find:
+
+```bash
+cat package.json
+```
+
+Determine:
+- `projectType`: "cli" (has `bin` field), "webapp" (has react/next/vue), "api" (has express/fastify), or "library" (default)
+- `needsE2E`: true for webapps, false for CLIs/libraries
+- `needsEnvVars`: true for APIs/webapps with env config, false for CLIs
+- `needsDatabase`: true if database dependencies found
+
+Write `.docguard.json` with these settings.
+
+## Step 3: Write Real Documentation
+
+For each canonical document, generate an AI prompt and write real content:
+
+```bash
+npx docguard fix --doc architecture
+```
+
+Read the output, execute the RESEARCH STEPS, then write the ARCHITECTURE.md with real project content.
+
+Repeat for each document:
+```bash
+npx docguard fix --doc data-model
+npx docguard fix --doc security
+npx docguard fix --doc test-spec
+npx docguard fix --doc environment
+```
+
+## Step 4: Verify Everything
+
+```bash
+npx docguard guard
+npx docguard score
+```
+
+All checks should pass. Report the final score.
+
+## Step 5: Set Up Git Hooks (Optional)
+
+```bash
+npx docguard hooks
+```
+
+This installs pre-commit (guard), pre-push (score), and commit-msg (conventional commits) hooks.

package/templates/commands/docguard.review.md

@@ -0,0 +1,44 @@
+# /docguard.review — Review documentation vs code for drift
+
+You are an AI agent reviewing documentation quality and detecting drift between docs and code.
+
+## Step 1: Run Diff
+
+```bash
+npx docguard diff
+```
+
+Read the output carefully. It shows where documentation no longer matches the codebase.
+
+## Step 2: Run Guard
+
+```bash
+npx docguard guard
+```
+
+Note any failed validators — these indicate docs that need updating.
+
+## Step 3: Check Freshness
+
+For each file listed in the guard output with a freshness warning:
+1. Read the document
+2. Read the related source code
+3. Compare: does the doc accurately describe the current code?
+4. If not, update the doc to match reality
+
+## Step 4: Update Stale Docs
+
+For each stale or drifted document:
+1. Read the relevant source code files
+2. Update the document to match current implementation
+3. Update the `docguard:last-reviewed` date to today
+4. If the change is intentional drift, add an entry to DRIFT-LOG.md
+
+## Step 5: Verify
+
+```bash
+npx docguard guard
+npx docguard score
+```
+
+Report the final results to the user.

package/templates/commands/docguard.update.md

@@ -0,0 +1,44 @@
+# /docguard.update — Update canonical docs after code changes
+
+You are an AI agent that updates documentation to reflect recent code changes.
+
+## Step 1: Identify What Changed
+
+```bash
+git log --oneline -10
+git diff HEAD~5 --stat
+```
+
+Read the recent commits. Understand what code changed and why.
+
+## Step 2: Check Which Docs Are Affected
+
+For each changed file, determine which canonical doc it affects:
+
+| Code Change | Update This Doc |
+|-------------|----------------|
+| New API endpoint or route | ARCHITECTURE.md (component map) |
+| Database schema change | DATA-MODEL.md (entities, fields) |
+| New env variable | ENVIRONMENT.md (env var table) |
+| Auth or permission change | SECURITY.md (auth/RBAC section) |
+| New test or test config | TEST-SPEC.md (test categories) |
+| New dependency added | ARCHITECTURE.md (tech stack) |
+| Major refactoring | ARCHITECTURE.md (layer boundaries, data flow) |
+
+## Step 3: Update Each Affected Doc
+
+For each affected document:
+1. Read the current document
+2. Read the relevant source code changes
+3. Update the specific section that changed
+4. Update the `docguard:last-reviewed` date to today
+5. Add entry to CHANGELOG.md under [Unreleased]
+
+## Step 4: Verify
+
+```bash
+npx docguard guard
+npx docguard score
+```
+
+All checks should pass. Report the changes made.