Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
google-labs-code avatar

Automate Github Issues

  • 701 installs
  • 84 repo stars
  • Updated June 4, 2026
  • google-labs-code/jules-skills

automate-github-issues is a Claude Code skill that schedules Jules fleet sessions to fetch open GitHub issues and dispatch parallel coding agents for developers who want issue backlog work automated without manual triage

About

automate-github-issues is a Claude Code skill from google-labs-code/jules-skills that orchestrates Jules fleet sessions against a GitHub repository's open issues. Configuration requires JULES_API_KEY for dispatching sessions and GITHUB_TOKEN with repo access for issue fetching and optional PR merge, with an optional FLEET_BASE_BRANCH override defaulting to the current branch. Developers reach for this skill when open issues should fan out to parallel Jules agents instead of sitting in a manual queue. The workflow copies environment variables from the bundled .env template, then schedules fleet runs that pull issues and assign coding agents automatically. It fits teams experimenting with agent fleets on maintenance backlogs, dependency bumps, or labeled good-first-issue queues where Jules can propose patches.

  • Daily cron or manual workflow_dispatch Fleet Dispatch GitHub Action
  • Requires JULES_API_KEY and GITHUB_TOKEN for sessions, issue fetch, and PR merge
  • Optional FLEET_BASE_BRANCH override for fleet session base branch
  • Concurrency group fleet-dispatch prevents overlapping fleet runs
  • Bootstrap prompt drives in-repo fleet scripts to analyze and dispatch on open issues

Automate Github Issues by the numbers

  • 701 all-time installs (skills.sh)
  • Ranked #356 of 2,742 Automation & Workflows skills by installs in the Skillselion catalog
  • Security screen: CRITICAL risk (skills.sh audit)
  • Data as of Jul 27, 2026 (Skillselion catalog sync)
npx skills add https://github.com/google-labs-code/jules-skills --skill automate-github-issues

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs701
repo stars84
Security audit1 / 3 scanners passed
Last updatedJune 4, 2026
Repositorygoogle-labs-code/jules-skills

How do you automate GitHub issues with Jules?

Schedule Jules fleet sessions that fetch open GitHub issues and dispatch parallel coding agents to work them without manual triage.

Who is it for?

Developers operating Google Jules with repo-scoped tokens who want parallel agents to chew through labeled GitHub issue backlogs automatically.

Skip if: Skip automate-github-issues when issues need human design review first, Jules API access is unavailable, or GitHub tokens lack repo write permissions.

When should I use this skill?

The developer wants Jules fleet sessions to fetch GitHub issues and run parallel coding agents without manual issue-by-issue assignment.

What you get

Scheduled Jules fleet sessions, dispatched parallel agent runs per open issue, and optional PR merges from the configured base branch.

  • Jules fleet session schedule
  • Parallel agent dispatches per issue

By the numbers

  • Requires 2 mandatory environment variables: JULES_API_KEY and GITHUB_TOKEN
  • Supports 1 optional FLEET_BASE_BRANCH override for fleet session targeting

Files

SKILL.mdMarkdownGitHub ↗

Automate GitHub Issues with Jules

You are setting up a repository to automatically analyze open GitHub issues, plan implementation tasks, and dispatch parallel Jules coding agents to fix them.

What You're Setting Up

A 5-phase automated pipeline that runs via GitHub Actions (or locally):

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.ts
├── fleet-plan.ts
├── fleet-dispatch.ts
├── fleet-merge.ts
├── types.ts
├── prompts/
│   ├── analyze-issues.ts
│   └── bootstrap.ts
└── github/
    ├── git.ts
    ├── issues.ts
    ├── markdown.ts
    └── cache-plugin.ts
Important: Preserve the directory structure exactly. The scripts use relative imports between files.

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 a package.json for the fleet scripts

Create scripts/fleet/package.json with the required dependencies:

{
  "name": "fleet-scripts",
  "private": true,
  "type": "module",
  "dependencies": {
    "@google/jules-sdk": "^0.1.0",
    "octokit": "^4.1.0",
    "find-up": "^7.0.0"
  },
  "devDependencies": {
    "@types/bun": "^1.2.0"
  }
}

Step 4: Create environment template

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

Step 5: Install dependencies

cd scripts/fleet && bun install

Step 6: Print next steps for the user

Tell the user they need to: 1. Add JULES_API_KEY as a GitHub repository secret (Settings → Secrets → Actions) 2. GITHUB_TOKEN is provided automatically by GitHub Actions 3. Customize the cron schedule in .github/workflows/fleet-dispatch.yml (default: daily 6am UTC) 4. Commit all generated files

Manual Usage

After setup, the user can run the pipeline locally:

cd scripts/fleet

# Fetch open issues
bun fleet-analyze.ts

# Plan tasks (creates a Jules planning session)
JULES_API_KEY=<key> bun fleet-plan.ts

# Dispatch parallel agents
JULES_API_KEY=<key> bun fleet-dispatch.ts

# Merge PRs sequentially
GITHUB_TOKEN=<token> bun fleet-merge.ts

Customization

Prompt Tuning

The analysis prompt in scripts/fleet/prompts/analyze-issues.ts controls how deeply issues are investigated. Users can adjust:

  • Root cause analysis depth
  • Solution implementation detail level
  • Merge conflict avoidance rules
  • File ownership constraints

Issue Filtering

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

Resource References

  • Architecture Overview — Detailed explanation of the 5-phase pipeline

Troubleshooting

  • "Unable to parse git remote URL": Ensure the repo has a valid GitHub remote (git remote get-url origin)
  • Ownership conflict errors: Two tasks claim the same file. Adjust the task JSON or merge them manually.
  • CI timeout during merge: Increase maxWaitMs in fleet-merge.ts (default: 10 minutes)
  • Bun not found: Install Bun: curl -fsSL https://bun.sh/install | bash

Related skills

FAQ

What environment variables does automate-github-issues require?

automate-github-issues requires JULES_API_KEY to dispatch Jules sessions and GITHUB_TOKEN with repository access for fetching issues and merging PRs. FLEET_BASE_BRANCH optionally overrides the default base branch for fleet runs.

What does automate-github-issues do with open GitHub issues?

automate-github-issues schedules Jules fleet sessions that fetch open GitHub issues and dispatch parallel coding agents to work them. The skill removes manual triage when fleet automation is configured with valid API credentials.

Is Automate Github Issues safe to install?

skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Automation & Workflowsintegrationsgit

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.