feat: register all 6 agents from fullsend-ai/agents

[ggallen]

Summary

• Register 5 newly extracted agents (code, fix, review, retro, prioritize) from fullsend-ai/agents
• Update triage agent to the latest SHA (bc7beaa9a57a) matching the other agents
• All 6 agents pinned to the same commit with #sha256= integrity hashes

Follows the extraction in fullsend-ai/agents#12 and plan Step 6 from ADR 0058.

Test plan

• fullsend agent list shows all 6 agents resolving correctly
• Smoke test each agent after merge (triage, code, review, fix, retro, prioritize)

🤖 Generated with Claude Code

[qodo-code-review]

PR Summary by Qodo

Register extracted Fullsend agents pinned to a single commit with integrity hashes

✨ Enhancement ⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Register code, fix, review, retro, and prioritize agents from fullsend-ai/agents.
• Update triage agent to the same pinned commit SHA as the others.
• Pin all agent sources with sha256 integrity hashes for reproducible resolution.

Diagram

graph TD
  cfg["config.yaml"] --> loader["Agent loader"] --> gh["raw.githubusercontent.com/fullsend-ai/agents"] --> registry["6 agent YAMLs"]
  registry --> cli["fullsend agent list"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Pin to a release tag (or semver) instead of a commit SHA

• ➕ More human-readable and communicable versioning
• ➕ Easier to roll forward/backward with explicit releases
• ➖ Requires a disciplined release process in fullsend-ai/agents
• ➖ Still needs integrity verification to avoid supply-chain drift

2. Vendor the agent YAMLs into this repo

• ➕ No network dependency at runtime
• ➕ Standard code review and provenance within the repo
• ➖ Duplication and manual sync burden with upstream
• ➖ Larger repo footprint; harder to track upstream provenance

Recommendation: The PR’s approach (single commit SHA pinned for all agents plus sha256 integrity hashes) is the best default for reproducibility and supply-chain safety. If/when upstream provides stable release tags, consider switching pins from commit SHA to tagged releases while keeping sha256 verification.

Files changed (1) +6 / -1

Other (1) +6 / -1

config.yamlRegister 5 new agents and align triage to a single pinned commit +6/-1

Register 5 new agents and align triage to a single pinned commit

• Replaces the triage agent source with a newer pinned commit and sha256 hash. Adds code, fix, review, retro, and prioritize agents, all pinned to the same fullsend-ai/agents commit for consistent resolution.

config.yaml

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 4 rules

1. Docs agent format drift 🐞 Bug ⚙ Maintainability

Description

config.yaml now registers agents via agents[].source remote YAML URLs, but internal docs still
instruct registering agents by adding explicit role/name/slug entries. This documentation drift
can cause future config edits to be made in the wrong format and silently break agent registration.

Code

config.yaml[R33-38]

+    - source: https://raw.githubusercontent.com/fullsend-ai/agents/bc7beaa9a57aed031c6ef1d9755c1f2cfca516da/harness/triage.yaml#sha256=f56cbb0a3c1cb71563aa1b2fb80ca9ecb922e4c832f886e8154e2e9beb6b56c6
+    - source: https://raw.githubusercontent.com/fullsend-ai/agents/bc7beaa9a57aed031c6ef1d9755c1f2cfca516da/harness/code.yaml#sha256=050382941bb4c4a3dad5f00253de854684c0d22dd8cc1ca0a548079774470aad
+    - source: https://raw.githubusercontent.com/fullsend-ai/agents/bc7beaa9a57aed031c6ef1d9755c1f2cfca516da/harness/fix.yaml#sha256=f966f0b8cd9b58289f19b446cfc4fd343c9079d9c9acee0260824b57e896e068
+    - source: https://raw.githubusercontent.com/fullsend-ai/agents/bc7beaa9a57aed031c6ef1d9755c1f2cfca516da/harness/review.yaml#sha256=08456e534c7d1251b3a3b2bc1236643403809ecab27832c273764769f219a45b
+    - source: https://raw.githubusercontent.com/fullsend-ai/agents/bc7beaa9a57aed031c6ef1d9755c1f2cfca516da/harness/retro.yaml#sha256=8be74d42aa94ed0083fd1a915f9903435d797b801b3866acd7e8249830388835
+    - source: https://raw.githubusercontent.com/fullsend-ai/agents/bc7beaa9a57aed031c6ef1d9755c1f2cfca516da/harness/prioritize.yaml#sha256=21cf62dce54fce3ae23cf5e3dfe901d03b69bc5e91533288ffa772187b24e95d

Evidence

The config now clearly uses agents[].source URL entries, while docs still describe/teach an inline
role/name/slug agent registration format under agents:.

config.yaml[32-38]
docs/scribe-agent.md[217-230]
docs/superpowers/plans/2026-05-01-prioritize-agent.md[967-980]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`config.yaml` switched to registering agents via remote `agents[].source` URLs, but docs still describe the older inline registration format (`role`, `name`, `slug`). This mismatch can mislead maintainers and lead to incorrect future edits.

## Issue Context
- The current config uses:
 - `agents: - source: https://raw.githubusercontent.com/.../harness/<agent>.yaml#sha256=...`
- Some docs still claim or show examples where `agents:` entries are inline objects with `role/name/slug`.

## Fix Focus Areas
- docs/scribe-agent.md[217-230]
- docs/superpowers/plans/2026-05-01-prioritize-agent.md[967-980]

## Suggested change
- Update the referenced docs to explicitly describe the new `agents[].source` registration method (and optionally note the old inline `role/name/slug` format as deprecated/outdated if it still exists elsewhere).
- Replace the inline YAML example under `agents:` with a `source:` example (mirroring the current `config.yaml`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

1. Docs agent format drift 🐞 Bug ⚙ Maintainability

config.yaml now registers agents via agents[].source remote YAML URLs, but internal docs still
instruct registering agents by adding explicit role/name/slug entries. This documentation drift
can cause future config edits to be made in the wrong format and silently break agent registration.

Agent Prompt

## Issue description
`config.yaml` switched to registering agents via remote `agents[].source` URLs, but docs still describe the older inline registration format (`role`, `name`, `slug`). This mismatch can mislead maintainers and lead to incorrect future edits.

## Issue Context
- The current config uses:
  - `agents: - source: https://raw.githubusercontent.com/.../harness/<agent>.yaml#sha256=...`
- Some docs still claim or show examples where `agents:` entries are inline objects with `role/name/slug`.

## Fix Focus Areas
- docs/scribe-agent.md[217-230]
- docs/superpowers/plans/2026-05-01-prioritize-agent.md[967-980]

## Suggested change
- Update the referenced docs to explicitly describe the new `agents[].source` registration method (and optionally note the old inline `role/name/slug` format as deprecated/outdated if it still exists elsewhere).
- Replace the inline YAML example under `agents:` with a `source:` example (mirroring the current `config.yaml`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools