start-working-on-issue

Convert GitHub issues into pull requests using gh and git CLIs.

16|1|Updated Sep 24, 2025

Search Tags:#automation #testing #linting #pull request #github #cli #issue

Ready to run

npx skills add https://github.com/Hey-Diga/dotclaude --skill start-working-on-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: start-working-on-issue
Source: https://github.com/Hey-Diga/dotclaude/tree/main/skills/start-working-on-issue
Command: npx skills add https://github.com/Hey-Diga/dotclaude --skill start-working-on-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the repetitive and error-prone steps of converting a GitHub issue into working code: fetching issue details, analyzing requirements, implementing changes, running lint and tests, and opening a pull request.

Core Features & Use Cases

End-to-end Implementation: Fetches issue details, reads comments, and guides or performs code changes to address the issue.
Quality Gates: Runs lint and test commands before committing to ensure baseline code quality.
GitHub Integration: Uses gh and git to comment on issues, create PRs, and keep an audit trail of actions.
Use Case: Ideal when picking up a bug or feature ticket and wanting the assistant to handle analysis, implementation, testing, and PR creation.

Quick Start

Use the start-working-on-issue skill to implement GitHub issue 123 from analysis through PR creation.

Frequently Asked Questions about start-working-on-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate converting a GitHub issue into a pull request?▼

Automating a GitHub issue into a pull request is done by fetching issue details and comments, implementing code changes, running local lint and tests, and using git and gh CLIs to commit, push, and create the PR while logging actions as comments.

Does this workflow run lint and test commands before creating a PR?▼

Yes, the workflow runs npm lint and test commands locally before committing and pushing changes to ensure baseline code quality and verify that the implementation passes quality gates prior to PR creation.

Can I use GitHub CLI to comment on issues and track pull request progress?▼

Yes, you can use the gh CLI to comment on issues and create PRs, maintaining an audit trail by recording automated actions and implementation progress directly as comments on the GitHub issue and pull request.

What is the best way to implement code changes from a bug or feature ticket end-to-end?▼

The best way to implement code changes end-to-end is using an automated workflow that analyzes requirements fetched from issue comments, applies the necessary code changes, validates them with local tests, and opens a pull request.

Do I need git and gh CLIs installed to automate issue implementation?▼

Yes, you need both git and gh CLIs installed locally, as the workflow relies on these command-line tools to fetch issue details via GitHub, commit and push code changes, and execute pull request creation commands.