chore(agents): add graphite-commit agent for conventional commits

[NathanFlurry]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
rivetkit-serverless	Ready	Preview	Comment	Nov 6, 2025 5:38am

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
rivet-cloud	Ignored			Nov 6, 2025 5:38am
rivet-inspector	Ignored			Nov 6, 2025 5:38am
rivet-site	Ignored			Nov 6, 2025 5:38am

[NathanFlurry]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• chore(agents): add graphite-commit agent for conventional commits #3394 👈 (View in Graphite)
• fix(rivetkit): only trigger onStateChange and inspector updates for actor state changes #3393
• fix(rivetkit): reject all waiters in SinglePromiseQueue #3392
• fix(rivetkit): fix hibernatable websocket last seen message index to be i64 instead of u64 #3391
• fix(rivetkit): gracefully call _onStop for actors on runner shutdown #3390
• fix(rivetkit): fix initial hibernation state always being overridden with msgIndex of -1 #3389
• fix(rivetkit): fix missing duplex in nextjs in development #3388
• chore(runner): add safeguard against duplicate sockets #3387
• chore(runner): explicitly stringify tunnel messages, commands, and events #3386
• fix(runner): do not send websocket close on tunnel shutdown since pegboard-runner takes care of this #3385
• fix(rivetkit): fix actors trying to sleep after stop started #3384
• chore(runner): rename webSocketId -> requestId #3383
• chore(runner): add explicit close reason when client runner shuts down #3382
• fix(guard): fix 1006 when client closes ws connection #3381
• chore(runner): add child logger with runner id #3380
• chore(rivetkit): remove warnings for graceful runner shtudown #3379
• fix(gateway): fix gc logic #3378
• fix: boot dupe runners #3377
• fix(rocksdb): fix txn conflict checker #3376
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[pkg-pr-new]

More templates

• example-ai-agent
• example-background-jobs
• example-better-auth-external-db
• example-bots
• chat-room
• example-cloudflare-workers
• example-cloudflare-workers-hono
• example-counter
• example-counter-serverless
• example-crdt
• example-cursors
• example-cursors-raw-websocket
• example-database
• example-deno
• example-sqlite
• example-elysia
• example-express
• example-freestyle
• example-game
• example-hono
• example-hono-bun
• example-hono-react
• example-kitchen-sink
• example-next-js
• example-rate
• example-raw-fetch-handler
• example-raw-websocket-handler
• example-raw-websocket-handler-proxy
• example-react
• starter
• example-stream
• example-sync
• example-tenant
• example-trpc
• example-workflows

@rivetkit/actor

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/actor@3394

@rivetkit/cloudflare-workers

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/cloudflare-workers@3394

@rivetkit/core

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/core@3394

@rivetkit/db

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/db@3394

@rivetkit/framework-base

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/framework-base@3394

@rivetkit/next-js

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/next-js@3394

@rivetkit/react

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/react@3394

rivetkit

pnpm add https://pkg.pr.new/rivet-dev/rivet/rivetkit@3394

@rivetkit/sql-loader

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sql-loader@3394

@rivetkit/engine-runner

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner@3394

@rivetkit/engine-runner-protocol

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner-protocol@3394

commit: 45a088b

[claude]

PR Review: Add graphite-commit Agent

Overview

This PR adds a specialized Claude agent to help users create conventional commit messages for the Graphite workflow. The agent analyzes staged changes and offers commit message options following the project's conventions.

Strengths

✅ Well-structured description: The frontmatter includes excellent examples showing when this agent should be invoked, which helps the main agent understand when to delegate to this specialized agent.

✅ Follows existing patterns: The agent structure mirrors the existing rivetkit-driver-test-writer.md agent with proper frontmatter, clear responsibilities, and operational guidelines.

✅ Alignment with CLAUDE.md: The agent correctly references the Graphite CLI conventions documented in CLAUDE.md (lines 55-59), specifically using gt c -m for commits.

✅ Appropriate scoping: The agent correctly identifies common packages from the codebase structure (engine, pegboard, error, pools, gasoline, etc.) mentioned in CLAUDE.md.

✅ Good UX design: The 3-option approach with explanations is user-friendly and provides flexibility while maintaining consistency.

Issues and Recommendations

1. Critical: Missing AskUserQuestion Tool Context

Issue: Line 38 instructs the agent to "Use the AskUserQuestion tool" but this may not be available in all contexts or may need specific formatting.

Recommendation: Verify that the AskUserQuestion tool is available to agents, or consider using a different interaction pattern (e.g., direct output with instructions for the user to respond).

2. Potential Race Condition

Issue: Lines 12 and 47 emphasize "DO NOT run git log or check recent commit history" but don't explain why this restriction exists.

Recommendation: Add a brief explanation (e.g., "to avoid confusion with unrelated commits" or "to keep the agent focused only on current changes").

3. Error Handling Missing

Issue: The agent doesn't specify what to do if:

• git diff --cached returns empty (no staged changes)
• gt c -m fails
• Staged changes contain merge conflicts

Recommendation: Add error handling guidelines, such as:

### Error Scenarios
- If `git diff --cached` is empty: Inform user no changes are staged and suggest `git add`
- If `gt c` fails: Show the error and suggest checking Graphite setup
- If merge conflicts exist: Advise resolving conflicts before committing

4. Quote Escaping in Command

Issue: Line 40 shows gt c -m 'your-message' with single quotes, but if the commit message contains single quotes, this will break.

Recommendation: Specify using double quotes or proper escaping:

gt c -m "your-message"

5. Consistency with Main System Prompt

Issue: The main Claude Code system (per CLAUDE.md) includes Claude attribution in commits ("🤖 Generated with Claude Code" + "Co-Authored-By: Claude"), but line 44 explicitly states "DO NOT mention Claude or co-authors."

Recommendation: This appears intentional for Graphite workflow, but consider adding a comment explaining why this differs from standard git commit behavior to avoid confusion:

- The commit should be ONLY the single-line conventional commit. DO NOT mention Claude or co-authors.
  (Note: This differs from standard git commits to maintain clean Graphite commit history)

6. Character Limit Suggestion

Issue: Line 34 says "Keep it under 72 characters when possible" but this is a soft suggestion.

Recommendation: Consider being more explicit about when it's acceptable to exceed 72 characters (e.g., "when technical terms or package names make it unavoidable").

7. Testing Consideration

Issue: No mention of how to test this agent works correctly.

Recommendation: Consider adding a testing section or example usage scenario to help validate the agent behaves as expected.

Minor Suggestions

• Line 2: The description field is quite long. Consider if this could be shortened while maintaining the examples separately in the body.
• Line 18: "Scripts and tooling" is a bit vague - consider adding examples like scripts/cargo, .claude, etc.
• Line 50: "If uncertain about the scope or type" - provide specific examples of uncertainty scenarios.

Security Considerations

✅ No security concerns identified. The agent only reads staged changes and creates commits, which are standard development operations.

Performance Considerations

✅ The agent appropriately avoids expensive operations like full repository scans and focuses on staged changes only.

Test Coverage

⚠️ Not Applicable: This is configuration/documentation for an agent. Consider manual testing scenarios:

1. Test with changes to a single package
2. Test with changes spanning multiple packages
3. Test with no staged changes
4. Test with very long file paths or complex changes

Conclusion

This is a well-designed agent that will improve developer workflow consistency. The main concerns are around error handling and tool availability. With the recommended improvements, this will be a valuable addition to the project.

Recommendation: Approve with minor revisions suggested above.

---

Rating: 8/10 - Solid implementation with room for improved robustness.

[graphite-app]

Merge activity

• Nov 6, 5:47 AM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Nov 6, 5:48 AM UTC: CI is running for this pull request on a draft pull request (#3395) due to your merge queue CI optimization settings.
• Nov 6, 5:50 AM UTC: Merged by the Graphite merge queue via draft PR: #3395.