Repository navigation
Description
What happened
PR #906 renamed all /fs-* slash command patterns to unprefixed versions in dispatch workflow files, silently breaking all slash commands. The review agent approved PR #906 without detecting this behavioral regression. PR #1063 was then needed to fix it. The dispatch workflow files (reusable-dispatch.yml, per-repo dispatch.yml) define the command routing that all agents depend on — changes to command patterns are high-impact behavioral changes that should be flagged even when the code is syntactically valid.
The failed retro agent run 25994807322 on this PR also identified this gap but could not file the proposal due to schema validation failures.
What could go better
The review agent's code-review skill does not have specific guidance for evaluating dispatch/workflow file changes. These files have implicit contracts (command patterns must match what docs, skills, and agent definitions reference) that are not captured in any schema or test — they are only discoverable through cross-referencing.
Confidence: Medium. I am confident that PR #906's regression was missed by the review agent. I am moderately confident that adding cross-reference checking guidance to the code-review skill would catch similar regressions. However, the review agent did use a subagent on PR #1063 to cross-reference /fs- patterns across the codebase, so the capability exists — it just was not applied on the original PR #906.
Uncertainty: I have not reviewed the PR #906 review agent transcript to confirm why the regression was missed. It may have been a different root cause (e.g., the review agent was not triggered, or the diff was too large).
Proposed change
In the code-review skill definition (internal/scaffold/fullsend-repo/skills/code-review.md or equivalent), add a review dimension for dispatch/workflow file changes that instructs the agent to:
- When the diff modifies comment pattern matching (e.g.,
issue_commentbody checks), cross-reference the patterns against docs, agent definitions, and skill files to verify consistency. - Flag any command pattern rename as a high-severity behavioral change requiring explicit justification.
- When workflow files change dispatch routing, verify that all referenced agent types still have matching handlers.
This is a targeted addition to the existing review dimensions, not a new skill.
Validation criteria
- A PR that renames slash command patterns in dispatch files triggers a high-severity finding about behavioral change.
- The review agent cross-references command patterns against at least agent definitions and docs when reviewing dispatch file changes.
- No false positives on dispatch file changes that do not alter command routing (e.g., adding a new command alongside existing ones).
Generated by retro agent from #1063
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsTodo
Activity
fullsend-ai-triage commentedon May 17, 2026
Re-triaged for relevance as requested. The overall architecture has moved on since May: the review-agent skills now live in fullsend-ai/agents (skills/code-review, skills/pr-review/sub-agents), not the fullsend-repo scaffold path this issue originally cited, which no longer holds skill files in that form.
More importantly, the three related issues the prior triage flagged (#890/#1911, #852, #1060) have all since been closed and merged (via PRs #1912, #1807, #1156). Together they added: consumer-completeness checks for new dispatch/enum values, generic rename/removal staleness grepping (including doc references), and mandatory findings for permission-manifest changes. That generic staleness check is a real mitigation for the PR #906 class of regression — but it reports every identifier rename, including a dispatch/workflow command-pattern rename, as a flat medium-severity finding, with no dispatch-routing-specific escalation or explicit handler-consistency verification. So the specific gap this issue calls out — treating a slash-command routing rename as the high-severity behavioral change it is — remains open.
Two other open issues touch adjacent ground without duplicating this one: #5332 (review agent should validate dispatch infrastructure fixes across all deployment modes) and #1309 (mandatory finding when a diff modifies the review agent's own behavior files). Worth coordinating with if this is picked up.
The issue is still valid and actionable, but per the requester's instruction this triage is not recommending or triggering ready-to-code — it's being left for human prioritization to decide whether the remaining, narrower scope is still worth implementing now.
Next steps:
/fs-code— agent creates a PR to implement this issue/fs-code <your instruction>— agent implements with your specific guidancePrevious run
Triage Summary
This is a well-defined feature request to add behavioral-change detection for dispatch/workflow files to the code-review skill.
Problem: PR #906 renamed slash command patterns in dispatch workflow files, breaking all slash commands. The review agent approved the change without detecting the regression, and a follow-up fix PR was needed.
Root cause hypothesis: The code-review skill has no review dimension for dispatch/workflow file changes. Command pattern renames are syntactically valid but semantically breaking, and nothing instructs the review agent to cross-reference patterns against docs, skills, and agent definitions.
Proposed change: Add guidance to the code-review skill to:
Related issues:
These are complementary, not duplicates, but coordinated implementation could reduce redundancy.
Proposed test case:
Labels: This is a feature request to enhance the review agent's code-review skill with a new review dimension. It is ready for implementation with clear scope and validation criteria.
ifireball commentedon May 26, 2026
/fs-prioritize
fullsend-ai-prioritize commentedon May 31, 2026
RICE Priority Score: 1.8
Score breakdown
Formula: (1.5 x 1.5 x 0.8) / 1 = 1.8
ralphbean commentedon Sep 21, 2026
/fs-triage lots of things have changed between when this was originally filed and now across both the https://github.com/fullsend-ai/fullsend and https://github.com/fullsend-ai/agents repos. Is this still relevant? This is a stale-issue review, not an implementation request: even if the issue is still a valid bug and has sufficient information, do not recommend or trigger ready-to-code yet. Leave it for human prioritization after confirming whether it remains relevant. Do not close a still-relevant bug merely to avoid coding it.
fullsend-ai-triage commentedon Sep 21, 2026
🤖 Finished Triage · ✅ Success · Started 4:54 PM UTC · Completed 4:59 PM UTC
Commit:
eb8149a· View workflow run →Runtime: claude · Model: sonnet → claude-sonnet-5 · Effort: high · Cost: $0.45