Skip to content

Bump the dev-dependencies group across 1 directory with 3 updates #25

Bump the dev-dependencies group across 1 directory with 3 updates

Bump the dev-dependencies group across 1 directory with 3 updates #25

Workflow file for this run

# The AI that reviews your code at 3am while you sleep. Burns tokens, not bridges.
name: Claude Code
on:
issue_comment:
types: [created]
pull_request_review_comment:
types: [created]
issues:
types: [opened, assigned, labeled]
pull_request_review:
types: [submitted]
pull_request:
types: [opened, synchronize]
concurrency:
group: claude-${{ github.event.pull_request.number || github.event.issue.number || github.run_id }}
cancel-in-progress: false
jobs:
# Summon the AI by whispering @claude into the void
claude:
name: Claude
if: |
(github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
(github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude')) ||
(github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude')) ||
(github.event_name == 'issues' && contains(github.event.issue.body, '@claude'))
runs-on: ubuntu-latest
permissions:
contents: read
pull-requests: write
issues: write
id-token: write
steps:
- name: Checkout
uses: actions/checkout@v4
with:
fetch-depth: 1
- name: Run Claude
uses: anthropics/claude-code-action@v1
with:
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
# Every PR gets judged. No exceptions. No feelings.
review:
name: AI Review
if: github.event_name == 'pull_request'
runs-on: ubuntu-latest
permissions:
contents: read
pull-requests: write
issues: write
id-token: write
steps:
- name: Checkout
uses: actions/checkout@v4
with:
fetch-depth: 1
- name: Review PR
uses: anthropics/claude-code-action@v1
with:
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
track_progress: "true"
prompt: |
You are a code reviewer for Vibe Code.
Your voice: dry British sarcasm, cheeky cynicism, zero LinkedIn energy.
Think "shitposter with a philosophy minor" meets senior engineer who's seen things.
Review this PR. Focus on:
- Bugs, logic errors, things that'll break at 2am on a Friday
- Code style (check CLAUDE.md for project conventions)
- Security issues (hardcoded secrets, injection, the OWASP greatest hits)
- Missing tests for non-trivial changes
Rules:
- Skip the praise. "Great work!" is for LinkedIn. Flag what matters.
- One-liners over essays. If you need a paragraph, something's very wrong.
- If the PR is genuinely clean, say so in one dry sentence and move on.
- Don't nitpick formatting -- the linter handles that. You're better than a linter.
- Be helpful, not hostile. Roast the code, not the author.