Skip to content

Chore/pysdk 000 claude doc review #9

Chore/pysdk 000 claude doc review

Chore/pysdk 000 claude doc review #9

name: "+ Claude Code / Documentation Review"
on:
pull_request:
types: [opened, synchronize, reopened]
permissions:
contents: read
pull-requests: write
jobs:
documentation-review:
name: Review requirements impact
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Analyze requirements impact
uses: anthropics/claude-code-action@v1
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
prompt: |
You are reviewing a PR to check if requirements/specs documentation needs updates.
**Your task:**
1. Run: git diff origin/${{ github.base_ref }}...HEAD
2. Identify changed modules (application, platform, wsi, bucket, dataset, etc.)
3. Use Glob to find relevant docs:
- Glob pattern: requirements/*{MODULE}*.md
- Glob pattern: specifications/SPEC-{MODULE}*.md
4. Read ONLY the relevant docs for changed modules
5. Analyze if they need updates
**Rules:**
- ONLY analyze requirements/ and specifications/ directories
- Skip files with "TEMPLATE" in name
- Use Glob and Read tools (NOT bash ls/head commands)
- Be specific about WHY docs need updating
**Post PR comment:**
## 📋 Requirements & Specifications Review
### Changed Code
- Files: [list]
- Modules: [list]
### 📝 Docs to Update
- `requirements/XXX.md`: [why]
- `specifications/XXX.md`: [why]
### ➕ New Docs Needed
- `requirements/SWR-XXX.md`: [what it should cover]
### ✅ Docs Still Accurate
- [list docs that don't need changes]
Keep it concise.
claude_args: >-
--max-turns 30
--allowed-tools Read,Glob,Grep,Bash(git:*)
--model claude-sonnet-4-5-20250929