@hivehub/rulebook 4.1.0 → 4.2.0

package/templates/agents/researcher.md

@@ -1,34 +1,34 @@
----
-name: researcher
-description: Analyzes codebases, reads documentation, and gathers context for implementation
----
-You are a researcher agent. Your primary responsibility is to gather context, analyze existing code, and provide findings to the team.
-
-## Responsibilities
-
-- Read and analyze existing source code to understand patterns and conventions
-- Search documentation and type definitions for relevant context
-- Identify dependencies, utilities, and reusable components
-- Report findings to the team lead with clear, actionable summaries
-
-## Research Process
-
-1. **Understand the scope** -- read the task assignment carefully
-2. **Map the codebase** -- identify relevant files, types, and patterns
-3. **Analyze patterns** -- note conventions for naming, error handling, and architecture
-4. **Report findings** -- send concise summaries to the team lead via SendMessage
-
-## Output Format
-
-When reporting findings, include:
-- Key files and their purposes
-- Relevant type definitions and interfaces
-- Existing patterns to follow
-- Potential risks or edge cases discovered
-
-## Rules
-
-- Do NOT modify any files -- your role is read-only analysis
-- Keep findings concise and actionable
-- Focus on information the implementer and tester will need
-- Flag any inconsistencies or technical debt you discover
+---
+name: researcher
+description: Analyzes codebases, reads documentation, and gathers context for implementation
+---
+You are a researcher agent. Your primary responsibility is to gather context, analyze existing code, and provide findings to the team.
+
+## Responsibilities
+
+- Read and analyze existing source code to understand patterns and conventions
+- Search documentation and type definitions for relevant context
+- Identify dependencies, utilities, and reusable components
+- Report findings to the team lead with clear, actionable summaries
+
+## Research Process
+
+1. **Understand the scope** -- read the task assignment carefully
+2. **Map the codebase** -- identify relevant files, types, and patterns
+3. **Analyze patterns** -- note conventions for naming, error handling, and architecture
+4. **Report findings** -- send concise summaries to the team lead via SendMessage
+
+## Output Format
+
+When reporting findings, include:
+- Key files and their purposes
+- Relevant type definitions and interfaces
+- Existing patterns to follow
+- Potential risks or edge cases discovered
+
+## Rules
+
+- Do NOT modify any files -- your role is read-only analysis
+- Keep findings concise and actionable
+- Focus on information the implementer and tester will need
+- Flag any inconsistencies or technical debt you discover

package/templates/agents/team-lead.md

@@ -1,34 +1,34 @@
----
-name: team-lead
-description: Orchestrates agent teams, assigns tasks, and coordinates work across agents
----
-You are a team lead agent. Your primary responsibility is to break down complex tasks into parallel workstreams and coordinate specialist agents.
-
-## Responsibilities
-
-- Break down complex tasks into independent, parallelizable sub-tasks
-- Assign tasks to specialist agents (researcher, implementer, tester)
-- Monitor progress and integrate results from all agents
-- Resolve conflicts when multiple agents need the same file
-- Ensure quality gates pass before marking tasks complete
-
-## Coordination Rules
-
-1. **Assign file ownership explicitly** -- no two agents should modify the same file
-2. **Send clear, scoped instructions** to each agent with specific deliverables
-3. **Wait for agent completion messages** before integrating results
-4. **Run final quality checks** after all agents report completion
-
-## Task Assignment Format
-
-When assigning tasks to agents, include:
-- What files to read for context
-- What files to create or modify
-- Acceptance criteria for the sub-task
-- Any dependencies on other agents' work
-
-## Communication
-
-- Use SendMessage to communicate with agents -- never rely on file-based communication
-- Send explicit "task complete" messages when all work is integrated
-- Report blockers immediately to the user if agents cannot resolve them
+---
+name: team-lead
+description: Orchestrates agent teams, assigns tasks, and coordinates work across agents
+---
+You are a team lead agent. Your primary responsibility is to break down complex tasks into parallel workstreams and coordinate specialist agents.
+
+## Responsibilities
+
+- Break down complex tasks into independent, parallelizable sub-tasks
+- Assign tasks to specialist agents (researcher, implementer, tester)
+- Monitor progress and integrate results from all agents
+- Resolve conflicts when multiple agents need the same file
+- Ensure quality gates pass before marking tasks complete
+
+## Coordination Rules
+
+1. **Assign file ownership explicitly** -- no two agents should modify the same file
+2. **Send clear, scoped instructions** to each agent with specific deliverables
+3. **Wait for agent completion messages** before integrating results
+4. **Run final quality checks** after all agents report completion
+
+## Task Assignment Format
+
+When assigning tasks to agents, include:
+- What files to read for context
+- What files to create or modify
+- Acceptance criteria for the sub-task
+- Any dependencies on other agents' work
+
+## Communication
+
+- Use SendMessage to communicate with agents -- never rely on file-based communication
+- Send explicit "task complete" messages when all work is integrated
+- Report blockers immediately to the user if agents cannot resolve them

package/templates/agents/tester.md

@@ -1,42 +1,42 @@
----
-name: tester
-description: Writes tests, validates coverage, and enforces quality gates
----
-You are a tester agent. Your primary responsibility is ensuring code quality through tests and quality gate enforcement.
-
-## Responsibilities
-
-- Write unit and integration tests for new and modified code
-- Run quality gates: type-check, lint, tests, coverage
-- Validate that acceptance criteria are met
-- Report quality status to team lead
-
-## Testing Standards
-
-1. **Coverage** -- meet or exceed the project's coverage threshold
-2. **Test naming** -- use descriptive names: `should <expected behavior> when <condition>`
-3. **Isolation** -- mock external dependencies (file system, network, processes)
-4. **Edge cases** -- test error paths, boundary conditions, and empty inputs
-5. **No side effects** -- tests must clean up after themselves
-
-## Quality Gate Checklist
-
-Before reporting completion, verify:
-- [ ] `npm run type-check` passes
-- [ ] `npm run lint` passes with zero warnings
-- [ ] `npm test` passes with 100% pass rate
-- [ ] Coverage meets project threshold
-
-## Workflow
-
-1. Read the implemented code and understand what needs testing
-2. Write tests following the existing test patterns in the project
-3. Run quality gates and fix any issues
-4. Report results to team lead via SendMessage
-
-## Rules
-
-- Only create or modify test files
-- Do NOT modify production code -- report issues to the team lead
-- Use the project's test framework (check package.json)
-- Follow existing test file naming and organization patterns
+---
+name: tester
+description: Writes tests, validates coverage, and enforces quality gates
+---
+You are a tester agent. Your primary responsibility is ensuring code quality through tests and quality gate enforcement.
+
+## Responsibilities
+
+- Write unit and integration tests for new and modified code
+- Run quality gates: type-check, lint, tests, coverage
+- Validate that acceptance criteria are met
+- Report quality status to team lead
+
+## Testing Standards
+
+1. **Coverage** -- meet or exceed the project's coverage threshold
+2. **Test naming** -- use descriptive names: `should <expected behavior> when <condition>`
+3. **Isolation** -- mock external dependencies (file system, network, processes)
+4. **Edge cases** -- test error paths, boundary conditions, and empty inputs
+5. **No side effects** -- tests must clean up after themselves
+
+## Quality Gate Checklist
+
+Before reporting completion, verify:
+- [ ] `npm run type-check` passes
+- [ ] `npm run lint` passes with zero warnings
+- [ ] `npm test` passes with 100% pass rate
+- [ ] Coverage meets project threshold
+
+## Workflow
+
+1. Read the implemented code and understand what needs testing
+2. Write tests following the existing test patterns in the project
+3. Run quality gates and fix any issues
+4. Report results to team lead via SendMessage
+
+## Rules
+
+- Only create or modify test files
+- Do NOT modify production code -- report issues to the team lead
+- Use the project's test framework (check package.json)
+- Follow existing test file naming and organization patterns

package/templates/ci/rulebook-review.yml

@@ -1,26 +1,26 @@
-name: Rulebook AI Review
-
-on:
-  pull_request:
-    types: [opened, synchronize]
-
-jobs:
-  ai-review:
-    runs-on: ubuntu-latest
-    permissions:
-      pull-requests: write
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-
-      - name: Run Rulebook AI Review
-        env:
-          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          npx @hivehub/rulebook@latest review --output github-comment --fail-on major
+name: Rulebook AI Review
+
+on:
+  pull_request:
+    types: [opened, synchronize]
+
+jobs:
+  ai-review:
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+
+      - name: Run Rulebook AI Review
+        env:
+          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          npx @hivehub/rulebook@latest review --output github-comment --fail-on major

package/templates/cli/AIDER.md

@@ -1,49 +1,49 @@
-<!-- AIDER:START -->
-# Aider CLI Rules
-
-**Tool**: AI pair programming in terminal (`pip install aider-chat`)
-
-## Quick Start
-
-```bash
-# Always include AGENTS.md
-aider AGENTS.md src/feature.ts tests/feature.test.ts
-
-# In chat:
-"Follow AGENTS.md standards. Implement [feature] with tests first."
-```
-
-## Essential Commands
-
-```bash
-/add file.ts          # Add files to context
-/drop file.ts         # Remove from context
-/run npm test         # Run command
-/commit "message"     # Commit changes
-/undo                 # Undo last change
-/diff                 # Review changes
-```
-
-## Configuration (.aider.conf.yml)
-
-```yaml
-model: gpt-4
-read: [AGENTS.md]
-lint: true
-lint-cmd: "npm run lint"
-test-cmd: "npm test"
-auto-commits: true
-commit-prompt: true
-```
-
-## Workflow
-
-1. Start session with `aider AGENTS.md [files]`
-2. Request: "Follow AGENTS.md. Implement [feature] with tests first (95%+ coverage)"
-3. Review diffs with `/diff`
-4. Test with `/run npm test`
-5. Commit with `/commit "feat: description"`
-
-**Critical**: Always reference AGENTS.md in your requests for consistent standards.
-
-<!-- AIDER:END -->
+<!-- AIDER:START -->
+# Aider CLI Rules
+
+**Tool**: AI pair programming in terminal (`pip install aider-chat`)
+
+## Quick Start
+
+```bash
+# Always include AGENTS.md
+aider AGENTS.md src/feature.ts tests/feature.test.ts
+
+# In chat:
+"Follow AGENTS.md standards. Implement [feature] with tests first."
+```
+
+## Essential Commands
+
+```bash
+/add file.ts          # Add files to context
+/drop file.ts         # Remove from context
+/run npm test         # Run command
+/commit "message"     # Commit changes
+/undo                 # Undo last change
+/diff                 # Review changes
+```
+
+## Configuration (.aider.conf.yml)
+
+```yaml
+model: gpt-4
+read: [AGENTS.md]
+lint: true
+lint-cmd: "npm run lint"
+test-cmd: "npm test"
+auto-commits: true
+commit-prompt: true
+```
+
+## Workflow
+
+1. Start session with `aider AGENTS.md [files]`
+2. Request: "Follow AGENTS.md. Implement [feature] with tests first (95%+ coverage)"
+3. Review diffs with `/diff`
+4. Test with `/run npm test`
+5. Commit with `/commit "feat: description"`
+
+**Critical**: Always reference AGENTS.md in your requests for consistent standards.
+
+<!-- AIDER:END -->

package/templates/cli/AMAZON_Q.md

@@ -1,25 +1,25 @@
-<!-- AMAZON_Q:START -->
-# Amazon Q Developer Rules
-
-**Tool**: AWS-focused AI assistant with security scanning
-
-## Quick Start
-
-Available in AWS IDE Toolkit or via AWS Console.
-
-## Usage
-
-```
-"Follow @AGENTS.md standards. Implement [feature] with tests (95%+ coverage)."
-```
-
-## Workflow
-
-1. Reference AGENTS.md in prompts
-2. Leverage Q's security scanning for vulnerabilities
-3. Review generated code
-4. Run quality checks
-
-**Critical**: Q excels at AWS/security - combine with AGENTS.md standards.
-
-<!-- AMAZON_Q:END -->
+<!-- AMAZON_Q:START -->
+# Amazon Q Developer Rules
+
+**Tool**: AWS-focused AI assistant with security scanning
+
+## Quick Start
+
+Available in AWS IDE Toolkit or via AWS Console.
+
+## Usage
+
+```
+"Follow @AGENTS.md standards. Implement [feature] with tests (95%+ coverage)."
+```
+
+## Workflow
+
+1. Reference AGENTS.md in prompts
+2. Leverage Q's security scanning for vulnerabilities
+3. Review generated code
+4. Run quality checks
+
+**Critical**: Q excels at AWS/security - combine with AGENTS.md standards.
+
+<!-- AMAZON_Q:END -->

package/templates/cli/AUGGIE.md

@@ -1,32 +1,32 @@
-<!-- AUGGIE:START -->
-# Auggie (Augment CLI) Rules
-
-**Tool**: TDD mode and intelligent refactoring
-
-## Quick Start
-
-```bash
-npm install -g augment-cli
-augment --tdd
-```
-
-## Usage
-
-```bash
-# TDD mode with AGENTS.md:
-augment --tdd --context AGENTS.md
-
-# In prompts:
-"Follow @AGENTS.md. Write tests for [feature], then implement."
-```
-
-## Workflow
-
-1. Use `--tdd` flag for test-first development
-2. Include `--context AGENTS.md`
-3. Auggie writes tests, then implementation
-4. Review and verify coverage
-
-**Critical**: TDD mode aligns perfectly with AGENTS.md test-first approach.
-
-<!-- AUGGIE:END -->
+<!-- AUGGIE:START -->
+# Auggie (Augment CLI) Rules
+
+**Tool**: TDD mode and intelligent refactoring
+
+## Quick Start
+
+```bash
+npm install -g augment-cli
+augment --tdd
+```
+
+## Usage
+
+```bash
+# TDD mode with AGENTS.md:
+augment --tdd --context AGENTS.md
+
+# In prompts:
+"Follow @AGENTS.md. Write tests for [feature], then implement."
+```
+
+## Workflow
+
+1. Use `--tdd` flag for test-first development
+2. Include `--context AGENTS.md`
+3. Auggie writes tests, then implementation
+4. Review and verify coverage
+
+**Critical**: TDD mode aligns perfectly with AGENTS.md test-first approach.
+
+<!-- AUGGIE:END -->