GitHub Issues
Low RiskLocal git operations and GitHub issue management for project development workflows.
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: local git operations and github issue management for project development workflows.
The current description adds a practical clue about how the skill behaves in the field: a skill for managing github issues and local git operations. it identifies issues as development requirements and coordinates with claude code for implementation. use it to create feature branches, commit and push code changes, and pull the latest updates from your repository. latest version: 1.0.0 license: mit 0 registry tags: latest source: https://clawhub.ai/skills/git hub issus. Combined with a CLI-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. No explicit permission list is published in the current record, so verify the runtime surface in the source repository before rollout.
Best fit
engineering teams running repository, CI, and issue workflows
Install surface
Open in ClawHub: https://clawhub.ai/skills/git-hub-issus
Source signal
Public source link available
Workflow tags
Git, Github, and Issues
Adoption posture
Install command documented
Risk review
Can usually be trialed quickly, as long as the source and permissions still get reviewed
Install Command
Open in ClawHub: https://clawhub.ai/skills/git-hub-issusBest-fit workflows
GitHub Issues is best evaluated in development environments where local git operations and github issue management for project development workflows
Shortlist it when your team is actively comparing options for git, github, and issues 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
A skill for managing GitHub issues and local git operations. It identifies issues as development requirements and coordinates with Claude Code for implementation. Use it to create feature branches, commit and push code changes, and pull the latest updates from your repository. Latest version: 1.0.0 License: MIT-0 Registry tags: latest Source: https://clawhub.ai/skills/git-hub-issus
Rollout checklist
Review the source repository at https://clawhub.ai/skills/git-hub-issus and confirm the README, maintenance activity, and install notes are still current.
Run `Open in ClawHub: https://clawhub.ai/skills/git-hub-issus` in a disposable environment first so you can confirm package resolution, dependencies, and rollback steps.
Capture the permissions and runtime surface during the first install, because the current record does not yet publish a detailed permission map.
Map GitHub Issues against the rest of your stack in git, github, and issues workflows so the team knows whether it is a standalone tool or a supporting utility.
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 local git operations and github issue management for project development workflows.
How should I evaluate GitHub Issues before using it in production?
Start by running Open in ClawHub: https://clawhub.ai/skills/git-hub-issus 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.
Related Skills
BM.md - Bookmark Management Skill
NPX-installable skill for managing bookmarks via miantiao-me/bm.md package
Jarvis Db Query Doctor 01
Diagnose slow SQL and rewrite queries for safer performance. Use when handling development work that needs repeatable steps, quality gates, and practical out...
OpenClaw All Backup
Complete backup of OpenClaw configuration directory with timestamped snapshots.