implement-issue

Original：🇨🇳 Chinese

Translated

Read a GitHub Issue, create a detailed plan in `_/local-plans/<issue-number>-<slug>.md`, and implement the code **after user approval**. After implementation, perform a security review (OWASP Top 10) → run tests → commit using Conventional Commits. Used for implementation requests where an Issue number or URL is provided, such as "Implement Issue #N" or "Start working on this Issue".

2installs

Sourcefandhe-ai/agent-cli-skills

Added on2026-05-11

NPX Install

npx skill4agent add fandhe-ai/agent-cli-skills implement-issue

SKILL.md Content (Chinese)

View Translation Comparison →

implement-issue

Read a GitHub Issue and implement the code after confirming the plan.

Flow

Step 1: Fetch the Issue

Retrieve the content from the Issue URL or number:

bash

gh issue view <url-or-number>

Step 2: Investigate the codebase and create an implementation plan

Investigate related code based on the Issue content and create a detailed plan file in

_/local-plans/

.

2-1. Investigate related code

Investigate the following in parallel:

Current status of target files (Glob / Grep / Read)
Reusable existing components and utilities
Relevant API endpoints
Similar implementation patterns

2-2. Save the plan file to

_/local-plans/

File name:

<issue-number>-<issue-slug>.md

(example:

_/local-plans/42-add-auth.md

)

Required sections for the plan:

markdown

# [Issue Title]

## Context
Background and purpose of the Issue, and why this change is necessary.

## Approach
Implementation strategy. If there are options, also describe the reason for choosing this approach.

## File Changes

| File Path | Changes |
|-------------|---------|
| `src/...` | Add ~ |
| `lib/...` | Modify ~ |

## Reuse
Path and purpose of existing implementations to reuse.

## Test Plan
- [ ] Operation verification steps
- [ ] Edge case verification

Step 3: Present the plan to the user and wait for approval

Display the content of the created plan file and start implementation only after obtaining user approval. Do not start implementation without approval.

Step 4: Implement the code

Implement in accordance with CLAUDE.md and project guidelines. For extensive changes, use

isolation: "worktree"

to implement safely.

Step 5: Security Review (Required)

Perform security checks using Agent tools.

Check items:

OWASP Top 10
Hardcoding of API keys and secrets
Input validation
Potential XSS vulnerabilities

If issues are found, fix them before proceeding to the next step.

Step 6: Run Tests

Run the project's test commands. Fix any issues if tests fail.

Step 7: Create a Commit

Use the

create-commit

skill to create a commit in Conventional Commits format.

Notes

Do not start implementation without user approval
Do not commit with unresolved security issues
Split large changes into separate commits
Use
GIT_SSL_NO_VERIFY=1
in sandbox environments: For details, refer to the "Execution in Sandbox Environment" section below

Execution in Sandbox Environment

When running this skill in a sandbox environment, consider using

GIT_SSL_NO_VERIFY=1

for GitHub operations over the network. The main remote operations of this skill are

gh issue view

/

gh issue comment

, and the "remote write" determination is Required (this skill mainly uses APIs). For details on command classification and precautions for disabling TLS verification, refer to

docs/sandbox-tls.md

.

implement-issue

NPX Install

Tags

SKILL.md Content (Chinese)

implement-issue

Flow

Step 1: Fetch the Issue

Step 2: Investigate the codebase and create an implementation plan

2-1. Investigate related code

2-2. Save the plan file to
`_/local-plans/`

Step 3: Present the plan to the user and wait for approval

Step 4: Implement the code

Step 5: Security Review (Required)

Step 6: Run Tests

Step 7: Create a Commit

Notes

Execution in Sandbox Environment