Repository navigation
chore: add installed slack-comms persona - #151
Conversation
|
Your free trial PR review limit of 300 PRs has been reached. Please upgrade your plan to continue using CodeAnt AI. |
|
Warning Review limit reached
More reviews will be available in 1 minute and 33 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces the slack-comms persona, adding its configuration file (slack-comms.json) and operational guidelines (slack-comms.md). The persona serves as a comms-only Slack liaison that handles inbound and outbound messages via relayfile writebacks. Feedback on the pull request points out an error in the documented path for threaded replies, which should use threads instead of messages to align with the writeback command root matching logic.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| - **Threaded reply** (the default): write to | ||
| `messages/<thread_ts>/replies/<name>.json` and include a `thread_ts` field. |
There was a problem hiding this comment.
The threaded reply path is described as messages/<thread_ts>/replies/<name>.json. However, according to the writeback command root matching logic in src/main/slack-writeback-command-roots.ts, the expected path segment for threads is threads, not messages (i.e., threads/<thread_ts>/replies/<name>.json). Writing to messages/.../replies/... will fail to match the writeback command root and won't be processed correctly.
| - **Threaded reply** (the default): write to | |
| `messages/<thread_ts>/replies/<name>.json` and include a `thread_ts` field. | |
| - **Threaded reply** (the default): write to | |
| `threads/<thread_ts>/replies/<name>.json` and include a `thread_ts` field. |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| "optional": true | ||
| } | ||
| }, | ||
| "agentsMd": "__assets/slack-comms/slack-comms.md" |
There was a problem hiding this comment.
🚩 agentsMd field vs claudeMdContent pattern
The new persona uses "agentsMd": "__assets/slack-comms/slack-comms.md" (a file-path reference) while the existing autonomous-actor.json uses claudeMdContent with inline content. The spec document at docs/specs/workforce-persona-agents.md:38 mentions claudeMdContent / agentsMdContent as known field names. agentsMd appears to be a file-path variant (as opposed to inline agentsMdContent). Since the agentworkforce CLI (^3.0.50) processes these persona definitions externally, and the referenced file exists at the correct relative path, this is likely a supported alternate form. Cannot fully verify without access to the agentworkforce CLI's schema documentation.
Was this helpful? React with 👍 or 👎 to provide feedback.
| "integrations": { | ||
| "slack": {} |
There was a problem hiding this comment.
🚩 integrations field is unique to this persona
The "integrations": { "slack": {} } field at line 8-9 does not appear in any other persona JSON in this repository. The other personas (autonomous-actor, pear-auth-specialist, settings-panel-hero) don't declare integrations. This is likely a valid field that tells the agentworkforce CLI to provision the Slack integration for this persona, but it's a pattern not previously seen in this repo's persona files. If the agentworkforce CLI doesn't recognize this field, it would be silently ignored rather than causing an error.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
Your free trial PR review limit of 300 PRs has been reached. Please upgrade your plan to continue using CodeAnt AI. |
|
✅ pr-reviewer applied fixes — committed and pushed Implemented the PR fixes in the checkout:
Validated locally:
Bot comments reviewed from PR #151: Gemini’s path issue and Devin’s sidecar concern are addressed; Devin’s integrations concern was validated as supported. Current PR metadata showed mergeable true, and current remote checks were green, but these local edits still need the harness/cloud commit and the resulting checks before the PR can be considered ready. |
|
Your free trial PR review limit of 300 PRs has been reached. Please upgrade your plan to continue using CodeAnt AI. |
Commits the slack-comms persona installed via `agentworkforce install @agentworkforce/persona-slack-comms`, matching the other tracked personas in this directory. Comms-only Slack liaison (Sonnet), 5 relayfile/relay skills, stay-in-lane operating spec. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
So `npm run personas:refresh` pulls upstream updates to the published @agentworkforce/persona-slack-comms pack (mirrors cloud's personas:refresh pattern), not just autonomous-actor. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
099827b to
ba7f283
Compare
|
Your free trial PR review limit of 300 PRs has been reached. Please upgrade your plan to continue using CodeAnt AI. |
|
✅ pr-reviewer applied fixes — committed and pushed Reviewed PR #151 against the provided diff and current checkout. Fixed:
Verified locally:
I did not print |
What
Adds the
slack-commspersona to pear's tracked personas (.agentworkforce/workforce/personas/), matching the existing tracked personas (autonomous-actor, pear-auth-specialist, settings-panel-hero).How it got here
Installed via
agentworkforce install @agentworkforce/persona-slack-comms(published from AgentWorkforce/workforce#213). This PR commits the installed artifacts so the persona is version-controlled in pear (and survives respawn).Contents
slack-comms.json— harnessclaude/ modelclaude-sonnet-4-6; 5 skills (setting-up-relayfile, workspace-layout, writeback-as-files, orchestrating-agent-relay, persona-relayfile-mount).__assets/slack-comms/slack-comms.md— operating spec: comms-only liaison, threaded brief-yet-detailed replies,<@ID>mentions, writeback flush verification, OOB-read drop-guard, and stay-in-lane discipline (route issues to the coordinator; don't diagnose/fix/task workers directly).🤖 Generated with Claude Code