automate-github-issues
Set up automated GitHub issue triage and resolution using parallel Jules coding agents
- License 许可
- MIT
- 最近更新
- 2026-11-05
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- automate-github-issues
- description
- Set up automated GitHub issue triage and resolution using parallel Jules coding agents
- allowed-tools
- [ "Bash", "Read", "Write" ]
02 资源文件 20
- 资产文件assets/.env.example391 B
- 资产文件assets/fleet-dispatch.yml1.6 KB
- 资产文件assets/fleet-merge.yml11.7 KB
- 其他bun.lock11.6 KB
- 参考文档package.json505 B
- 参考文档README.md4.8 KB
- 参考文档resources/architecture.md3.8 KB
- 脚本scripts/fleet-analyze.ts866 B
- 脚本scripts/fleet-dispatch.ts5.3 KB
- 脚本scripts/fleet-merge.ts14.0 KB
- 脚本scripts/fleet-plan.ts1.3 KB
- 脚本scripts/github/cache-plugin.ts1.5 KB
- 脚本scripts/github/git.ts2.9 KB
- 脚本scripts/github/issues.ts1.4 KB
- 脚本scripts/github/markdown.ts3.3 KB
- 脚本scripts/prompts/analyze-issues.ts13.2 KB
- 脚本scripts/prompts/bootstrap.ts2.5 KB
- 脚本scripts/setup.sh2.4 KB
- 脚本scripts/types.ts1.4 KB
- 参考文档tsconfig.json266 B
03 SKILL.md 正文
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):
- Analyze — Fetch open issues and format as structured markdown
- Plan — A Jules session performs deep code-level triage and produces self-contained task prompts
- Validate — Verify no two tasks modify the same file (prevents merge conflicts)
- Dispatch — Spawn parallel Jules sessions, one per task
- 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.ymlassets/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:
- Add
JULES_API_KEYas a GitHub repository secret (Settings → Secrets → Actions) GITHUB_TOKENis provided automatically by GitHub Actions- Customize the cron schedule in
.github/workflows/fleet-dispatch.yml(default: daily 6am UTC) - 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
maxWaitMsinfleet-merge.ts(default: 10 minutes) - Bun not found: Install Bun:
curl -fsSL https://bun.sh/install | bash
04 同仓库更多 Skills
taste-design
Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
stitch-loop
Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern
site-md
Analyze a project description or site requirements and synthesize a project constitution into SITE.md for the Stitch Build Loop
enhance-prompt
Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.
design-md
Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files
stitch::upload-to-stitch
Upload local assets (images, mockups, extracted HTML, design markdown) to a Stitch project. ALWAYS use this skill when you need to upload visual assets, HTML pages, or design docs to Stitch, particularly when direct MCP tool calls fail or truncate due to base64 token limits.