From f7976355a58c7fb626a3c1d130b1f4e07647043a Mon Sep 17 00:00:00 2001 From: "Andrei G." Date: Wed, 23 Sep 2026 12:15:10 +0200 Subject: [PATCH 1/2] feat(plugin): adapt to Claude Code 2.1.265-2.1.280, bump v1.47.0 - Auto mode subagents report through SubagentHandback: continuous-improvement, sdd-integration and the handoff protocol no longer require a plain final message - team-develop Step 6.5 covers /code-review running inline where ReportFindings exists (desktop app) as well as forked - Opus agents move to claude-opus-5-5 with explicit effort: high - team-develop and team-debug forbid isolation on teammate spawns - Marketplace entry description and keywords synced with plugin.json - Fix continuous-improvement journal preflight printing an empty value - Fix stale sonnet labels for rust-arch-analyst and rust-security-analyst --- .claude-plugin/marketplace.json | 18 +++++++++++----- README.md | 6 +++--- rust-code/.claude-plugin/plugin.json | 5 +++-- rust-code/CHANGELOG.md | 21 +++++++++++++++++++ rust-code/README.md | 4 ++-- rust-code/agents/01-rust-architect.md | 2 +- .../agents/05-rust-security-maintenance.md | 2 +- rust-code/agents/09-rust-critic.md | 2 +- rust-code/agents/15-rust-arch-analyst.md | 2 +- rust-code/agents/16-rust-security-analyst.md | 2 +- .../skills/continuous-improvement/SKILL.md | 12 +++++------ .../references/sdd-integration.md | 4 ++-- .../references/sdd-integration.md | 4 ++-- .../references/sdd-integration.md | 4 ++-- rust-code/skills/rust-agent-handoff/SKILL.md | 2 +- rust-code/skills/team-debug/SKILL.md | 2 ++ rust-code/skills/team-develop/SKILL.md | 6 ++++-- 17 files changed, 66 insertions(+), 32 deletions(-) diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index 15d09d7..66e5431 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -6,14 +6,14 @@ }, "metadata": { "description": "Professional Rust development plugin: specialist agents with LSP integration, team orchestration, and peer-to-peer communication", - "version": "1.46.0" + "version": "1.47.0" }, "plugins": [ { "name": "rust-agents", "source": "./rust-code", - "description": "Comprehensive collection of specialized Rust development agents with Claude Code best practices. 15 specialist agents covering the full development lifecycle. rust-live-tester for live binary execution and anomaly detection; rust-researcher for dependency monitoring and competitive parity; rust-arch-analyst for architecture audits; rust-security-analyst for vulnerability scanning. continuous-improvement orchestrates all four as a read-only cycle. rust-modern-apis for proactive Rust 1.89–1.98 API suggestions. team-develop and team-debug for multi-agent orchestration. Full-cycle SDD with BRD/SRS/NFR pipeline. rust-analyzer LSP integration. Adversarial critic for stress-testing designs. Rust Edition 2024.", - "version": "1.46.0", + "description": "Rust development agents and skills for Claude Code: 15 specialist agents (architect, developer, testing, performance, security, reviewer, CI/CD, debugger, critic, SDD, live-tester, tech-writer, researcher, architecture and security analysts), team-develop and team-debug agent-team orchestration, a read-only continuous-improvement cycle that also runs headless, Rust 1.89-1.98 API reference, handoff protocol, spec-driven development pipeline, and rust-analyzer LSP integration.", + "version": "1.47.0", "author": { "name": "Andrei G", "email": "andrei.g@my.com" @@ -38,7 +38,7 @@ "edition-2024", "agent-teams", "team-orchestration", - "teamlead", + "team-debug", "issue-triage", "github-issues", "continuous-improvement", @@ -48,7 +48,15 @@ "security-audit", "tech-writer", "documentation", - "mdbook" + "mdbook", + "brd", + "srs", + "nfr", + "requirements", + "spec-driven-development", + "modern-apis", + "rust-1-89", + "rust-1-98" ], "category": "development", "tags": [ diff --git a/README.md b/README.md index d4a0d05..c651ee0 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ This repository contains plugins that extend Claude Code's capabilities with spe ### Rust Agents Plugin (`rust-code`) -[![Version](https://img.shields.io/badge/version-1.46.0-blue)](./rust-code) +[![Version](https://img.shields.io/badge/version-1.47.0-blue)](./rust-code) [![License](https://img.shields.io/badge/license-MIT-green)](./rust-code/LICENSE) A comprehensive collection of specialized Rust development agents covering the entire Rust development lifecycle. @@ -59,8 +59,8 @@ A comprehensive collection of specialized Rust development agents covering the e | rust-live-tester | sonnet | Live binary execution, anomaly detection, coverage tracking, bug filing | | tech-writer | sonnet | User-facing documentation with mdBook, progressive disclosure | | rust-researcher | sonnet | Dependency monitoring, security advisories, research, competitive parity | -| rust-arch-analyst | sonnet | Architecture audits: type system anti-patterns, DRY violations, workspace structure, async defects | -| rust-security-analyst | sonnet | Vulnerability audits: dependency advisories, unsafe code, secrets, injection, crypto misuse, auth, panic-DoS, supply chain | +| rust-arch-analyst | opus | Architecture audits: type system anti-patterns, DRY violations, workspace structure, async defects | +| rust-security-analyst | opus | Vulnerability audits: dependency advisories, unsafe code, secrets, injection, crypto misuse, auth, panic-DoS, supply chain | **Best for**: Rust projects requiring expert guidance in architecture, performance, security, testing, DevOps, or multi-agent team workflows. diff --git a/rust-code/.claude-plugin/plugin.json b/rust-code/.claude-plugin/plugin.json index cc0efb8..ee03b5a 100644 --- a/rust-code/.claude-plugin/plugin.json +++ b/rust-code/.claude-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "rust-agents", - "version": "1.46.0", + "version": "1.47.0", "description": "Rust development agents and skills for Claude Code: 15 specialist agents (architect, developer, testing, performance, security, reviewer, CI/CD, debugger, critic, SDD, live-tester, tech-writer, researcher, architecture and security analysts), team-develop and team-debug agent-team orchestration, a read-only continuous-improvement cycle that also runs headless, Rust 1.89-1.98 API reference, handoff protocol, spec-driven development pipeline, and rust-analyzer LSP integration.", "author": { "name": "Andrei G", @@ -30,7 +30,8 @@ "issue-triage", "github-issues", "continuous-improvement", - "ci-analyst", + "live-testing", + "research-protocol", "vulnerability-scanning", "security-audit", "tech-writer", diff --git a/rust-code/CHANGELOG.md b/rust-code/CHANGELOG.md index 4881016..d3b9405 100644 --- a/rust-code/CHANGELOG.md +++ b/rust-code/CHANGELOG.md @@ -5,6 +5,27 @@ All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). +## [1.47.0] - 2026-09-23 + +Adapts the plugin to Claude Code 2.1.265–2.1.280. + +### Changed + +- `rust-architect`, `rust-critic`, `rust-security-maintenance`, `rust-arch-analyst`, `rust-security-analyst`: model `claude-opus-5` → `claude-opus-5-5`, keeping `effort: high` explicit because the model defaults to `medium`. +- `continuous-improvement` subagents engine and `sdd-integration` references: in auto mode agents deliver their report through `SubagentHandback`, not a plain final message. +- `rust-agent-handoff`: names where the handoff block goes: `SendMessage` as a teammate, `SubagentHandback` when available, otherwise the final message. +- `team-develop` Step 6.5: handles `/code-review` running inline in the desktop app (`ReportFindings`) as well as forked. +- `team-develop`, `team-debug`: never pass `isolation` on teammate spawns, since it turns them into plain subagents outside the team. +- Marketplace entry description and keywords synced with `plugin.json`, because `/plugin` → Installed now shows the marketplace entry. +- `CLAUDE.md`: documents `omitClaudeMd`, `initialPrompt` (ignored for plugin agents) and full-ID model pinning. +- README: headless `continuous-improvement` runs recommend Claude Code 2.1.280 or later. + +### Fixed + +- `continuous-improvement` preflight showed an empty "Last cycle journal" instead of `none` when the journal directory was missing. +- Root README and `continuous-improvement` still described `rust-arch-analyst` and `rust-security-analyst` as `sonnet` agents. +- Version badges, plugin and marketplace manifests bumped to `1.47.0`. + ## [1.46.0] - 2026-09-16 ### Changed diff --git a/rust-code/README.md b/rust-code/README.md index da620e4..923bc85 100644 --- a/rust-code/README.md +++ b/rust-code/README.md @@ -1,6 +1,6 @@ # Rust Agents Plugin -[![Version](https://img.shields.io/badge/version-1.46.0-blue)](https://github.com/bug-ops/claude-plugins) +[![Version](https://img.shields.io/badge/version-1.47.0-blue)](https://github.com/bug-ops/claude-plugins) [![License](https://img.shields.io/badge/license-MIT-green)](LICENSE) [![Rust Edition](https://img.shields.io/badge/rust-Edition%202024-orange)](https://doc.rust-lang.org/edition-guide/rust-2024/) @@ -456,7 +456,7 @@ Orchestrate a full CI cycle by spawning `rust-live-tester`, `rust-researcher`, ` **Workflow**: `TaskCreate` per agent → spawn teammates with `name` (the team forms implicitly) → wait for `SendMessage` with handoff → `TaskUpdate(completed)` → `SendMessage(shutdown_request)`; team directories are cleaned up automatically at session end -**Engines**: with `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` in an interactive session the agents run as an agent team (add `CLAUDE_CODE_ENABLE_TODO_TOOLS=1` on Claude Code 2.1.233+ for shared task-list coordination). Without the flag, or in a non-interactive session, the same agents run as background subagents and report through task notifications. This is the only orchestration skill that works headless, which makes it suitable for recurring runs: +**Engines**: with `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` in an interactive session the agents run as an agent team (add `CLAUDE_CODE_ENABLE_TODO_TOOLS=1` on Claude Code 2.1.233+ for shared task-list coordination). Without the flag, or in a non-interactive session, the same agents run as background subagents and report back when they finish (in auto mode through the `SubagentHandback` call). This is the only orchestration skill that works headless, which makes it suitable for recurring runs. Use Claude Code 2.1.280 or later for unattended runs: earlier versions could lose background reports or leave a `-p` run hanging: ```bash # one-off unattended cycle diff --git a/rust-code/agents/01-rust-architect.md b/rust-code/agents/01-rust-architect.md index 6629a98..255f0aa 100644 --- a/rust-code/agents/01-rust-architect.md +++ b/rust-code/agents/01-rust-architect.md @@ -1,7 +1,7 @@ --- name: rust-architect description: Rust strategic architect specializing in type-driven design, domain modeling, workspace architecture, and compile-time safety patterns. Use PROACTIVELY when starting projects, designing type hierarchies, making architectural decisions, or implementing state machines with typestate pattern. -model: claude-opus-5 +model: claude-opus-5-5 effort: high memory: "user" experimental: diff --git a/rust-code/agents/05-rust-security-maintenance.md b/rust-code/agents/05-rust-security-maintenance.md index 5960a82..49bc84f 100644 --- a/rust-code/agents/05-rust-security-maintenance.md +++ b/rust-code/agents/05-rust-security-maintenance.md @@ -1,7 +1,7 @@ --- name: rust-security-maintenance description: Rust security and maintenance specialist focused on cargo-deny, dependency management, vulnerability scanning, and secure coding practices. MUST BE USED for unsafe code blocks, authentication, authorization, cryptography, or external input validation. -model: claude-opus-5 +model: claude-opus-5-5 effort: high memory: "user" skills: diff --git a/rust-code/agents/09-rust-critic.md b/rust-code/agents/09-rust-critic.md index 0c20387..9ebeb99 100644 --- a/rust-code/agents/09-rust-critic.md +++ b/rust-code/agents/09-rust-critic.md @@ -1,7 +1,7 @@ --- name: rust-critic description: Adversarial critic specializing in finding logical gaps, flawed assumptions, scalability limits, and missing edge cases in architectural designs, implementation proposals, and ideas. Use PROACTIVELY after architecture design, before committing to an approach, or when a user wants their idea stress-tested. Never writes fixes — produces structured critique reports (may build a throwaway reproducer to prove a finding). Triggers on "review this design", "challenge assumptions", "find weak points", "devil's advocate", "stress test this idea", "what could go wrong", "critique this". -model: claude-opus-5 +model: claude-opus-5-5 effort: high memory: "user" skills: diff --git a/rust-code/agents/15-rust-arch-analyst.md b/rust-code/agents/15-rust-arch-analyst.md index c6bb2c4..19e5db9 100644 --- a/rust-code/agents/15-rust-arch-analyst.md +++ b/rust-code/agents/15-rust-arch-analyst.md @@ -1,7 +1,7 @@ --- name: rust-arch-analyst description: Rust architecture analyst for continuous improvement cycles. Scans existing codebases for type system anti-patterns, DRY violations, API naming issues, workspace structure problems, and async concurrency defects. Read-only role — identifies and files improvement issues, never modifies source code. Use as part of the continuous-improvement skill or when auditing an existing project's structural health. -model: claude-opus-5 +model: claude-opus-5-5 effort: high memory: "local" skills: diff --git a/rust-code/agents/16-rust-security-analyst.md b/rust-code/agents/16-rust-security-analyst.md index 95e76ea..6488d9d 100644 --- a/rust-code/agents/16-rust-security-analyst.md +++ b/rust-code/agents/16-rust-security-analyst.md @@ -1,7 +1,7 @@ --- name: rust-security-analyst description: Rust security analyst for continuous improvement cycles. Maps the attack surface and scans existing codebases for vulnerabilities — dependency advisories, unsafe code, exposed secrets, injection and input-validation gaps, cryptography misuse, broken authentication, panic and resource-exhaustion denial of service, network and filesystem hardening, supply-chain risk, and missing verification gates. Read-only role — identifies and files security issues, never modifies source code. Use as part of the continuous-improvement skill or when auditing an existing project's security posture. -model: claude-opus-5 +model: claude-opus-5-5 effort: high memory: "local" skills: diff --git a/rust-code/skills/continuous-improvement/SKILL.md b/rust-code/skills/continuous-improvement/SKILL.md index f05481f..449bbbc 100644 --- a/rust-code/skills/continuous-improvement/SKILL.md +++ b/rust-code/skills/continuous-improvement/SKILL.md @@ -12,8 +12,8 @@ Run a continuous improvement cycle for the current Rust project by coordinating - **`rust-live-tester`** — syncs with remote, executes the project binary live, detects anomalies and regressions, tracks coverage, files bug issues - **`rust-researcher`** — monitors dependency health, researches new techniques, tracks competitive parity, files research and dependency issues -- **`rust-arch-analyst`** — audits existing codebase for type system anti-patterns, DRY violations, architectural debt, API naming issues, and async concurrency problems; files improvement issues (read-only, sonnet + high effort) -- **`rust-security-analyst`** — scans existing codebase for vulnerabilities: dependency advisories, unsafe code, exposed secrets, injection and input-validation gaps, crypto misuse, broken auth, panic-based DoS, and supply-chain risk; files security issues (read-only, sonnet + high effort) +- **`rust-arch-analyst`** — audits existing codebase for type system anti-patterns, DRY violations, architectural debt, API naming issues, and async concurrency problems; files improvement issues (read-only) +- **`rust-security-analyst`** — scans existing codebase for vulnerabilities: dependency advisories, unsafe code, exposed secrets, injection and input-validation gaps, crypto misuse, broken auth, panic-based DoS, and supply-chain risk; files security issues (read-only) **Focus**: $ARGUMENTS @@ -43,7 +43,7 @@ If the preflight shows `.claude/rules/continuous-improvement.md` as present, pas - Task tools flag: !`printenv CLAUDE_CODE_ENABLE_TODO_TOOLS || echo unset` - Cargo.toml: !`test -f Cargo.toml && echo present || echo missing` - Project CI rules: !`test -f .claude/rules/continuous-improvement.md && echo present || echo absent` -- Last cycle journal: !`ls .local/testing/journal/ 2>/dev/null | grep -E '^ci-[0-9]{3}\.md$' | sort | tail -1 || echo none` +- Last cycle journal: !`ls .local/testing/journal/ 2>/dev/null | grep -E '^ci-[0-9]{3}\.md$' | sort | tail -1 | grep . || echo none` STOP if Cargo.toml is `missing`. @@ -54,9 +54,9 @@ This cycle is read-only fan-out: every agent works alone and reports back, so it | Agent teams flag | Engine | How agents report | |---|---|---| | `1` in an interactive session | **teams** — named spawns become teammates, the team forms implicitly on the first spawn | `SendMessage` to `team-lead` with handoff frontmatter + path | -| `unset`, or a non-interactive session (`claude -p`, SDK, `/loop`, `/schedule`) | **subagents** — the same `Agent()` calls run as background subagents | Task notification carries the agent's final message; require the handoff frontmatter + path in it | +| `unset`, or a non-interactive session (`claude -p`, SDK, `/loop`, `/schedule`) | **subagents** — the same `Agent()` calls run as background subagents | The agent's report arrives with its task notification, or in auto mode as its `SubagentHandback` message; require the handoff frontmatter + path in it | -Tell the user which engine is active. On the subagents engine: drop the Task Management and Communication sections from the spawn template, replace them with "Finish with your handoff frontmatter block + path as the last lines of your final message", skip Step 2.5 (background subagents end on their own), and treat each task notification as the WAIT signal. Never run `team-develop` or `team-debug` this way — they need peer messaging. +Tell the user which engine is active. On the subagents engine: drop the Task Management and Communication sections from the spawn template, replace them with "Deliver your report to the caller: the handoff frontmatter block + path. If you have the `SubagentHandback` tool, that call is your report — plain text at the end is not delivered", skip Step 2.5 (background subagents end on their own), and treat each task notification as the WAIT signal. Never run `team-develop` or `team-debug` this way — they need peer messaging. On the teams engine, load the tools: @@ -250,7 +250,7 @@ Write your handoff with a Security Review section listing all findings, severiti TaskUpdate(taskId: "security", owner: "security-analyst", status: "in_progress") ``` -**WAIT** for all spawned agents (teams engine: messages with handoff frontmatter + paths; subagents engine: task notifications). Then update their tasks to `completed`. Apply the Agent outcomes table from Step 0 to partial or failed results. +**WAIT** for all spawned agents (teams engine: messages with handoff frontmatter + paths; subagents engine: task notifications, with the report in the agent's hand-back message in auto mode). Then update their tasks to `completed`. Apply the Agent outcomes table from Step 0 to partial or failed results. ## Step 2.5: Shutdown Agents (teams engine only) diff --git a/rust-code/skills/continuous-improvement/references/sdd-integration.md b/rust-code/skills/continuous-improvement/references/sdd-integration.md index deb88e3..49996d7 100644 --- a/rust-code/skills/continuous-improvement/references/sdd-integration.md +++ b/rust-code/skills/continuous-improvement/references/sdd-integration.md @@ -64,7 +64,7 @@ Use the Spec Template from the sdd skill. Pre-fill all sections from the context above. Mark any missing information as `[NEEDS CLARIFICATION: ...]` rather than blocking. -Respond with the path to the created spec file when done. +Report the path to the created spec file when done. ``` ### Subagent call @@ -116,7 +116,7 @@ Research spec structure (use Spec Template, focus on these sections): The subagent MUST: 1. Create `.local/specs/-/spec.md` 2. Add an entry to `.local/specs/MOC-specs.md` -3. Return the spec file path in its final message +3. Return the spec file path in its report The CI analyst MUST: 1. Extract the spec path from the subagent result diff --git a/rust-code/skills/live-testing/references/sdd-integration.md b/rust-code/skills/live-testing/references/sdd-integration.md index db21e3e..8cad24f 100644 --- a/rust-code/skills/live-testing/references/sdd-integration.md +++ b/rust-code/skills/live-testing/references/sdd-integration.md @@ -64,7 +64,7 @@ Use the Spec Template from the sdd skill. Pre-fill all sections from the context above. Mark any missing information as `[NEEDS CLARIFICATION: ...]` rather than blocking. -Respond with the path to the created spec file when done. +Report the path to the created spec file when done. ``` ### Subagent call @@ -116,7 +116,7 @@ Research spec structure (use Spec Template, focus on these sections): The subagent MUST: 1. Create `.local/specs/-/spec.md` 2. Add an entry to `.local/specs/MOC-specs.md` -3. Return the spec file path in its final message +3. Return the spec file path in its report The CI analyst MUST: 1. Extract the spec path from the subagent result diff --git a/rust-code/skills/research-protocol/references/sdd-integration.md b/rust-code/skills/research-protocol/references/sdd-integration.md index db21e3e..8cad24f 100644 --- a/rust-code/skills/research-protocol/references/sdd-integration.md +++ b/rust-code/skills/research-protocol/references/sdd-integration.md @@ -64,7 +64,7 @@ Use the Spec Template from the sdd skill. Pre-fill all sections from the context above. Mark any missing information as `[NEEDS CLARIFICATION: ...]` rather than blocking. -Respond with the path to the created spec file when done. +Report the path to the created spec file when done. ``` ### Subagent call @@ -116,7 +116,7 @@ Research spec structure (use Spec Template, focus on these sections): The subagent MUST: 1. Create `.local/specs/-/spec.md` 2. Add an entry to `.local/specs/MOC-specs.md` -3. Return the spec file path in its final message +3. Return the spec file path in its report The CI analyst MUST: 1. Extract the spec path from the subagent result diff --git a/rust-code/skills/rust-agent-handoff/SKILL.md b/rust-code/skills/rust-agent-handoff/SKILL.md index 2422861..633d60a 100644 --- a/rust-code/skills/rust-agent-handoff/SKILL.md +++ b/rust-code/skills/rust-agent-handoff/SKILL.md @@ -47,7 +47,7 @@ Frontmatter is flat scalars; the only allowed array is `parent: [id1, id2]` when Conditional sections: `## Blockers` if `status: blocked`; `## Acceptance Criteria` if `next_task` needs more than one line. On `needs_discussion` state the open question — the caller returns it to the user. -3. Return frontmatter + path to caller — parent routes without reading the file: +3. Return frontmatter + path to caller — parent routes without reading the file. The block goes where your caller reads results: `SendMessage` to the lead when you are a teammate, the `SubagentHandback` call when you have that tool, otherwise your final message: ~~~markdown ## Handoff diff --git a/rust-code/skills/team-debug/SKILL.md b/rust-code/skills/team-debug/SKILL.md index 312e89c..808923a 100644 --- a/rust-code/skills/team-debug/SKILL.md +++ b/rust-code/skills/team-debug/SKILL.md @@ -42,6 +42,8 @@ Every WAIT step below ends with one of these outcomes: Never reuse a name for a fresh spawn — a new agent with an existing name shadows the old one and breaks `SendMessage` routing. +Never pass `isolation` on a teammate spawn, even when the Agent tool suggests `isolation: "worktree"` for parallel writers. A named call with `isolation` starts a plain subagent outside the team. Every teammate here is report-only. + ## Step 1: Load Tools ``` diff --git a/rust-code/skills/team-develop/SKILL.md b/rust-code/skills/team-develop/SKILL.md index fdf11cb..5c96325 100644 --- a/rust-code/skills/team-develop/SKILL.md +++ b/rust-code/skills/team-develop/SKILL.md @@ -150,6 +150,8 @@ Every WAIT step below ends with one of these outcomes. Handle them the same way Naming: never reuse a name for a fresh spawn — a new agent with an existing name shadows the old one and breaks `SendMessage` routing. Resume existing teammates with `SendMessage` when their context is useful (fix cycles, redesign after a critic verdict); use suffixed names (`developer-2`) when a clean context is wanted. +Isolation: never pass `isolation` on a teammate spawn, even when the Agent tool suggests `isolation: "worktree"` for parallel writers. A named call with `isolation` starts a plain subagent outside the team. Parallel developers stay apart through module ownership; validators are report-only. + ## Step 3: Architect ``` @@ -222,13 +224,13 @@ WAIT for ALL FOUR handoff messages. ## Step 6.5: Correctness Gate (lead-side, when available) -If the bundled `code-review` skill is listed in this session, run it yourself before spawning the reviewer. It is cheap, runs as a background subagent, and catches plain correctness bugs in the uncommitted diff, so `rust-code-reviewer` can focus on idiomatic Rust: +If the bundled `code-review` skill is listed in this session, run it yourself before spawning the reviewer. It catches plain correctness bugs in the uncommitted diff, so `rust-code-reviewer` can focus on idiomatic Rust: ``` Skill(skill: "code-review", args: "high") ``` -WAIT for its task notification. Send confirmed findings to the developer with `SendMessage` (same shape as Step 8) and WAIT for the fix handoff before Step 7. Never run this inside a teammate: teammates cannot start background work. +The skill picks its own mode. Usually it forks into a background subagent: WAIT for its task notification. When the `ReportFindings` tool is available (desktop app) it runs inline in your context and reports the findings in the same turn; pass `args: "medium"` there to keep the lead's context lean. Either way, send confirmed findings to the developer with `SendMessage` (same shape as Step 8) and WAIT for the fix handoff before Step 7. Never run this inside a teammate: teammates cannot start background work. ## Step 7: Code Review From 5c3fd86359ba7551a13a91450355894f8d6217ee Mon Sep 17 00:00:00 2001 From: "Andrei G." Date: Wed, 23 Sep 2026 12:15:45 +0200 Subject: [PATCH 2/2] docs(changelog): link 1.47.0 entries to PR #9 --- rust-code/CHANGELOG.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/rust-code/CHANGELOG.md b/rust-code/CHANGELOG.md index d3b9405..ffbf210 100644 --- a/rust-code/CHANGELOG.md +++ b/rust-code/CHANGELOG.md @@ -11,20 +11,20 @@ Adapts the plugin to Claude Code 2.1.265–2.1.280. ### Changed -- `rust-architect`, `rust-critic`, `rust-security-maintenance`, `rust-arch-analyst`, `rust-security-analyst`: model `claude-opus-5` → `claude-opus-5-5`, keeping `effort: high` explicit because the model defaults to `medium`. -- `continuous-improvement` subagents engine and `sdd-integration` references: in auto mode agents deliver their report through `SubagentHandback`, not a plain final message. -- `rust-agent-handoff`: names where the handoff block goes: `SendMessage` as a teammate, `SubagentHandback` when available, otherwise the final message. -- `team-develop` Step 6.5: handles `/code-review` running inline in the desktop app (`ReportFindings`) as well as forked. -- `team-develop`, `team-debug`: never pass `isolation` on teammate spawns, since it turns them into plain subagents outside the team. -- Marketplace entry description and keywords synced with `plugin.json`, because `/plugin` → Installed now shows the marketplace entry. -- `CLAUDE.md`: documents `omitClaudeMd`, `initialPrompt` (ignored for plugin agents) and full-ID model pinning. -- README: headless `continuous-improvement` runs recommend Claude Code 2.1.280 or later. +- `rust-architect`, `rust-critic`, `rust-security-maintenance`, `rust-arch-analyst`, `rust-security-analyst`: model `claude-opus-5` → `claude-opus-5-5`, keeping `effort: high` explicit because the model defaults to `medium`. (#9) +- `continuous-improvement` subagents engine and `sdd-integration` references: in auto mode agents deliver their report through `SubagentHandback`, not a plain final message. (#9) +- `rust-agent-handoff`: names where the handoff block goes: `SendMessage` as a teammate, `SubagentHandback` when available, otherwise the final message. (#9) +- `team-develop` Step 6.5: handles `/code-review` running inline in the desktop app (`ReportFindings`) as well as forked. (#9) +- `team-develop`, `team-debug`: never pass `isolation` on teammate spawns, since it turns them into plain subagents outside the team. (#9) +- Marketplace entry description and keywords synced with `plugin.json`, because `/plugin` → Installed now shows the marketplace entry. (#9) +- `CLAUDE.md`: documents `omitClaudeMd`, `initialPrompt` (ignored for plugin agents) and full-ID model pinning. (#9) +- README: headless `continuous-improvement` runs recommend Claude Code 2.1.280 or later. (#9) ### Fixed -- `continuous-improvement` preflight showed an empty "Last cycle journal" instead of `none` when the journal directory was missing. -- Root README and `continuous-improvement` still described `rust-arch-analyst` and `rust-security-analyst` as `sonnet` agents. -- Version badges, plugin and marketplace manifests bumped to `1.47.0`. +- `continuous-improvement` preflight showed an empty "Last cycle journal" instead of `none` when the journal directory was missing. (#9) +- Root README and `continuous-improvement` still described `rust-arch-analyst` and `rust-security-analyst` as `sonnet` agents. (#9) +- Version badges, plugin and marketplace manifests bumped to `1.47.0`. (#9) ## [1.46.0] - 2026-09-16