@hanzlaa/rcode 2.1.0

package/rihal/workflows/document-project.md

@@ -0,0 +1,180 @@
+# Workflow: rihal:document-project
+
+<purpose>
+Load documentation-requirements.csv, audit current documentation for coverage and staleness, identify missing or outdated docs, and file them as SPRINT.md subtasks or separate plan phases.
+</purpose>
+
+
+## Step 0 — Usage check
+
+If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
+
+```
+/rihal:document-project <argument-here>
+```
+
+**Examples:**
+```
+/rihal:document-project example 1
+/rihal:document-project example 2
+```
+
+STOP — do not proceed.
+
+<available_agent_types>
+- `rihal-docs-auditor` — documentation compliance auditor
+</available_agent_types>
+
+## Step 0 — Initialize
+
+```bash
+INIT=$(node .rihal/bin/rihal-tools.cjs init document-project "$ARGUMENTS")
+```
+
+Parse:
+- `flags.csv` — path to documentation-requirements.csv (default: `.rihal/documentation-requirements.csv`)
+- `flags.auto_file_tasks` — auto-create SPRINT.md for missing docs (default: false)
+- `csv_path` — resolved CSV path
+- `audit_output_path` — `.rihal/DOCS-AUDIT.md` (output)
+
+## Step 1 — Load or Create Documentation Requirements
+
+**If `csv_path` exists:**
+Load CSV and parse:
+
+```csv
+Document,Required,Priority,Audience,Last Updated,Status
+README.md,yes,high,all,2026-04-01,current
+API.md,yes,high,developers,2026-03-15,stale
+CONTRIBUTING.md,yes,medium,contributors,2026-02-01,missing
+DEPLOYMENT.md,yes,high,devops,2026-04-01,current
+ARCHITECTURE.md,yes,high,architects,2026-01-01,outdated
+```
+
+**If missing:** Create template at `.rihal/documentation-requirements.csv`:
+
+```bash
+cat > .rihal/documentation-requirements.csv << 'EOF'
+Document,Required,Priority,Audience,Last Updated,Status
+README.md,yes,high,all,,
+API.md,yes,high,developers,,
+CONTRIBUTING.md,yes,medium,contributors,,
+DEPLOYMENT.md,yes,high,devops,,
+ARCHITECTURE.md,yes,high,architects,,
+DEVELOPMENT.md,yes,medium,developers,,
+EOF
+```
+
+## Step 2 — Audit Current Documentation
+
+For each row in CSV, check if document exists and assess staleness:
+
+```bash
+for doc in $(cut -d',' -f1 .rihal/documentation-requirements.csv | tail -n +2); do
+  if [ -f "$doc" ]; then
+    MTIME=$(stat -c %Y "$doc")
+    NOW=$(date +%s)
+    AGE_DAYS=$(( ($NOW - $MTIME) / 86400 ))
+    if [ $AGE_DAYS -gt 90 ]; then echo "STALE"; fi
+  else
+    echo "MISSING"
+  fi
+done
+```
+
+## Step 3 — Spawn Docs Auditor
+
+Spawn `rihal-docs-auditor` subagent:
+
+```
+Task tool call:
+  subagent_type: "rihal-docs-auditor"
+  description: "Audit documentation coverage and staleness"
+  prompt: |
+    Audit project documentation against requirements.
+    
+    **Requirements CSV:**
+    {csv_contents}
+    
+    **Audit findings:**
+    {per_doc_status}
+    
+    For each doc, determine:
+    - Status: Missing, Current, Stale (>90 days old), Outdated (references removed features)
+    - Priority: high/medium/low (from CSV)
+    - Estimated effort: 1-4 hours
+    - Who should write: audience from CSV
+    
+    Output format: DOCS-AUDIT.md with:
+    1. Summary table (doc, status, priority, effort)
+    2. Per-doc assessment and recommendations
+    3. Suggested documentation plan
+    
+    Write to: {audit_output_path}
+```
+
+## Step 4 — File Missing Docs as Tasks
+
+**If `flags.auto_file_tasks` is true:**
+
+For each missing or stale doc (status=Missing or Stale):
+
+Create task subtask in state:
+
+```bash
+node .rihal/bin/rihal-tools.cjs state add-task \
+  --title "Write {doc_name}: {purpose}" \
+  --description "Audience: {audience}, Priority: {priority}" \
+  --effort {effort_hours} \
+  --component documentation
+```
+
+Create SPRINT.md if multiple docs needed:
+
+File: `.planning/plans/documentation-updates/SPRINT.md`
+
+```markdown
+# Plan: Documentation Updates
+
+{doc_1_task}
+{doc_2_task}
+...
+```
+
+Print:
+```
+📋 Documentation audit complete: {audit_output_path}
+
+Summary:
+  • {current_count} current
+  • {stale_count} stale (>90 days)
+  • {missing_count} missing
+
+Missing docs filed as tasks. Run:
+
+/rihal:plan .planning/plans/documentation-updates/SPRINT.md
+```
+
+## Step 5 — Auto-inject into Resume-Work
+
+After audit, if resume-work.md exists, prepend to Step 2:
+
+```
+If .rihal/DOCS-AUDIT.md exists, check for missing/stale docs:
+
+@.rihal/DOCS-AUDIT.md
+```
+
+## Success Criteria
+
+- CSV loaded or created
+- All docs in CSV audited for presence/staleness
+- DOCS-AUDIT.md generated with per-doc assessment
+- Missing/stale docs categorized by priority
+- (Optional) Tasks filed in state or SPRINT.md created
+
+## On Error
+
+- If CSV malformed: use template
+- If audit agent fails: provide manual audit template
+- If state write fails: skip task filing, report audit only

package/rihal/workflows/enable-hooks.md

@@ -0,0 +1,102 @@
+# Workflow: rihal:enable-hooks
+
+<purpose>
+Merge Rihal opt-in hooks from settings-hooks.json into .claude/settings.json. Creates settings.json if missing. Enables pre-edit (read-before-edit check), pre-workflow (command hint), and post-commit (format validation) guardrails.
+</purpose>
+
+
+## Step 0 — Usage check
+
+If `$ARGUMENTS` is empty or contains only `--help` or `-h`:
+
+```
+/rihal:enable-hooks <argument-here>
+```
+
+**Examples:**
+```
+/rihal:enable-hooks example 1
+/rihal:enable-hooks example 2
+```
+
+STOP — do not proceed.
+
+## Step 1 — Load hooks template
+
+```bash
+cat .rihal/templates/settings-hooks.json
+```
+
+Parse the JSON. If file does not exist, print error and stop:
+
+```
+Error: .rihal/templates/settings-hooks.json not found. Run 'rihal-code install-v2' to reinstall.
+```
+
+## Step 2 — Load or create settings.json
+
+Check if `.claude/settings.json` exists in the project root.
+
+- **If it exists:** Read and parse it. Merge incoming hooks into the existing `hooks` object (or create if missing).
+- **If it does not exist:** Create a minimal settings.json with the hooks from step 1.
+
+If `.claude/` directory does not exist, create it first.
+
+## Step 3 — Merge hooks
+
+For each hook type (`PreToolUse`, `PostToolUse`):
+
+- If the hook type does not exist in the current settings.json, add it.
+- If it exists, append the new matchers and hook commands (avoid duplicates by checking for exact command matches).
+
+**Duplicate detection:** If a matcher + command pair already exists, skip it.
+
+## Step 4 — Write merged settings.json
+
+Write the merged settings.json back to `.claude/settings.json` with proper JSON formatting (2-space indent).
+
+## Step 5 — Verify hook binary
+
+Verify that the hook binary exists and is executable:
+
+```bash
+if [ ! -f .rihal/bin/rihal-hooks.cjs ]; then
+  echo "⚠ Hook binary missing at .rihal/bin/rihal-hooks.cjs"
+  echo "  Run: node /tmp/rihal-src/cli/install-v2.js . --force --yes"
+  exit 1
+fi
+node .rihal/bin/rihal-hooks.cjs --help 2>&1 || true
+```
+
+If the binary is missing, print error and stop. Otherwise, test it with `--help` (ignore exit code).
+
+## Step 5.5 — Print confirmation
+
+Print success message:
+
+```
+✓ Rihal hooks installed to .claude/settings.json
+
+Enabled guardrails:
+  • pre-edit: Verifies files are Read() before Edit/Write
+  • pre-workflow: Warns if rihal:* commands look suspicious
+  • post-commit: Validates commit format and bans "Generated with Claude" patterns
+
+To disable, remove the hooks section from .claude/settings.json or edit .rihal/templates/settings-hooks.json and re-run.
+```
+
+## Success Criteria
+
+- [ ] `.claude/settings.json` created or updated with hooks merged
+- [ ] No duplicate hook entries in merged settings
+- [ ] File written with valid JSON formatting
+- [ ] Confirmation message printed to user
+
+## On Error
+
+- **Template not found:** print error and stop (Step 1).
+- **`.claude/` directory creation fails:** print error and stop.
+- **state.json missing:** continue without error — hooks installation is standalone.
+- **settings.json has invalid JSON:** print error with path and stop.
+- **Permission denied writing .claude/settings.json:** print error and stop.
+- **Merge produces duplicate hooks:** skip duplicates (Step 3).