@orderful/droid 0.26.0 → 0.27.0

package/dist/tools/code-review/skills/code-review/SKILL.md

@@ -0,0 +1,154 @@
+---
+name: code-review
+description: "Comprehensive code review using specialized agents. Use when reviewing PRs, checking staged changes, or analysing code quality. User prompts like 'review this PR', 'check my changes', 'review before I commit'."
+globs:
+  - "**/*"
+alwaysApply: false
+allowed-tools: [Read, Grep, Glob, Bash, Task]
+---
+
+# Code Review Skill
+
+Run comprehensive code reviews using specialized agents, each focused on a specific concern.
+
+## How It Works
+
+The `/code-review` command orchestrates multiple specialized agents in parallel:
+
+1. **edi-standards-reviewer** - EDI patterns, partnership handling, billing concerns
+2. **test-coverage-analyzer** - Test completeness and edge cases
+3. **error-handling-reviewer** - Silent failures, missing error handling
+4. **type-reviewer** - TypeScript type design, interface contracts
+
+Each agent returns issues with confidence scores (0-100). Issues below 80% confidence are filtered out to reduce noise.
+
+## Usage
+
+```bash
+/code-review #123           # Review PR #123
+/code-review staged         # Review staged changes
+/code-review branch         # Review current branch vs main
+/code-review path/to/file   # Review specific file
+```
+
+## Output Format
+
+Reviews are presented in prioritized categories:
+
+🔴 **Critical** - Security, data loss, billing errors
+🟠 **Important** - Bugs, missing tests, type issues
+🟡 **Suggestions** - Style, readability improvements
+
+## Post-Review Actions
+
+After presenting findings, you can:
+
+- Post the review as a PR comment
+- Get suggested fixes for specific issues
+- Check out the branch and fix critical issues
+
+## Domain-Aware Reviews
+
+The EDI Standards Reviewer discovers project conventions by reading:
+
+- `.claude/CLAUDE.md` or `CLAUDE.md` for team conventions
+- `AGENTS.md` or `docs/` for architecture guidance
+
+This lets it apply your project's specific patterns rather than generic rules.
+
+## Review Procedure
+
+### Step 0: Check for Brain Integration
+
+**If the `brain` skill is installed** (check for `~/.claude/skills/brain/SKILL.md` or `~/.config/opencode/skills/brain/SKILL.md`):
+
+Ask the user: **"Would you like the review results saved to a `/brain review` doc?"**
+
+- If yes: Create a brain review doc at the start using `/brain review {PR title or branch name}`
+- The final report will be written to the brain doc instead of just displayed
+- This allows for async discussion via `@droid`/`@{user}` comments
+
+If brain skill is not installed or user declines, proceed with normal terminal output.
+
+### Step 1: Determine Review Scope
+
+Parse the argument to determine what to review:
+
+**If argument starts with `#` or is a number (e.g., `#123` or `123`):**
+
+- This is a PR number
+- Fetch PR details: `gh pr view $PR_NUMBER --json title,body,baseRefName,headRefName,files`
+- Get the diff: `gh pr diff $PR_NUMBER`
+- Note the PR author and description for context
+
+**If argument is `staged` or empty:**
+
+- Review staged changes: `git diff --cached`
+
+**If argument is `branch`:**
+
+- Review current branch vs main: `git diff origin/main...HEAD`
+
+**If argument is a file path:**
+
+- Review specific file: `git diff HEAD -- $FILE_PATH`
+- If no changes, review the entire file for issues
+
+### Step 2: Gather Context
+
+For PR reviews, also fetch:
+
+- PR description (may contain context about the change)
+- Linked issues: `gh pr view $PR_NUMBER --json body` and parse for #issue refs
+- Changed files list for targeted agent assignment
+
+### Step 3: Parallel Agent Reviews
+
+Launch these agents in parallel using the Task tool with `run_in_background: true`:
+
+1. **edi-standards-reviewer**: EDI patterns, partnership handling, billing concerns
+2. **test-coverage-analyzer**: Test completeness and edge cases
+3. **error-handling-reviewer**: Silent failures, missing error handling
+4. **type-reviewer**: Type design, interface contracts
+
+Pass each agent:
+
+1. The diff content
+2. The full file content for changed files (for context)
+3. PR description if available
+
+Use TaskOutput to collect results from all agents.
+
+### Step 4: Confidence Filtering
+
+Each agent returns issues with confidence scores (0-100).
+Filter out issues with confidence < 80.
+
+### Step 5: Synthesize Report
+
+Compile findings into a prioritized report:
+
+**PR #123: "Add partnership billing events"** (if reviewing a PR)
+_Author: @username_
+
+**Critical** (security, data loss, billing errors)
+
+- `file.ts:42` - Issue description
+
+**Important** (bugs, missing tests, type issues)
+
+- `file.ts:67` - Issue description
+
+**Suggestions** (style, readability)
+
+- `file.ts:89` - Issue description
+
+**Summary**: X critical, Y important, Z suggestions across N files.
+
+### Step 6: Offer Actions (for PRs)
+
+After presenting the report, offer:
+
+- "Would you like me to post this as a PR comment?"
+- "Should I suggest fixes for any of these issues?"
+- "Want me to check out this branch and fix the critical issues?"

package/dist/tools/codex/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "droid-codex",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "Shared organizational knowledge - PRDs, tech designs, domains, proposals, patterns, and explored topics. Use when loading project context, searching codex, capturing decisions, or creating new entries.",
   "author": {
     "name": "Orderful",

package/dist/tools/codex/TOOL.yaml

@@ -1,14 +1,15 @@
 name: codex
 description: "Shared organizational knowledge - PRDs, tech designs, domains, proposals, patterns, and explored topics. Use when loading project context, searching codex, capturing decisions, or creating new entries."
-version: 0.1.5
+version: 0.1.6
 status: beta
 
 includes:
   skills:
-    - name: droid-codex
+    - name: codex
       required: true
   commands:
-    - codex
+    - name: codex
+      is_alias: false
   agents:
     - codex-document-processor
 

package/dist/tools/codex/commands/codex.md

@@ -1,78 +1,31 @@
 ---
-description: Shared organizational knowledge - PRDs, tech designs, patterns, domains, proposals, and explored topics
+name: codex
+description: "Shared organizational knowledge - PRDs, tech designs, patterns, domains, proposals, and explored topics"
 argument-hint: "[projects | domains | proposals | patterns | topics | {name} | search {query} | new {type} {name} | decision {text}]"
-allowed-tools: [Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(git:*), Bash(ls:*), Bash(mkdir:*)]
 ---
 
 # /codex
 
-Entry point for shared organizational knowledge. See the **codex skill** for full behaviour.
+**User invoked:** `/codex $ARGUMENTS`
 
-> Context is AI's multiplier. This is Orderful's.
-
-## Arguments
-
-$ARGUMENTS
-
-## Prerequisites
-
-Before first use, verify:
-
-1. **Repo cloned** at configured `codex_repo` path
-2. **gh CLI** installed and authenticated
-
-## Usage
-
-```bash
-/codex                           # Show categories (5 total)
-/codex projects                  # List projects
-/codex domains                   # List domains
-/codex proposals                 # List proposals
-/codex patterns                  # List patterns
-/codex topics                    # List topics
-/codex {name}                    # Load entry (searches all categories)
-/codex search {query}            # Search across everything
-/codex new {name}                # Scaffold new project (shorthand)
-/codex new project {name}        # Scaffold new project from templates
-/codex new domain {name}         # Scaffold new domain entry
-/codex new proposal {name}       # Scaffold new proposal entry
-/codex new pattern {name}        # Scaffold new pattern entry
-/codex new topic {name}          # Scaffold new topic entry
-/codex decision {text}           # Append to active project's DECISIONS.md
-/codex snapshot {type} {file} {name}  # Import PDF/markdown to codex
-/codex artifact {file} {project}      # Add supporting artifact to project
-```
-
-## Configuration
-
-**ALWAYS read `~/.droid/skills/codex/overrides.yaml` first.**
-
-- `codex_repo` - Path to local orderful-codex repository (required)
-- `freshness_days` - Days before showing staleness warning (default: 30)
-
-## Behaviour
-
-Refer to the codex skill for:
-- **Loading**: How to search, handle matches, check freshness, auto-generate CONTEXT.md
-- **Decisions**: How to append to active project's DECISIONS.md
-- **Creating**: How to scaffold new entries (projects, domains, proposals, patterns, topics)
-
-The skill's `references/` folder contains detailed procedures for each workflow.
+**Your task:** Invoke the **codex skill** with these arguments.
 
 ## Examples
 
-```bash
-# Load project context
-/codex transaction-templates
-
-# Search for webhook-related content
-/codex search webhook
+- `/codex projects` → List all projects in the codex
+- `/codex transaction-templates` → Load the transaction-templates entry
+- `/codex search webhook` → Search for "webhook" across all codex content
+- `/codex new project billing-v2` → Create new project scaffolding
+- `/codex decision "Use PostgreSQL for audit log"` → Append decision to active project
 
-# Capture a decision during implementation
-/codex decision "Using UUIDv7 for IDs because it's sortable and includes timestamp"
+## Quick Reference
 
-# Create new entries
-/codex new domain partnerships
-/codex new proposal caching-layer
-/codex new topic organization-hierarchy
 ```
+/codex                      # Show categories overview
+/codex {name}               # Load entry (searches all categories)
+/codex search {query}       # Search across everything
+/codex new project {name}   # Scaffold new project
+/codex decision {text}      # Append to active project's DECISIONS.md
+```
+
+See the **codex skill** for complete documentation and procedures.

package/dist/tools/codex/skills/{droid-codex → codex}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: droid-codex
+name: codex
 description: "Shared organizational knowledge - PRDs, tech designs, patterns, and explored topics. Use when loading project context ('load transaction-templates'), searching codex ('search webhook'), capturing decisions ('codex decision'), or adding explored topics ('add topic'). User prompts like 'check the codex', 'what's in the codex about X', 'load the PRD for Y'."
 globs:
   - "**/PRD.md"
@@ -7,7 +7,18 @@ globs:
   - "**/CONTEXT.md"
   - "**/DECISIONS.md"
 alwaysApply: false
-allowed-tools: [Read, Write, Edit, Glob, Grep, Bash(gh:*), Bash(git:*), Bash(ls:*), Bash(mkdir:*)]
+allowed-tools:
+  [
+    Read,
+    Write,
+    Edit,
+    Glob,
+    Grep,
+    Bash(gh:*),
+    Bash(git:*),
+    Bash(ls:*),
+    Bash(mkdir:*),
+  ]
 ---
 
 # Codex Skill
@@ -32,6 +43,7 @@ gh --version
 ```
 
 If prerequisites fail, guide user to fix:
+
 - Repo missing: `git clone git@github.com:orderful/orderful-codex.git {path}`
 - gh missing: `brew install gh && gh auth login`
 
@@ -43,16 +55,16 @@ If prerequisites fail, guide user to fix:
 
 The codex skill includes three git scripts. **Always use these instead of raw git commands.**
 
-| Script | Purpose | When to use |
-|--------|---------|-------------|
-| `git-preamble` | Ensure clean main + pull latest | Before ANY operation |
-| `git-start-write` | Preamble + create branch | Before write operations |
-| `git-finish-write` | Commit + PR + return to main | After write operations |
+| Script             | Purpose                         | When to use             |
+| ------------------ | ------------------------------- | ----------------------- |
+| `git-preamble`     | Ensure clean main + pull latest | Before ANY operation    |
+| `git-start-write`  | Preamble + create branch        | Before write operations |
+| `git-finish-write` | Commit + PR + return to main    | After write operations  |
 
 ### Read Operations (search, load, list)
 
 ```bash
-droid config codex | droid exec droid-codex git-preamble --config -
+droid config codex | droid exec codex git-preamble --config -
 # Then proceed with the read
 ```
 
@@ -60,12 +72,12 @@ droid config codex | droid exec droid-codex git-preamble --config -
 
 ```bash
 # 1. Start write (runs preamble + creates branch)
-droid config codex | droid exec droid-codex git-start-write --config - --branch codex/{action}-{name}
+droid config codex | droid exec codex git-start-write --config - --branch codex/{action}-{name}
 
 # 2. Make your changes (write files)
 
 # 3. Finish write (commit + PR + return to main)
-droid config codex | droid exec droid-codex git-finish-write --config - \
+droid config codex | droid exec codex git-finish-write --config - \
   --message "{commit message}" \
   --pr-title "{PR title}" \
   --pr-body "{PR description}"
@@ -76,11 +88,13 @@ The scripts return JSON with success/failure status. Check the result before pro
 ### Error Handling
 
 The scripts handle errors internally:
+
 - Silent recovery for transient issues
 - Clear error messages in JSON output
 - Automatic return to main even on partial failure
 
 If a script fails, check the JSON `error` field and report a user-friendly message:
+
 - "I hit a sync issue with the codex. Let me try again..."
 - Only escalate as last resort: "The codex repo needs manual attention."
 
@@ -134,44 +148,44 @@ fi
 
 **ALWAYS read `~/.droid/skills/codex/overrides.yaml` first.**
 
-| Setting | Default | Description |
-|---------|---------|-------------|
-| `codex_repo` | `~/src/github.com/orderful-codex` | Path to local codex repo |
-| `freshness_days` | `30` | Days before staleness warning |
+| Setting          | Default                           | Description                   |
+| ---------------- | --------------------------------- | ----------------------------- |
+| `codex_repo`     | `~/src/github.com/orderful-codex` | Path to local codex repo      |
+| `freshness_days` | `30`                              | Days before staleness warning |
 
 ## Categories
 
 The codex has five categories:
 
-| Category | Path | Purpose |
-|----------|------|---------|
-| `projects` | `{codex_repo}/projects/` | Feature/project context (PRD, tech design, decisions) |
-| `domains` | `{codex_repo}/domains/` | Business domain knowledge - the "what" and "why" |
-| `proposals` | `{codex_repo}/proposals/` | Ideas and future direction - not yet committed |
-| `patterns` | `{codex_repo}/patterns/` | Cross-cutting technical patterns |
-| `topics` | `{codex_repo}/topics/` | Explored codebase areas with freshness tracking |
+| Category    | Path                      | Purpose                                               |
+| ----------- | ------------------------- | ----------------------------------------------------- |
+| `projects`  | `{codex_repo}/projects/`  | Feature/project context (PRD, tech design, decisions) |
+| `domains`   | `{codex_repo}/domains/`   | Business domain knowledge - the "what" and "why"      |
+| `proposals` | `{codex_repo}/proposals/` | Ideas and future direction - not yet committed        |
+| `patterns`  | `{codex_repo}/patterns/`  | Cross-cutting technical patterns                      |
+| `topics`    | `{codex_repo}/topics/`    | Explored codebase areas with freshness tracking       |
 
 ## Commands
 
-| Command | Action |
-|---------|--------|
-| `/codex` | Show categories overview |
-| `/codex projects` | List all projects |
-| `/codex domains` | List all domains |
-| `/codex proposals` | List all proposals |
-| `/codex patterns` | List all patterns |
-| `/codex topics` | List all topics |
-| `/codex {name}` | Load entry (searches all categories) |
-| `/codex search {query}` | Search across everything |
-| `/codex new {name}` | Scaffold new project (shorthand) |
-| `/codex new project {name}` | Scaffold new project from templates |
-| `/codex new domain {name}` | Scaffold new domain entry |
-| `/codex new proposal {name}` | Scaffold new proposal entry |
-| `/codex new pattern {name}` | Scaffold new pattern entry |
-| `/codex new topic {name}` | Scaffold new topic entry |
-| `/codex decision {text}` | Append to active project's DECISIONS.md |
-| `/codex snapshot {type} {file} {name}` | Import PDF/markdown to codex (uses agent) |
-| `/codex artifact {file} {project}` | Add supporting artifact to project (uses agent) |
+| Command                                | Action                                          |
+| -------------------------------------- | ----------------------------------------------- |
+| `/codex`                               | Show categories overview                        |
+| `/codex projects`                      | List all projects                               |
+| `/codex domains`                       | List all domains                                |
+| `/codex proposals`                     | List all proposals                              |
+| `/codex patterns`                      | List all patterns                               |
+| `/codex topics`                        | List all topics                                 |
+| `/codex {name}`                        | Load entry (searches all categories)            |
+| `/codex search {query}`                | Search across everything                        |
+| `/codex new {name}`                    | Scaffold new project (shorthand)                |
+| `/codex new project {name}`            | Scaffold new project from templates             |
+| `/codex new domain {name}`             | Scaffold new domain entry                       |
+| `/codex new proposal {name}`           | Scaffold new proposal entry                     |
+| `/codex new pattern {name}`            | Scaffold new pattern entry                      |
+| `/codex new topic {name}`              | Scaffold new topic entry                        |
+| `/codex decision {text}`               | Append to active project's DECISIONS.md         |
+| `/codex snapshot {type} {file} {name}` | Import PDF/markdown to codex (uses agent)       |
+| `/codex artifact {file} {project}`     | Add supporting artifact to project (uses agent) |
 
 ## Loading an Entry
 
@@ -181,7 +195,7 @@ The codex has five categories:
 
 1. **Run preamble first:**
    ```bash
-   droid config codex | droid exec droid-codex git-preamble --config -
+   droid config codex | droid exec codex git-preamble --config -
    ```
 2. **Read `{codex_repo}/index.yaml`** - this contains all entry names and aliases for fast lookup
 3. Match `{name}` against index keys and aliases (case-insensitive, partial match)
@@ -199,10 +213,11 @@ The codex has five categories:
 **Progressive disclosure:** CONTEXT.md is the first layer - a synthesised summary (~2KB) that handles most queries. Only load full PRD/TECH-DESIGN/DECISIONS files when deeper detail is explicitly needed. This avoids loading 30KB+ of docs for simple context questions.
 
 **If no CONTEXT.md exists for a project:**
-- Spawn background agent to synthesise (non-blocking)
-- Immediately ask user which file to load - don't make them wait
-- Background agent: reads PRD.md + TECH-DESIGN.md + DECISIONS.md, synthesises, creates PR
-- Notify user when complete: "CONTEXT.md ready - PR #{number}"
+
+- Synthesise one from PRD.md + TECH-DESIGN.md + DECISIONS.md
+- Create branch, commit CONTEXT.md, open PR
+- Output the new CONTEXT.md with "need more detail?" options
+- **OPTIONAL:** You may use a background agent (Task tool with `run_in_background: true`) to avoid blocking the user, but synchronous generation is fine too
 
 Full procedure: `references/loading.md`
 
@@ -225,6 +240,7 @@ codebase_paths:
 ```
 
 **Status values (unified across all categories):**
+
 - `draft` - Initial capture, not ready for consumption
 - `active` - Current, being used for implementation
 - `complete` - Project shipped, kept for reference
@@ -316,6 +332,7 @@ The main conversation handles: git branch, commit, PR creation, user interaction
 **Trigger:** `/codex artifact {file} {project}` or user wants to add supporting material to a project
 
 Artifacts are supplementary documents that support a project but aren't core document types (PRD, TECH-DESIGN, DECISIONS). Examples:
+
 - Customer interviews / transcripts
 - Research notes
 - Meeting summaries
@@ -409,6 +426,7 @@ The codex holds **shared** organizational knowledge. The `/project` skill holds
 ```
 
 When user runs `/project create --from codex:{name}`:
+
 1. Load the codex entry
 2. Extract key context for personal PROJECT.md
 3. Create project in user's projects_dir
@@ -418,6 +436,7 @@ When user runs `/project create --from codex:{name}`:
 **See "Git Hygiene (CRITICAL)" section above.** All codex changes go through PRs (main branch is protected).
 
 **Key points:**
+
 - Always run the preamble before any operation (ensures clean main + latest)
 - Write operations: branch → commit → PR → **return to main**
 - Safe changes (new files, decision appends) auto-merge via GitHub Action