Skip to content

feat(chore): updated libs #20

feat(chore): updated libs

feat(chore): updated libs #20

name: Claude Code
on:
pull_request:
types: [opened, reopened, synchronize]
issue_comment:
types: [created]
pull_request_review_comment:
types: [created]
issues:
types: [opened, assigned]
pull_request_review:
types: [submitted]
jobs:
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') || contains(github.event.issue.title, '@claude')))
runs-on: ubuntu-latest
permissions:
contents: read
pull-requests: read
issues: read
id-token: write
steps:
- name: Checkout repository
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Run Claude Code
id: claude
uses: anthropics/claude-code-action@main
with:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
code_review:
if: github.event_name == 'pull_request'
runs-on: ubuntu-latest
permissions:
contents: read
pull-requests: read
issues: read
id-token: write
steps:
- name: Checkout repository
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Run Claude Code
id: claude
uses: anthropics/claude-code-action@main
with:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
model: claude-sonnet-4-20250514
direct_prompt: |
You are a senior product engineer.
Please provide a thorough review of this pull request.
Pay extra attention to coding standards, security practices,
test coverage, readability, maintainability, and performance.
Focus on:
- Correctness & hidden bugs (edge cases, race conditions, off-by-one, etc.)
- Performance hot-spots (Big-O, memory, DB queries, async misuse)
- Security vulnerabilities (injection, XSS, secrets exposure)
- Readability & maintainability (naming, duplication, comments)
- Test coverage gaps (suggest unit/integration tests)
- Code quality and best practices
- Potential bugs or issues
- Performance considerations
- Security implications
- Test coverage
- Documentation updates if needed
Reply with:
- *One-sentence purpose summary* of the snippet.
- A **table** with columns **Severity (Critical/High/Medium/Low)**, **Line(s)**, **Issue**, **Recommendation**.
- Concrete code samples for any non-trivial fix.
- An overall quality score **/10** and the top 3 next steps.
Provide constructive feedback with specific suggestions for improvement.
Use inline comments to highlight specific areas of concern.
Use <details> and <summary> md tags to show summary in comment and view details on click