chore: remove Claude workflows

[KMKoushik]

Summary

• Remove the Claude Code GitHub workflow.
• Remove the Claude code review GitHub workflow.

Validation

• git diff --check
• Confirmed no .github/workflows/*claude*.yml or .github/workflows/*claude*.yaml files remain.

No build or migration commands were run.

Summary by CodeRabbit

• Chores
  • Removed an experimental automated review mode.
  • Improved review automation triggers to better distinguish review requests from other mentions.
  • Increased automation permissions where needed for review workflows.
  • Switched to the stable Claude integration and updated how prompts are supplied, including reference to agent guidance.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
unsend-marketing	Ready	Preview, Comment	May 18, 2026 1:07am

[coderabbitai]

Walkthrough

This PR refines the main Claude GitHub Actions workflow: it tightens the job's trigger expression to better detect @claude mentions across issue_comment, pull_request_review_comment, pull_request_review, and issues events; raises job permissions for contents, pull-requests, and issues from read to write; upgrades anthropics/claude-code-action from @beta to @v1; and replaces custom_instructions with claude_args that append a system prompt referencing AGENTS.md.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title 'chore: remove Claude workflows' contradicts the PR's actual objectives which involve upgrading and updating Claude workflows, not removing them.	Update the title to accurately reflect the changes, such as 'chore: upgrade Claude workflows to v1 and improve routing' or similar.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cloudflare-workers-and-pages]

Deploying usesend with    Cloudflare Pages

Latest commit:	4d9c124
Status:	✅  Deploy successful!
Preview URL:	https://8854c967.usesend.pages.dev
Branch Preview URL:	https://fix-claude-workflows.usesend.pages.dev

View logs

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/claude-code-review.yml:
- Around line 25-26: The workflow currently checks out the
contributor-controlled PR head (ref: refs/pull/${{ github.event.issue.number
}}/head) and then loads reviewer guidance from AGENTS.md, which allows a PR to
tamper with reviewer instructions; change the workflow so reviewer guidance is
loaded from a trusted branch/path instead of the PR head—e.g., keep the existing
checkout for running tests on the PR but add a separate actions/checkout
invocation (or a dedicated fetch) that checks out the repository at a pinned ref
(main or a trusted branch) and read AGENTS.md from that checked-out trusted
copy; update any steps that reference AGENTS.md to point to that trusted
workspace rather than the PR head.

In @.github/workflows/claude.yml:
- Around line 16-27: The workflow currently grants write permissions for any
event that contains '`@claude`' (the github.event_name condition block) allowing
untrusted actors to trigger repo mutations; restrict triggering and write
permissions by adding an explicit trust gate: require
github.event.*.author_association to be one of trusted values (e.g., OWNER,
MEMBER, COLLABORATOR, MAINTAINER, or a defined allowlist) in the same
conditional expressions that check for '`@claude`' (the existing github.event_name
== ... && contains(...) clauses), and remove or downgrade write permissions in
the permissions block to read-only unless that trust condition is met (or split
into two jobs/paths where only the trusted-path job has contents: write,
pull-requests: write, issues: write).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e6ab3cd5-2c3e-4aa7-903c-79bce771855a

📥 Commits

Reviewing files that changed from the base of the PR and between dad2941 and dd72bc3.

📒 Files selected for processing (2)

• .github/workflows/claude-code-review.yml
• .github/workflows/claude.yml