automate-github-issues

Automate GitHub Issues with Jules

You are setting up automated GitHub issue triage and resolution using parallel Jules coding agents.

What You're Setting Up

A 5-phase automated pipeline:

1. Analyze — Fetch open issues and format as structured markdown
2. Plan — A Jules session performs deep code-level triage and produces self-contained task prompts
3. Validate — Verify no two tasks modify the same file (prevents merge conflicts)
4. Dispatch — Spawn parallel Jules sessions, one per task
5. Merge — Sequential PR merge with CI validation

Setup Steps

Step 1: Copy fleet scripts to the repository

Copy the entire scripts/ directory from this skill into the target repository at scripts/fleet/:

Target structure:
scripts/fleet/
├── fleet-analyze.js
├── fleet-plan.js
├── fleet-dispatch.js
├── fleet-merge.js
├── types.js
├── prompts/
│   ├── analyze-issues.js
│   └── bootstrap.js
└── github/
    ├── git.js
    ├── issues.js
    ├── markdown.js
    └── cache-plugin.js

Step 2: Copy workflow templates

Copy the workflow files from assets/ to the repository's .github/workflows/ directory:

• assets/fleet-dispatch.yml → .github/workflows/fleet-dispatch.yml
• assets/fleet-merge.yml → .github/workflows/fleet-merge.yml

Step 3: Create environment template

Copy assets/.env.example to the repository root.

Step 4: Configure environment variables

Ensure these are set:

• JULES_API_KEY — Your Jules API key
• GITHUB_TOKEN — GitHub personal access token
• SUPABASE_URL — (optional) Supabase project URL
• SUPABASE_KEY — (optional) Supabase anon key

Step 5: Run the pipeline

Using OpenClaw tools:

jules_automate_github_issues owner=myorg repo=myrepo sourceId=<source-id>

Or run phases manually:

jules_list_sources          # Find your repo's source ID
jules_create_session ...    # Run individual phases
jules_batch_sessions ...    # Dispatch parallel agents

Manual Usage

# Fetch open issues
node scripts/fleet/fleet-analyze.js

# Plan tasks (creates a Jules planning session)
JULES_API_KEY=<key> node scripts/fleet/fleet-plan.js

# Dispatch parallel agents
JULES_API_KEY=<key> node scripts/fleet/fleet-dispatch.js

# Merge PRs sequentially
GITHUB_TOKEN=<token> node scripts/fleet/fleet-merge.js

Customization

Prompt Tuning

The analysis prompt in scripts/fleet/prompts/analyze-issues.js controls how deeply issues are investigated.

Issue Filtering

Edit scripts/fleet/github/issues.js to filter by label, milestone, or state.

Resource References

• Architecture Overview — Detailed pipeline explanation
• Troubleshooting Guide — Common issues and fixes

Troubleshooting

• "Unable to parse git remote URL": Ensure the repo has a valid GitHub remote
• Ownership conflict errors: Two tasks claim the same file — merge them manually
• CI timeout during merge: Increase maxWaitMs in fleet-merge.js