working-on-an-issue | claude-code-skills | ClaudePluginHub

Skill

Community

working-on-an-issue

From claude-code-skills

1

Description

Use when asked to work on, read, or implement a GitHub issue.

Install

1

Add the repository(one-time)

$

/plugin marketplace add britt/claude-code-skills

2

Install the plugin

$

/plugin install claude-code-skills@britt

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Skill Content

Working on an Issue

Announce at start: "I'm using the working-on-an-issue skill to implement this GitHub issue."

Overview

A structured workflow for implementing GitHub issues with verification.

Core Principle: Understand → Plan → Verify → Implement → Verify Again

When to Use

Developer asks to work on a GitHub issue
Developer asks to implement an issue
Developer provides an issue URL or number

Pre-flight Checklist

Before starting:

Issue URL or number obtained
Repository cloned and on correct branch
CLAUDE.md exists (or run setting-up-a-project first)
Developer available for questions (or async mode agreed)

The Process

1. Read and Understand the Issue

Get the issue content via:

GitHub CLI: gh issue view <number>
Ask user to paste the issue content
Use GitHub MCP tools if available

Clarify before proceeding:

If requirements are ambiguous, ask specific questions
If acceptance criteria are missing, propose them
If scope is unclear, confirm boundaries

Do not assume or invent requirements not in the issue.

2. Write an Implementation Plan

Use the obra/writing-plans skill (if available) or create a brief plan covering:

What changes are needed
Which files will be modified/created
Order of implementation
Risks or unknowns

Save to docs/plans/issue-<number>-plan.md and get developer approval before proceeding.

3. Write a Verification Plan

Use the britt/writing-verification-plans skill to create acceptance tests for the issue.

4. Implement

Follow TDD practices if TDD.rules.md is present
Commit after each logical change
Pause and ask if you hit unexpected complexity

5. Execute Verification

Run the verification plan. Report results using the verification log format from britt/writing-verification-plans.

Absolute Rules

No assumptions: Ask if anything is unclear
No scope creep: Only implement what's specified
Verification required: Task is incomplete until verification passes or developer confirms manual verification
Blocked = Stop: If blocked, use summoning-the-user skill

Links

GitHub Stats

0 forks

Updated 1 day ago

Similar Skills

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

54.7k

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

54.7k

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

54.7k