MythEclipse/zesdex
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

refactor(prompts): update reviewer prompts to align with Hive's directive and contamination protocols

Browse Source
This commit is contained in:
asepharyana
2026-07-15 00:20:41 +07:00
parent d392c4aa00
commit 519be7559b
12 changed files with 133 additions and 80 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/tool/spawn.rs
+6 -6
View File
@@ -22,12 +22,12 @@ impl Tool for SpawnAgents {
fn name(&self) -> &'static str { "spawn_agents" }
fn description(&self) -> &'static str {
"Fan out independent subtasks to multiple subagents running in PARALLEL. \
Pass a list of prompt strings — each becomes one autonomous subagent with \
"Fan out independent subtasks to multiple Hive nodes running in PARALLEL. \
Pass a list of prompt strings — each becomes one autonomous node with \
access to all tools. Use this whenever a task has independent parts that do \
not need each other's output (e.g. analysing multiple files simultaneously, \
writing multiple independent modules, parallel verification). \
Results from all agents are returned together. \
Results from all nodes are returned together. \
Use spawn_pipeline instead when each stage needs the previous stage's output."
}
@@ -37,7 +37,7 @@ impl Tool for SpawnAgents {
"properties": {
"agents": {
"type": "array",
"description": "List of prompt strings, one per subagent. Each subagent runs independently and in parallel.",
"description": "List of prompt strings, one per Hive node. Each node runs independently and in parallel.",
"items": { "type": "string" },
"minItems": 2
},
@@ -130,7 +130,7 @@ impl Tool for SpawnPipeline {
fn name(&self) -> &'static str { "spawn_pipeline" }
fn description(&self) -> &'static str {
"Run subagents SEQUENTIALLY in a pipeline — each stage sees findings \
"Run Hive nodes SEQUENTIALLY in a pipeline — each stage sees findings \
shared by previous stages via note_finding. Use when stages build on each \
other (e.g. 'research -> plan -> implement -> test'). \
Use spawn_agents instead when tasks are truly independent and order does not matter."
@@ -142,7 +142,7 @@ impl Tool for SpawnPipeline {
"properties": {
"stages": {
"type": "array",
"description": "Ordered list of prompt strings. Each stage runs after the previous one completes. Stages can call note_finding() to pass data to later stages.",
"description": "Ordered list of prompt strings — each stage is a Hive node that runs after the previous one completes. Stages can call note_finding() to pass data to later stages.",
"items": { "type": "string" },
"minItems": 2
}