[antowaddle]

This PR adds the fullsend scaffold files for per-repo installation.

Merge this PR to activate fullsend workflows.

Getting started

Once this PR is merged, interact with fullsend by commenting one of these slash commands. The supported target (issue and/or pull request) is shown for each:

• /fs-triage (issue or PR) — Invoke the triage agent to categorize, label, and assess an issue.
• /fs-code (issue only) — Invoke the code agent to implement a fix for an issue and open a PR.
• /fs-review (PR only) — Invoke the review agent to review a pull request.
• /fs-fix (PR only) — Invoke the fix agent to address review feedback on a pull request.
• /fs-retro (issue or PR) — Invoke the retro agent to analyze completed work and propose improvements.
• /fs-prioritize (issue or PR) — Invoke the prioritize agent to score an issue for project board ranking.

Runtime

Agents in this repository run on pi (runtime: in .fullsend/config.yaml). To change it later, edit that key, re-run fullsend github setup <owner/repo> --runtime <claude|pi|codex>, or override a single run with fullsend run --runtime. To put one agent on another runtime or model, set runtime/model/effort on its agents: entry in the same file (fullsend agent set <name> --runtime pi). See https://github.com/fullsend-ai/fullsend/blob/main/docs/runtimes.md.

[coderabbitai]

Warning

Review limit reached

This review ran on the open-source allowance, not this organization's plan, because the pull request author doesn't have an assigned seat. Waiting won't change this — ask an organization admin to assign them a seat, or add seats in Billing if every seat is already assigned, then retry.

Next included review available in 56 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 9a24f47a-49e3-4751-9c82-e8297efe7eba

Commits

Reviewing files that changed from the base of the PR and between 7ba73b0 and b2a7591.

Files selected for processing: 1

• .fullsend/config.yaml

No actionable comments were generated in the recent review.

Walkthrough

The change adds Fullsend repository configuration and GitHub Actions workflows. The workflows dispatch eligible events, process authorized /fs-fix-stop comments, and run manual prioritization.

Changes: Fullsend workflow integration

Layer / File(s)	Summary
Repository configuration and event dispatch .fullsend/config.yaml, .github/workflows/fullsend.yaml	The configuration sets Fullsend targets, runtime, roles, remote-resource URL prefixes, and inference settings. The workflow forwards eligible events to a pinned reusable workflow.
Authorized fix-stop handling .github/workflows/fullsend.yaml	For /fs-fix-stop comments, the workflow authorizes the PR author or checks collaborator permissions. If authorized, it applies the fullsend-no-fix label and posts a comment.
Manual prioritization workflow .github/workflows/prioritize.yml	The manually triggered workflow groups runs by source repository and issue or pull request. It passes event data, project settings, and secrets to a pinned reusable workflow.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Change: Other

Merge Risk: Minimal · previous review 7ba73

This PR adds Fullsend configuration and workflows that become active on merge. Review found no concrete defects in the added workflows or configuration, and the fix-stop command checks authorization before changing anything.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title "chore: initialize fullsend per-repo installation" matches the main change. The PR adds the Fullsend scaffold files (.fullsend/config.yaml, the fullsend shim workflow, and the prioritize wor…
Description check		The description states that the PR adds fullsend scaffold files for per-repo installation. It also documents the slash commands, the pi runtime setting in .fullsend/config.yaml, and how to change the …
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title "chore: initialize fullsend per-repo installation" matches the main change. The PR adds the Fullsend scaffold files (.fullsend/config.yaml, the fullsend shim workflow, and the prioritize workflow) for per-repository installation. The title is short, specific, and follows conventional commit style.

Full details: Description check

Explanation

The description states that the PR adds fullsend scaffold files for per-repo installation. It also documents the slash commands, the pi runtime setting in .fullsend/config.yaml, and how to change the runtime. These topics match the changeset, which adds the config and workflow files.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: b3bbb606-86c2-479a-b598-ecd7567bec47

Commits

Reviewing files that changed from the base of the PR and between e36439d and 7ba73b0.

Files selected for processing: 3

• .fullsend/config.yaml
• .github/workflows/fullsend.yaml
• .github/workflows/prioritize.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.