-
Notifications
You must be signed in to change notification settings - Fork 104
211 lines (183 loc) · 8.88 KB
/
claude.yml
File metadata and controls
211 lines (183 loc) · 8.88 KB
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
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
name: Claude Code
on:
issue_comment:
types: [created]
pull_request_review_comment:
types: [created]
issues:
types: [opened, assigned]
pull_request_review:
types: [submitted]
jobs:
claude:
# Only run if comment/issue is from a repo writer (OWNER, MEMBER, or COLLABORATOR) and contains @claude
if: |
(github.event_name == 'issue_comment' &&
(github.event.comment.author_association == 'OWNER' ||
github.event.comment.author_association == 'MEMBER' ||
github.event.comment.author_association == 'COLLABORATOR') &&
contains(github.event.comment.body, '@claude')) ||
(github.event_name == 'pull_request_review_comment' &&
(github.event.comment.author_association == 'OWNER' ||
github.event.comment.author_association == 'MEMBER' ||
github.event.comment.author_association == 'COLLABORATOR') &&
contains(github.event.comment.body, '@claude')) ||
(github.event_name == 'pull_request_review' &&
(github.event.review.author_association == 'OWNER' ||
github.event.review.author_association == 'MEMBER' ||
github.event.review.author_association == 'COLLABORATOR') &&
contains(github.event.review.body, '@claude')) ||
(github.event_name == 'issues' &&
(github.event.issue.author_association == 'OWNER' ||
github.event.issue.author_association == 'MEMBER' ||
github.event.issue.author_association == 'COLLABORATOR') &&
(contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
timeout-minutes: 30
runs-on: ubuntu-latest
permissions:
contents: write
pull-requests: write
issues: write
id-token: write
actions: read
steps:
- name: Checkout repository
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: '3.11'
- name: Install uv
uses: astral-sh/setup-uv@v5
- name: Run Claude Code
id: claude
uses: anthropics/claude-code-action@v1
with:
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN || secrets.CLAUDE_MAX_OAUTH_TOKEN }}
allowed_bots: 'claude[bot]'
# This is an optional setting that allows Claude to read CI results on PRs
additional_permissions: |
actions: read
claude_args: |
--model opus
--max-turns 250
--allowedTools "Bash(git:*),Bash(./infra/pre-commit.py:*),Bash(uv:*),Bash(pytest:*),Bash(gh:*),Bash(python:*)"
--system-prompt "Always read and follow the guidelines in AGENTS.md before starting work. You always have the ability to commit and push your changes. Use your MCP tools if available, falling back to git and gh (which you have authorization for) if needed. Before submitting any changes: 1) Run ./infra/pre-commit.py --all-files --fix and fix any issues. 2) Run uv run pytest on tests relevant to your changes. Report on the test status when you provide an update. Always commit and push changes, even if you couldn't get the tests to pass. In any follow-up comments on issues or PRs, state how you tested your changes (which tests you ran and their results)."
triage:
if: |
github.event_name == 'issues' &&
github.event.action == 'opened' &&
(github.event.issue.author_association == 'OWNER' ||
github.event.issue.author_association == 'MEMBER' ||
github.event.issue.author_association == 'COLLABORATOR') &&
!contains(github.event.issue.body, '@claude') &&
!contains(github.event.issue.title, '@claude')
timeout-minutes: 60
runs-on: ubuntu-latest
permissions:
contents: write
pull-requests: write
issues: write
id-token: write
actions: read
steps:
- name: Checkout repository
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: '3.11'
- name: Install uv
uses: astral-sh/setup-uv@v5
- name: Triage Issue
uses: anthropics/claude-code-action@v1
with:
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN || secrets.CLAUDE_MAX_OAUTH_TOKEN }}
allowed_bots: 'claude[bot]'
additional_permissions: |
actions: read
prompt: |
Read AGENTS.md, .agents/skills/fix-issue/SKILL.md, and .agents/skills/pull-request/SKILL.md.
Then analyze issue #${{ github.event.issue.number }}.
## Comment management (critical)
You must use a SINGLE comment for all your progress updates. Follow this exact pattern:
1. Post your initial plan as a new comment:
`gh issue comment ${{ github.event.issue.number }} --body '🤖 **Plan:** ...'`
2. For ALL subsequent updates, edit that same comment in place:
`gh issue comment ${{ github.event.issue.number }} --edit-last --body '🤖 **Plan:** ...'`
NEVER post a second comment to update progress. Always use --edit-last after the first comment.
Check off completed items and add status notes as you progress.
Use GitHub checkbox syntax for your plan:
```
🤖 **Plan:**
- [x] Completed step
- [ ] Pending step
```
## Respond based on scope
- **Small, self-contained bug fixes (<100 lines changed)**: open a PR following the fix-issue skill workflow.
- **Anything larger** (new features, multi-module changes, design work, research questions, >100 lines):
do NOT open a PR. Instead, update your comment with root cause analysis, relevant code links,
and a proposed approach for a human to review before implementation begins.
## PR format (critical)
When opening a PR, you MUST follow .agents/skills/pull-request/SKILL.md exactly.
PR descriptions are plain text — no markdown headers, no bullet lists, no emoji,
no "## Summary" or "## Test plan" sections. Violations will be rejected.
Always produce output — either a PR or an analysis comment. Never silently exit.
claude_args: |
--model opus
--max-turns 250
--permission-mode acceptEdits
--allowedTools "Bash(git:*),Bash(./infra/pre-commit.py:*),Bash(uv:*),Bash(pytest:*),Bash(gh:*),Bash(python:*)"
--system-prompt "You can commit and push changes. Use MCP tools if available, falling back to git and gh. Always commit and push, even if tests fail. Never post multiple comments — post one comment, then use --edit-last for all updates."
autofix:
if: |
github.event_name == 'pull_request_review' &&
(github.event.review.author_association == 'OWNER' ||
github.event.review.author_association == 'MEMBER' ||
github.event.review.author_association == 'COLLABORATOR') &&
contains(github.event.review.body, 'autofix') &&
!contains(github.event.review.body, '@claude')
timeout-minutes: 30
runs-on: ubuntu-latest
permissions:
contents: write
pull-requests: write
issues: write
id-token: write
actions: read
steps:
- name: Checkout PR branch
uses: actions/checkout@v4
with:
fetch-depth: 0
ref: ${{ github.event.pull_request.head.ref }}
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: '3.11'
- name: Install uv
uses: astral-sh/setup-uv@v5
- name: Apply Autofix
uses: anthropics/claude-code-action@v1
with:
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN || secrets.CLAUDE_MAX_OAUTH_TOKEN }}
allowed_bots: 'claude[bot]'
prompt: |
PR: #${{ github.event.pull_request.number }}
REVIEW: ${{ github.event.review.body }}
A reviewer has requested autofix. Read AGENTS.md.
1. Fetch the full review with inline comments: `gh pr view ${{ github.event.pull_request.number }} --json reviews,comments`
2. Fetch inline PR review comments: `gh api repos/${{ github.repository }}/pulls/${{ github.event.pull_request.number }}/comments`
3. Apply ALL actionable changes from the review comments to the code.
4. Run ./infra/pre-commit.py --all-files --fix
5. Run uv run pytest -m 'not slow' on affected tests
6. Commit and push changes to the PR branch
7. Post a comment summarizing what was changed, prefixed with "🤖 Autofix:"
claude_args: |
--model claude-sonnet-4-6
--max-turns 100
--allowedTools "Bash(git:*),Bash(./infra/pre-commit.py:*),Bash(uv:*),Bash(pytest:*),Bash(gh:*),Bash(python:*)"