bb-create-issue
Creates a labeled handoff protocol for agents to track design artifacts and tasks.
Install
mkdir -p .claude/skills/bb-create-issue && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14431" && unzip -o skill.zip -d .claude/skills/bb-create-issue && rm skill.zipInstalls to .claude/skills/bb-create-issue
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Babel internal issue protocol — create a labeled handoff between pipeline agents. Writes designs/<name>/.handoff/<label>.md and appends to handoff_log.jsonl; best-effort gh issue create if gh available. Triggered by every guru/architect agent at handoff time.Key capabilities
- →Create labeled handoff markdown files for pipeline agents
- →Append handoff details to a JSONL log file
- →Attempt to create a GitHub issue if `gh` CLI is available
- →Derive design name from artifact path if not provided
- →Return output contract with artifact path, log path, and GitHub issue URL
How it works
This skill writes a markdown file with handoff details, appends a log entry to a JSONL file, and attempts to create a GitHub issue. It derives the design name if not explicitly provided.
Inputs & outputs
When to use bb-create-issue
- →Handing off RTL for verification
- →Logging synthesis status
- →Escalating issues to the user
About this skill
bb-create-issue
Inputs
--label <label>— one ofready-for-rtl | ready-for-verification | ready-for-synth | ready-for-pd | signoff | arch-needs-fix | rtl-needs-fix | synth-needs-fix | escalate-user | pd-rework--artifact <path>— canonical artifact path (e.g.designs/<name>/mas/mas.json)--body-file <path>(optional) — markdown body source--correlation-id <sha256>(optional) — sha256 of failing artifact for dedup (fix M-07)--design-name <name>(optional) — derived from artifact path if absent--summary <one-liner>(optional) — placed at top of body
Output Contract
| field | 值 |
|---|---|
artifact_path | designs/<name>/.handoff/<label>.md |
log_path | designs/<name>/.handoff/handoff_log.jsonl |
gh_issue_url | URL|null |
valid | bool |
4-Phase 执行
Phase 1 — derive_design_name
if --design-name absent:
parse from --artifact: matches "designs/([^/]+)/" → design_name
if no match: error "cannot derive design_name", exit 2
Phase 2 — write_handoff
LLM 直接调 Write 工具写出 designs/<design_name>/.handoff/<label>.md:
# <label>
- timestamp: <ISO 8601 Beijing time>
- artifact: <path>
- correlation_id: <sha or NA>
- summary: <one-liner or "">
- body: <body-file content or stdin>
Phase 3 — append_log
调 Bash:
mkdir -p designs/<design_name>/.handoff
LINE=$(printf '{"ts":"%s","label":"%s","artifact":"%s","correlation_id":"%s"}' \
"$(date -u +'%Y-%m-%dT%H:%M:%SZ')" "<label>" "<artifact>" "<correlation_id_or_NA>")
echo "$LINE" >> designs/<design_name>/.handoff/handoff_log.jsonl
Phase 4 — gh_best_effort
if command -v gh >/dev/null 2>&1; then
gh issue create \
--label "<label>" \
--title "<label>: <design_name>" \
--body-file designs/<design_name>/.handoff/<label>.md \
2>/dev/null || true
fi
返回 {artifact_path, log_path, gh_issue_url|null, valid:true}。
Failure Modes
- design_name 不可推导 → exit 2
- label 不在 allow-list → exit 3
- Write 失败 → 返回
{valid:false, error:"write failed"}
与 PostToolUse hook 联动
写入 <label>.md 后由 bb-hook-pipeline-advance.sh 自动提示用户下一步 agent;写 *-needs-fix.md 由 bb-hook-create-fix-issue.sh 记录 escalation。
Allow-list
ready-for-rtl, ready-for-verification, ready-for-synth, ready-for-pd, signoff,
arch-needs-fix, rtl-needs-fix, synth-needs-fix, pd-rework, escalate-user
When not to use it
- →When a handoff is not between pipeline agents
- →When a GitHub issue is not desired or the `gh` CLI is unavailable
- →When the label is not part of the allow-list
Limitations
- →The `gh issue create` is a best-effort attempt and may not always succeed
- →The label must be one of the predefined allow-list values
- →Failure to derive `design_name` will result in an error and exit
How it compares
This skill standardizes the creation and logging of handoffs across pipeline agents and integrates with GitHub issues, providing a structured approach compared to manual documentation.
Compared to similar skills
bb-create-issue side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| bb-create-issue (this skill) | 0 | 2mo | Review | Beginner |
| linear-ci-integration | 1 | 1mo | Caution | Intermediate |
| regression | 0 | 2mo | Review | Advanced |
| dev-release | 0 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
linear-ci-integration
jeremylongshore
Configure Linear CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Linear sync into your build process. Trigger with phrases like "linear CI", "linear GitHub Actions", "linear automated tests", "CI linear pipeline", "linear CI/CD".
regression
ThePalaceProject
Run a full release regression test — sets up workspace, runs automated tools, guides manual testing, generates report and Jira tickets. Use for release gates and QA cycles.
dev-release
forecast-bio
Use to drive a guided release pipeline — version bump, changelog drafting, doc review, test/lint, PR creation, tag, GitHub release, and back-merge. Mixes agent steps (the agent does them) with user-only steps (push / merge / tag, blocked by policy and printed for the user). Trigger when the user say
twig-sdlc
PolyphonyRequiem
Run the end-to-end SDLC workflow for twig development. Takes an ADO work item or natural language prompt through planning, implementation, PR lifecycle, and close-out via Conductor multi-agent orchestration. Activate when asked to implement a feature end-to-end, run the full SDLC pipeline, or orches
agent-project-board-sync
ruvnet
Agent skill for project-board-sync - invoke with $agent-project-board-sync
closeout
LaPaGaYo
|