soly 0.1.1

Simple Transaction Builder and Sender for Solana
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66

name: PR Review

on:
  pull_request:
    types: [opened, synchronize, ready_for_review, reopened]

jobs:
  review-with-tracking:
    if: contains(github.event.pull_request.labels.*.name, 'jobtaker')
    runs-on: ${{ vars.RUNNER }}
    permissions:
      contents: read
      pull-requests: write
      id-token: write
    steps:
      - name: Checkout repository
        uses: actions/checkout@v5
        with:
          fetch-depth: 1

      - name: PR Review with Progress Tracking
        uses: anthropics/claude-code-action@v1
        with:
          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
          trigger_phrase: "@jobtaker"
          # Enable progress tracking
          track_progress: false
          # Your custom review instructions
          prompt: |
            REPO: ${{ github.repository }}
            PR NUMBER: ${{ github.event.pull_request.number }}

            Perform a comprehensive code review with the following focus areas:

            1. **Code Quality**
               - Clean code principles and best practices
               - Proper error handling and edge cases
               - Code readability and maintainability

            2. **Security**
               - Check for potential security vulnerabilities
               - Validate input sanitization
               - Review authentication/authorization logic
               - Check API documentation accuracy

            3. **Documentation**
               - Do **not** inform me to add documentation unless there is a panic or unexpected behavior that requires user attention
               - Correct the spelling and grammar of existing documentation only

            4. **Breaking API Changes**
               - Do **not** comment on breaking API changes, i have another tool for this.


            Provide detailed feedback using inline comments for specific issues.
            Use top-level comments for general observations or praise, but do not praise individual lines of code.
            Do not be shy, I am a big boy and can handle criticism gracefully. I welcome feedback and suggestions.

          # Tools for comprehensive PR review
          claude_args: |
            --allowedTools "mcp__github_inline_comment__create_inline_comment,Bash(gh pr comment:*),Bash(gh pr diff:*),Bash(gh pr view:*)"

# When track_progress is enabled:
# - Creates a tracking comment with progress checkboxes
# - Includes all PR context (comments, attachments, images)
# - Updates progress as the review proceeds
# - Marks as completed when done