Skip to content

Commit ea464c1

Browse files
retsohuangclaude
andcommitted
fix: address PR review comments
- Add space before (SDD) acronym in CLAUDE.md and AGENTS.md - Add missing verify step to Spectra workflow diagram - Update code-review-tools README to reflect review command removal Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 2d6b62e commit ea464c1

3 files changed

Lines changed: 19 additions & 16 deletions

File tree

AGENTS.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
# Spectra Instructions
44

5-
This project uses Spectra for Spec-Driven Development(SDD). Specs live in `openspec/specs/`, change proposals in `openspec/changes/`.
5+
This project uses Spectra for Spec-Driven Development (SDD). Specs live in `openspec/specs/`, change proposals in `openspec/changes/`.
66

77
## Use `/spectra:*` skills when:
88

@@ -15,7 +15,7 @@ This project uses Spectra for Spec-Driven Development(SDD). Specs live in `opens
1515

1616
## Workflow
1717

18-
discuss? → propose → apply ⇄ ingest → archive
18+
discuss? → propose → apply ⇄ ingest → verify → archive
1919

2020
- `discuss` is optional — skip if requirements are clear
2121
- Requirements change mid-work? Plan mode → `ingest` → resume `apply`

CLAUDE.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
# Spectra Instructions
44

5-
This project uses Spectra for Spec-Driven Development(SDD). Specs live in `openspec/specs/`, change proposals in `openspec/changes/`.
5+
This project uses Spectra for Spec-Driven Development (SDD). Specs live in `openspec/specs/`, change proposals in `openspec/changes/`.
66

77
## Use `/spectra:*` skills when:
88

@@ -15,7 +15,7 @@ This project uses Spectra for Spec-Driven Development(SDD). Specs live in `opens
1515

1616
## Workflow
1717

18-
discuss? → propose → apply ⇄ ingest → archive
18+
discuss? → propose → apply ⇄ ingest → verify → archive
1919

2020
- `discuss` is optional — skip if requirements are clear
2121
- Requirements change mid-work? Plan mode → `ingest` → resume `apply`

plugins/code-review-tools/README.md

Lines changed: 15 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -20,12 +20,12 @@ This plugin provides AI-powered code review capabilities that analyze git commit
2020
Review all commits from a specific commit hash to HEAD:
2121

2222
```bash
23-
/code-review-tools:review <commit-hash>
23+
/code-review <commit-hash>
2424
```
2525

2626
**Example:**
2727
```bash
28-
/code-review-tools:review abc123
28+
/code-review abc123
2929
```
3030

3131
### 2. Setup Custom Configuration
@@ -64,9 +64,10 @@ This plugin uses a **TypeScript CLI** for robust code processing, compiled to Ja
6464
```
6565
code-review-tools/
6666
├── commands/ # Slash commands (orchestration)
67-
│ ├── review.md # Main review command
68-
│ ├── init.md # Configuration setup
69-
│ └── create-rule.md # Custom rule generator
67+
│ ├── init.md # Configuration setup
68+
│ └── create-rule.md # Custom rule generator
69+
├── skills/ # Auto-invoked skills
70+
│ └── code-review/SKILL.md # Main review skill
7071
├── agents/ # Sub-agents for parallel processing
7172
│ ├── commit-reviewer.md # Reviews individual commits
7273
│ └── report-writer.md # Aggregates and writes reports
@@ -403,17 +404,17 @@ Common custom rule categories:
403404

404405
## Commands
405406

406-
| Command | Description |
407+
| Command / Skill | Description |
407408
| ----------------------------------------- | ----------------------------------- |
408-
| `/code-review-tools:review <commit-hash>` | Run code review from commit to HEAD |
409+
| `/code-review <commit-hash>` | Run code review from commit to HEAD |
409410
| `/code-review-tools:init` | Interactive setup for configuration |
410411
| `/code-review-tools:create-rule` | Create custom rules interactively |
411412

412413
## Review Output
413414

414415
### Terminal Output
415416

416-
When you run `/code-review-tools:review`, you'll see a concise summary in the terminal:
417+
When you run `/code-review`, you'll see a concise summary in the terminal:
417418
- Quick statistics: commits reviewed, files changed, issues found
418419
- Review process information (agents used, batching)
419420
- Top issue categories with counts
@@ -509,17 +510,18 @@ Full detailed reports are automatically saved to markdown files with:
509510
## Files and Directories
510511

511512
```
512-
plugins/code-review/
513+
plugins/code-review-tools/
513514
├── plugin.json # Plugin metadata
514515
├── README.md # This file
515516
├── config-schema.json # Configuration schema
516517
├── agents/
517518
│ ├── commit-reviewer.md # Sub-agent: reviews one commit with all rules
518519
│ └── report-writer.md # Sub-agent: orchestrates review, writes report (Sonnet)
519520
├── commands/
520-
│ ├── review.md # Main review command
521521
│ ├── init.md # Setup command
522522
│ └── create-rule.md # Rule creation command
523+
├── skills/
524+
│ └── code-review/SKILL.md # Main review skill
523525
├── rules/
524526
│ ├── component-extraction-rules.md
525527
│ ├── component-reuse-rules.md
@@ -550,8 +552,9 @@ plugins/code-review/
550552

551553
To improve this plugin:
552554
1. Built-in rules are in `plugins/code-review-tools/rules/`
553-
2. Commands are in `plugins/code-review-tools/commands/`
554-
3. Follow existing patterns for consistency
555+
2. Skills are in `plugins/code-review-tools/skills/`
556+
3. Commands are in `plugins/code-review-tools/commands/`
557+
4. Follow existing patterns for consistency
555558
4. Test with various commit scenarios
556559

557560
### For Developers

0 commit comments

Comments
 (0)