agenthub-multiagent-mcp 1.39.0 → 1.40.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
package/skills/catalog.json
CHANGED
|
@@ -55,6 +55,14 @@
|
|
|
55
55
|
"category": "skill",
|
|
56
56
|
"current_hash": "abf685d5d6770b34297f74dec42ff657b496a087db3f767296633b5db5bfdd4f",
|
|
57
57
|
"prior_hashes": ["f5ceff808f8f540e612c18b8ba1c1f5c771df9f64bf1eb84832279e61b140c30"]
|
|
58
|
+
},
|
|
59
|
+
{
|
|
60
|
+
"path": "skills/file-bug/SKILL.md",
|
|
61
|
+
"name": "file-bug",
|
|
62
|
+
"description": "File a reproducible bug as a first-class AgentHub ticket via report_bug — captures severity, repro steps, environment, and the defect lifecycle. Use when you hit a defect, failing test/CI step, or reproducible misbehavior worth tracking.",
|
|
63
|
+
"category": "skill",
|
|
64
|
+
"current_hash": "814bd58fa387c074b3fc1195b31e0e32d38402510028d4709579ec1f1ed663f1",
|
|
65
|
+
"prior_hashes": []
|
|
58
66
|
}
|
|
59
67
|
]
|
|
60
68
|
}
|
package/skills/manifest.json
CHANGED
|
@@ -35,6 +35,11 @@
|
|
|
35
35
|
"f5ceff808f8f540e612c18b8ba1c1f5c771df9f64bf1eb84832279e61b140c30",
|
|
36
36
|
"abf685d5d6770b34297f74dec42ff657b496a087db3f767296633b5db5bfdd4f"
|
|
37
37
|
]
|
|
38
|
+
},
|
|
39
|
+
"skills/file-bug/SKILL.md": {
|
|
40
|
+
"hashes": [
|
|
41
|
+
"814bd58fa387c074b3fc1195b31e0e32d38402510028d4709579ec1f1ed663f1"
|
|
42
|
+
]
|
|
38
43
|
}
|
|
39
44
|
}
|
|
40
45
|
}
|
|
@@ -0,0 +1,75 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: file-bug
|
|
3
|
+
description: File a reproducible bug as a first-class AgentHub ticket via the report_bug MCP tool. Use when you hit a defect, a failing test/CI step, or any reproducible misbehavior worth tracking — captures severity, repro steps, environment, and a defect lifecycle.
|
|
4
|
+
license: MIT
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# File a Bug
|
|
8
|
+
|
|
9
|
+
AgentHub has a first-class bug workflow (`add-bug-tracking-workflow`). A bug is a
|
|
10
|
+
`type=bug` ticket carrying **severity**, **reproduction steps**, an
|
|
11
|
+
**environment** tag, and a **defect lifecycle** (`bug_state`) that is separate
|
|
12
|
+
from work `status`. Use this skill whenever you find a reproducible defect worth
|
|
13
|
+
tracking — a failing test, a broken endpoint, a CI step that fails, or any
|
|
14
|
+
misbehavior you can describe steps for.
|
|
15
|
+
|
|
16
|
+
## File it with `report_bug`
|
|
17
|
+
|
|
18
|
+
Call the `report_bug` MCP tool. `repro_steps` is **required**; severity defaults
|
|
19
|
+
to `sev3` if omitted.
|
|
20
|
+
|
|
21
|
+
```jsonc
|
|
22
|
+
report_bug({
|
|
23
|
+
"title": "login returns 500",
|
|
24
|
+
"repro_steps": "1. POST /login with valid creds\n2. observe 500",
|
|
25
|
+
"severity": "sev1", // optional (default sev3)
|
|
26
|
+
"environment": "prod", // optional — e.g. "staging", "prod", "v1.12.0"
|
|
27
|
+
"expected": "200 + session cookie", // optional → folded into description
|
|
28
|
+
"actual": "500 Internal Server Error" // optional → folded into description
|
|
29
|
+
})
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
The tool returns the new bug's `id`/`key`. With no `story_id`/`openspec_change`
|
|
33
|
+
the bug is auto-anchored under the project's reserved **"Bugs"** epic+story — you
|
|
34
|
+
don't need to know the hierarchy. `report_bug` is a **reversible** internal
|
|
35
|
+
action, so active employees (including `qa-triage`) may call it without
|
|
36
|
+
break-glass.
|
|
37
|
+
|
|
38
|
+
> Requires `agent_register` first (the project binding is read from local state).
|
|
39
|
+
> A `400 repro_steps_required` means you left repro steps empty — always include
|
|
40
|
+
> concrete, numbered steps.
|
|
41
|
+
|
|
42
|
+
## Write a good bug
|
|
43
|
+
|
|
44
|
+
- **Title**: one line, specific. "Roadmap PDF export 500s on >50 entries", not "PDF broken".
|
|
45
|
+
- **repro_steps**: numbered, minimal, deterministic. Someone else should be able
|
|
46
|
+
to follow them and see the same failure.
|
|
47
|
+
- **severity** (impact, distinct from priority):
|
|
48
|
+
|
|
49
|
+
| Severity | Meaning |
|
|
50
|
+
|----------|---------|
|
|
51
|
+
| `sev1` | Critical — outage, data loss, security |
|
|
52
|
+
| `sev2` | High — major feature broken, no workaround |
|
|
53
|
+
| `sev3` | Medium — feature broken, workaround exists (default) |
|
|
54
|
+
| `sev4` | Low — cosmetic / minor |
|
|
55
|
+
|
|
56
|
+
- **environment**: where you saw it (`staging`, `prod`, a version/commit).
|
|
57
|
+
- **expected** / **actual**: the delta, when not obvious from repro steps.
|
|
58
|
+
|
|
59
|
+
## Lifecycle (don't overthink it at filing time)
|
|
60
|
+
|
|
61
|
+
Filing always starts at `bug_state=unverified`. Triage walks it forward with
|
|
62
|
+
`update_ticket` (`bug_state=...`):
|
|
63
|
+
`unverified → verified → in_progress → fixed → verified_fixed → closed`
|
|
64
|
+
(`wont_fix`/`duplicate` are terminal; `reopened` revives a terminal bug to
|
|
65
|
+
`verified`). Transitions are validated server-side — an illegal jump returns
|
|
66
|
+
`409 invalid_bug_transition`. You usually only set `unverified` (automatic) at
|
|
67
|
+
filing time and leave the rest to triage / the dashboard.
|
|
68
|
+
|
|
69
|
+
## Other paths (same result)
|
|
70
|
+
|
|
71
|
+
- **Dashboard**: the Issues page → **Open Bugs** board has a *File a bug* form.
|
|
72
|
+
- **HTTP**: `POST /api/projects/{projectId}/bugs` with `{title, repro_steps, severity?, environment?}`.
|
|
73
|
+
- **Reclassify a task you already created**: `update_ticket(type="bug", severity=..., repro_steps=...)` promotes it (defaults `bug_state=unverified`).
|
|
74
|
+
|
|
75
|
+
Full reference: the `bug-tracking-guide` doc.
|