Skip to content

chore: initialize fullsend per-repo installation - #175

Open
johnmcollier wants to merge 1 commit into
mainfrom
fullsend/scaffold-install
Open

chore: initialize fullsend per-repo installation#175
johnmcollier wants to merge 1 commit into
mainfrom
fullsend/scaffold-install

Conversation

@johnmcollier

Copy link
Copy Markdown
Member

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 claude (runtime: in .fullsend/config.yaml). To change it later, edit that key, re-run fullsend github setup <owner/repo> --runtime <claude|pi>, 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.

@sonarqubecloud

sonarqubecloud Bot commented Sep 3, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant