feat: migrate agents to @relayfile/relay-helpers

Merged
KH
5mo ago
+63-178

User description

Migrates all agents off the hardcoded VFS-path writes to the ergonomic, catalog-backed clients from @relayfile/relay-helpers (0.3.29). Paths now resolve from the adapter catalog instead of string literals duplicated in each agent — so a provider path change in relayfile-adapters flows through automatically.

AgentBeforeAfter
hn-monitor, vendor-monitorwriteJsonFile(c,'slack','post','/slack/channels/…',…)slackClient().post(channel, text)
spotify-releasesslack DM pathslackClient().dm(user, text)
linearreadJsonFile/writeJsonFile linear pathslinearClient().getIssue(id) / .comment(id, body)
granolalinear create+comment (needs receipt)relayClient('linear').write('issues'|'comments', …)
reviewgithub comment/merge + slackgithubClient().comment(…) / .mergePullRequest(…) + slackClient().post(…)
repo-hygienegithub comment + slackgithubClient().comment(…) + slackClient().post(…)

Reads that aren't catalog writeback resources stay on the raw runtime VFS helpers (correct — they're not in the catalog): github pulls/meta.json + the Notion journal (repo-hygiene), the linear teams listing (granola).

Verified the github merge payload contract while migrating: the adapter reads object.method ?? object.merge_method (and snake/camel for commit fields), so mergePullRequest is compatible.

npm run typecheck clean.

Note: left an unrelated pre-existing working-tree change in review/persona.ts (a removed Daytona comment) out of this PR since I didn't author it.

🤖 Generated with Claude Code

Summary by cubic

Migrate all agents from hardcoded VFS write paths to catalog-backed clients in @relayfile/relay-helpers for cleaner APIs and automatic adapter path updates. Slack, Linear, and GitHub writebacks now use typed helpers; non-catalog reads are unchanged.

  • Refactors

    • Slack: slackClient().post(channel, text) / .dm(user, text) in hn-monitor, vendor-monitor, spotify-releases, review, repo-hygiene.
    • Linear: linearClient().getIssue(id) / .comment(id, body); granola uses relayClient('linear').write('issues'|'comments', …) to keep writeback receipts.
    • GitHub: githubClient().comment(...) and .mergePullRequest(...) in review and repo-hygiene (merge response validated via merged).
    • Reads not in the adapter catalog stay on runtime VFS (e.g., GitHub pulls/meta.json, Notion journal, Linear teams).

  • Dependencies

    • Add @relayfile/relay-helpers@^0.3.29 (pulls @relayfile/adapter-core@^0.3.29).
    • Housekeeping: .gitignore adds .claude/; npm run typecheck clean.

CodeAnt-AI Description

Move agent Slack, GitHub, and Linear actions to relay helper clients

What Changed

  • Agents now send Slack DMs and channel posts through the relay helper clients instead of writing to VFS paths directly
  • Linear issue lookup, issue creation, and issue comments now use the helper clients
  • PR review and merge actions now use the GitHub helper client, including merge confirmation before reporting success
  • Added the relay helper package to the project dependencies

Impact

✅ Fewer broken integration paths
✅ More reliable Slack, GitHub, and Linear actions
✅ Safer PR merge confirmation

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.