davila7/claude-code-templates/github-workflow-automation

🔧 GitHub Workflow Automation

Patterns for automating GitHub workflows with AI assistance, inspired by Gemini CLI and modern DevOps practices.

When to Use This Skill

Use this skill when:

• Automating PR reviews with AI
• Setting up issue triage automation
• Creating GitHub Actions workflows
• Integrating AI into CI/CD pipelines
• Automating Git operations (rebases, cherry-picks)

1. Automated PR Review

1.1 PR Review Action

# .github/workflows/ai-review.yml
name: AI Code Review
 
on:
  pull_request:
    types: [opened, synchronize]
 
jobs:
  review:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
 
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
 
      - name: Get changed files
        id: changed
        run: |
          files=$(git diff --name-only origin/${{ github.base_ref }}...HEAD)
          echo "files<<EOF" >> $GITHUB_OUTPUT
          echo "$files" >> $GITHUB_OUTPUT
          echo "EOF" >> $GITHUB_OUTPUT
 
      - name: Get diff
        id: diff
        run: |
          diff=$(git diff origin/${{ github.base_ref }}...HEAD)
          echo "diff<<EOF" >> $GITHUB_OUTPUT
          echo "$diff" >> $GITHUB_OUTPUT
          echo "EOF" >> $GITHUB_OUTPUT
 
      - name: AI Review
        uses: actions/github-script@v7
        with:
          script: |
            const { Anthropic } = require('@anthropic-ai/sdk');
            const client = new Anthropic({ apiKey: process.env.ANTHROPIC_API_KEY });
 
            const response = await client.messages.create({
              model: "claude-sonnet-4-6",
              max_tokens: 4096,
              messages: [{
                role: "user",
                content: `Review this PR diff and provide feedback:
                
                Changed files: ${{ steps.changed.outputs.files }}
                
                Diff:
                ${{ steps.diff.outputs.diff }}
                
                Provide:
                1. Summary of changes
                2. Potential issues or bugs
                3. Suggestions for improvement
                4. Security concerns if any
                
                Format as GitHub markdown.`
              }]
            });
 
            await github.rest.pulls.createReview({
              owner: context.repo.owner,
              repo: context.repo.repo,
              pull_number: context.issue.number,
              body: response.content[0].text,
              event: 'COMMENT'
            });
        env:
          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}

1.2 Review Comment Patterns

# AI Review Structure
 
## 📋 Summary
 
Brief description of what this PR does.
 
## ✅ What looks good
 
- Well-structured code
- Good test coverage
- Clear naming conventions
 
## ⚠️ Potential Issues
 
1. **Line 42**: Possible null pointer exception
   ```javascript
   // Current
   user.profile.name;
   // Suggested
   user?.profile?.name ?? "Unknown";
   ```

1. Line 78: Consider error handling

``javascript // Add try-catch or .catch() ``

💡 Suggestions

• Consider extracting the validation logic into a separate function
• Add JSDoc comments for public methods

🔒 Security Notes

• No sensitive data exposure detected
• API key handling looks correct

 
### 1.3 Focused Reviews
 

Review only specific file types

• name: Filter code files

run: | files=$(git diff --name-only origin/${{ github.base_ref }}...HEAD | \ grep -E '\.(ts|tsx|js|jsx|py|go)$' || true) echo "code_files=$files" >> $GITHUB_OUTPUT

Review with context

• name: AI Review with context

run: | # Include relevant context files context="" for file in ${{ steps.changed.outputs.files }}; do if [[ -f "$file" ]]; then context+="=== $file ===\n$(cat $file)\n\n" fi done

# Send to AI with full file context

 
---
 
## 2. Issue Triage Automation
 
### 2.1 Auto-label Issues
 

.github/workflows/issue-triage.yml

name: Issue Triage

on: issues: types: [opened]

jobs: triage: runs-on: ubuntu-latest permissions: issues: write

steps:

• name: Analyze issue

uses: actions/github-script@v7 with: script: | const issue = context.payload.issue;

// Call AI to analyze const analysis = await analyzeIssue(issue.title, issue.body);

// Apply labels const labels = [];

if (analysis.type === 'bug') { labels.push('bug'); if (analysis.severity === 'high') labels.push('priority: high'); } else if (analysis.type === 'feature') { labels.push('enhancement'); } else if (analysis.type === 'question') { labels.push('question'); }

if (analysis.area) { labels.push(area: ${analysis.area}); }

await github.rest.issues.addLabels({ owner: context.repo.owner, repo: context.repo.repo, issue_number: issue.number, labels: labels });

// Add initial response if (analysis.type === 'bug' && !analysis.hasReproSteps) { await github.rest.issues.createComment({ owner: context.repo.owner, repo: context.repo.repo, issue_number: issue.number, body: `Thanks for reporting this issue!

To help us investigate, could you please provide:

• Steps to reproduce the issue
• Expected behavior
• Actual behavior
• Environment (OS, version, etc.)

This will help us resolve your issue faster. 🙏` }); }

 
### 2.2 Issue Analysis Prompt
 

const TRIAGE_PROMPT = ` Analyze this GitHub issue and classify it:

Title: {title} Body: {body}

Return JSON with: { "type": "bug" | "feature" | "question" | "docs" | "other", "severity": "low" | "medium" | "high" | "critical", "area": "frontend" | "backend" | "api" | "docs" | "ci" | "other", "summary": "one-line summary", "hasReproSteps": boolean, "isFirstContribution": boolean, "suggestedLabels": ["label1", "label2"], "suggestedAssignees": ["username"] // based on area expertise } `;

 
### 2.3 Stale Issue Management
 

.github/workflows/stale.yml

name: Manage Stale Issues

on: schedule:

• cron: "0 0 *" # Daily

jobs: stale: runs-on: ubuntu-latest steps:

• uses: actions/stale@v9

with: stale-issue-message: | This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.

If this issue is still relevant:

• Add a comment with an update
• Remove the stale label

Thank you for your contributions! 🙏

stale-pr-message: | This PR has been automatically marked as stale. Please update it or it will be closed in 14 days.

days-before-stale: 60 days-before-close: 14 stale-issue-label: "stale" stale-pr-label: "stale" exempt-issue-labels: "pinned,security,in-progress" exempt-pr-labels: "pinned,security"

 
---
 
## 3. CI/CD Integration
 
### 3.1 Smart Test Selection
 

.github/workflows/smart-tests.yml

name: Smart Test Selection

on: pull_request:

jobs: analyze: runs-on: ubuntu-latest outputs: test_suites: ${{ steps.analyze.outputs.suites }}

steps:

• uses: actions/checkout@v4

with: fetch-depth: 0

• name: Analyze changes

id: analyze run: | # Get changed files changed=$(git diff --name-only origin/${{ github.base_ref }}...HEAD)

# Determine which test suites to run suites="[]"

if echo "$changed" | grep -q "^src/api/"; then suites=$(echo $suites | jq '. + ["api"]') fi

if echo "$changed" | grep -q "^src/frontend/"; then suites=$(echo $suites | jq '. + ["frontend"]') fi

if echo "$changed" | grep -q "^src/database/"; then suites=$(echo $suites | jq '. + ["database", "api"]') fi

# If nothing specific, run all if [ "$suites" = "[]" ]; then suites='["all"]' fi

echo "suites=$suites" >> $GITHUB_OUTPUT

test: needs: analyze runs-on: ubuntu-latest strategy: matrix: suite: ${{ fromJson(needs.analyze.outputs.test_suites) }}

steps:

• uses: actions/checkout@v4

• name: Run tests

run: | if [ "${{ matrix.suite }}" = "all" ]; then npm test else npm test -- --suite ${{ matrix.suite }} fi

 
### 3.2 Deployment with AI Validation
 

.github/workflows/deploy.yml

name: Deploy with AI Validation

on: push: branches: [main]

jobs: validate: runs-on: ubuntu-latest steps:

• uses: actions/checkout@v4

• name: Get deployment changes

id: changes run: | # Get commits since last deployment last_deploy=$(git describe --tags --abbrev=0 2>/dev/null || echo "") if [ -n "$last_deploy" ]; then changes=$(git log --oneline $last_deploy..HEAD) else changes=$(git log --oneline -10) fi echo "changes<<EOF" >> $GITHUB_OUTPUT echo "$changes" >> $GITHUB_OUTPUT echo "EOF" >> $GITHUB_OUTPUT

• name: AI Risk Assessment

id: assess uses: actions/github-script@v7 with: script: | // Analyze changes for deployment risk const prompt = ` Analyze these changes for deployment risk:

${process.env.CHANGES}

Return JSON: { "riskLevel": "low" | "medium" | "high", "concerns": ["concern1", "concern2"], "recommendations": ["rec1", "rec2"], "requiresManualApproval": boolean } `;

// Call AI and parse response const analysis = await callAI(prompt);

if (analysis.riskLevel === 'high') { core.setFailed('High-risk deployment detected. Manual review required.'); }

return analysis; env: CHANGES: ${{ steps.changes.outputs.changes }}

deploy: needs: validate runs-on: ubuntu-latest environment: production steps:

• name: Deploy

run: | echo "Deploying to production..." # Deployment commands here

 
### 3.3 Rollback Automation
 

.github/workflows/rollback.yml

name: Automated Rollback

on: workflow_dispatch: inputs: reason: description: "Reason for rollback" required: true

jobs: rollback: runs-on: ubuntu-latest steps:

• uses: actions/checkout@v4

with: fetch-depth: 0

• name: Find last stable version

id: stable run: | # Find last successful deployment stable=$(git tag -l 'v*' --sort=-version:refname | head -1) echo "version=$stable" >> $GITHUB_OUTPUT

• name: Rollback

run: | git checkout ${{ steps.stable.outputs.version }} # Deploy stable version npm run deploy