Step: Update README, Style Guide, and User Guide to reflect /review and reviewer agent

Author: apiad

.gemini/style-guide.md

@@ -1,6 +1,6 @@
 # Gemini CLI Style Guide
 
-This guide defines the authoritative technical and narrative style for all project documentation, articles, and reports. The `/revise` command and the `editor` subagent use these rules to perform structured, step-by-step audits.
+This guide defines the authoritative technical and narrative style for all project documentation, articles, and reports. The `/review` command and the `reviewer` subagent use these rules to perform structured, multi-phase, non-destructive audits.
 
 ## General Context
 - **Tone:** Intellectual but accessible. Conversational academic style.

README.md

@@ -74,7 +74,7 @@ The `.gemini/commands/` directory defines specialized workflows that automate ev
 
 ### 🧹 Phase 3: Content Generation, Maintenance & Documentation
 *   **`/draft`**: Multi-phase workflow to turn research and plans into detailed, high-quality technical documents or articles section-by-section.
-*   **`/revise`**: Uses the `editor` subagent to perform structural and linguistic audits based on the project's style guide.
+*   **`/review`**: Uses the `reviewer` subagent to perform non-destructive, multi-phase structural and linguistic audits based on the project's style guide.
 *   **`/maintenance`**: Performs a deep scan of the codebase to identify technical debt, refactoring opportunities, and areas to improve test coverage.
 *   **`/document`**: Analyzes the codebase and journals to generate or update comprehensive project documentation in the `docs/` folder.
 *   **`/cron`**: Manages repetitive background tasks (e.g., health checks, automated reports) using **systemd user timers**.
@@ -104,7 +104,7 @@ This framework shines when you combine these commands into cohesive workflows:
 ### 3️⃣ Content Creation Workflow
 1.  **Research:** Use `/research` to gather data into an executive report.
 2.  **Draft:** Run `/draft` to build an outline and expand it into a full article.
-3.  **Revise:** Use `/revise` for step-by-step style guide-driven audits and refinements.
+3.  **Review:** Use `/review` for non-destructive, multi-phase audits and refinements.
 
 ## ⚓ The Hook System
 

docs/user-guide.md

@@ -158,6 +158,31 @@ This tool automatically:
 
 By following this discipline, you ensure that the AI agent always has an up-to-date "long-term memory" to draw from in future sessions.
 
+---
+
+## ✍️ The Content Creation Workflow
+
+Beyond code, this framework excels at generating high-quality technical content through a principled, multi-stage pipeline.
+
+### `/draft`
+
+Your primary tool for long-form technical writing.
+
+- **How it works:** Instead of generating a single large blob of text, the `/draft` command follows a strict 6-phase workflow: Context Gathering (from `research/` or `plans/`), Title & Metadata Selection, Outline Creation (aligned with the Style Guide), Initialization of the file, Section-by-Section Drafting (using the `reporter` subagent), and finally, a Conclusion with next steps.
+- **Why it works:** It forces structural integrity and prevents the "AI-ish" monotone by building the document incrementally based on project-specific research.
+
+### `/review`
+
+Your tool for deep, multi-phase editorial audits.
+
+- **How it works:** Replaces the legacy `/revise` command with a non-destructive, evidence-based reporting workflow. It uses the `reviewer` subagent to audit a file in three distinct phases:
+    1.  **Structural Audit:** Narrative arc and header hierarchy.
+    2.  **Substance Audit:** Concreteness and technical depth.
+    3.  **Linguistic Audit:** Removing "AI-isms" and polishing the prose.
+- **Why it works:** It produces a sidecar `<filename>.review.md` report instead of modifying the original file, allowing you to choose which suggestions to apply during the next `/draft` or `/task work` iteration.
+
+---
+
 ## ⚙️ Background Tasks & Maintenance
 
 

journal/2026-03-23.md

@@ -3,3 +3,4 @@
 [2026-03-23T05:47:57] - Update reviewer agent with grep_search and phase-based workflow.
 [2026-03-23T05:48:29] - Update /review command with multi-phase audit workflow and sidecar reporting.
 [2026-03-23T05:48:51] - Update /draft command to suggest /review instead of /revise.
+[2026-03-23T05:50:16] - Update README, Style Guide, and User Guide to reflect /review and reviewer agent.

tests/test_review_command.py

@@ -31,6 +31,16 @@ def test_draft_command_suggests_review():
     assert "/review" in content
     assert "/revise" not in content
 
+def test_docs_updated():
+    files_to_check = ["README.md", ".gemini/style-guide.md", "docs/user-guide.md"]
+    for f_path in files_to_check:
+        with open(f_path, "r") as f:
+            content = f.read()
+        assert "review" in content.lower()
+        assert "reviewer" in content.lower()
+        # "revise" might still exist in old context but should be gone from descriptions
+        # "editor" might still exist but "reviewer" should be the primary agent name now
+
 if __name__ == "__main__":
     # Simple manual runner for now
     try:
@@ -41,6 +51,7 @@ def test_draft_command_suggests_review():
         test_reviewer_agent_has_grep_search()
         test_review_command_is_multiphase()
         test_draft_command_suggests_review()
+        test_docs_updated()
         print("Tests Passed")
     except AssertionError as e:
         print(f"Test Failed: {e}")