GitHub Issues

Low Risk

Auto-handle GitHub issues and submit PRs

⭐ 342 stars👍 128 upvotes0

Editorial assessment

Where GitHub Issues fits

GitHub Issues is currently positioned as a development skill for engineering teams running repository, CI, and issue workflows. Based on the available metadata, the core job to be done is straightforward: auto handle github issues and submit prs.

The current description adds a practical clue about how the skill behaves in the field: automatically triage issues, generate fixes, and open pull requests. integrates with github api to monitor issues, analyze code, and submit automated fixes. Combined with an npm-based install path, this makes GitHub Issues easier to evaluate than pages that only list a name and external link.

GitHub Issues can usually be trialed quickly, as long as the source and permissions still get reviewed. The current record points to GitHub repository access and Read/write local workspace as part of the operational surface, which should be reviewed during security and workflow testing.

Best fit

engineering teams running repository, CI, and issue workflows

Install surface

npx skills add gh-issues

Source signal

Public source link available

Workflow tags

Github, Automation, and Coding

Adoption posture

Install command documented

Risk review

Can usually be trialed quickly, as long as the source and permissions still get reviewed

Priority review

Why this skill deserves a closer look

GitHub Issues earns extra editorial attention because it already sits near the top of the skill library by usage or voting signal. For ClawList readers, that makes it a better candidate for deeper evaluation than a one-line listing or an untested community import.

Best for

Best for engineering teams running repository, CI, and issue workflows. This is the kind of skill worth reviewing when you are standardizing a workflow, not just experimenting in a throwaway session.

Last reviewed

April 3, 2026

Key caveats

Even strong community signals do not replace a source review. Check the install path, maintenance history, and permission surface before wider rollout.

This skill advertises compatibility with OpenClaw >=2026.1.0, so confirm your runtime version before you depend on it.

Compare GitHub Issues against adjacent options before standardizing it, because the highest-voted skill is not always the best fit for your exact repo, team, or automation surface.

Alternatives

Code ReviewerManaged Agents Kit

Source links

GitHub Issues source repository github.com homepage

Install Command

npx skills add gh-issues

Requires OpenClaw >=2026.1.0

Best-fit workflows

GitHub Issues is best evaluated in development environments where auto handle github issues and submit prs

Shortlist it when your team is actively comparing options for github, automation, and coding workflows

Use a disposable workspace for the first pass so you can confirm the install flow, repository quality, and downstream permissions before broader adoption

About

Automatically triage issues, generate fixes, and open pull requests. Integrates with GitHub API to monitor issues, analyze code, and submit automated fixes.

Rollout checklist

Review the source repository at https://github.com/openclaw/skill-github-issues and confirm the README, maintenance activity, and install notes are still current.

Run `npx skills add gh-issues` in a disposable environment first so you can confirm package resolution, dependencies, and rollback steps.

Verify whether github repository access and read/write local workspace matches your security expectations and least-privilege model.

Map GitHub Issues against the rest of your stack in github, automation, and coding workflows so the team knows whether it is a standalone tool or a supporting utility.

Key Features

Automatic issue triage and labeling

Smart PR generation with fixes

Code analysis and suggestions

Integration with CI/CD pipelines

FAQ

What does GitHub Issues help with?

GitHub Issues is positioned as a development skill. Based on the current summary and tags, it is most relevant for engineering teams running repository, CI, and issue workflows, especially when the workflow requires auto handle github issues and submit prs.

How should I evaluate GitHub Issues before using it in production?

Start by running npx skills add gh-issues in a disposable environment, then review the source repository, permission surface, and any workflow-specific dependencies before wider rollout.

Why does this page include editorial guidance instead of only the upstream docs?

ClawList is trying to make each skill page more useful than a bare directory listing. That means surfacing practical signals like the install surface, source link, permissions, workflow fit, and rollout considerations in one place.

Who is the best first user for GitHub Issues?

The best first evaluator is usually the operator or engineer already responsible for development workflows, because they can verify whether GitHub Issues matches the current stack, risk tolerance, and maintenance expectations.