implement-issue

A workflow for implementing a GitHub issue from start to finish. GitHub issues are tracked work items; a pull request is the review page used to propose the completed change.

In plain words
What is it for?
Use it to read an issue, create a feature branch, implement the change, run Maven tests, commit and push the code, and open a pull request.
Why use it?
It keeps issue work isolated, tested, reviewed, and linked back to the original request. It also gives the developer a repeatable branch, commit, and pull-request process.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/alexmond/jhelm/implement-issue
Any agent
npx skills add alexmond/jhelm --skill implement-issue
Clone the repo
git clone --depth 1 https://github.com/alexmond/jhelm

Made for: Claude Code, Codex.

Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 339 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00339
Opus 5 $0.00008 $0.00169
Sonnet 5 $0.00003 $0.00068
Haiku 4.5 $0.00002 $0.00034

Measured 2d ago against content hash 66bd5321ef4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

implement-issue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/implement-issue/SKILL.md · 62 lines

What it actually says

Implement GitHub issue #$ARGUMENTS

Follow this workflow for every code change:

Step 1: Read the issue

gh issue view $ARGUMENTS

Step 2: Create a feature branch

git checkout main
git pull
git checkout -b feature/$ARGUMENTS-<short-description>

Step 3: Implement the changes

  • Read relevant source files before making modifications
  • Follow project coding standards (Java 21, Lombok, tabs)
  • Keep changes focused on the issue requirements

Step 4: Run tests

./mvnw test

Fix any failures before proceeding.

Step 5: Commit and push

git add <changed-files>
git commit -m "<descriptive message>

Closes #$ARGUMENTS

Co-Authored-By: Claude <[email protected]>"
git push -u origin HEAD

Step 6: Create pull request

gh pr create --title "<concise title>" --body "## Summary
<bullet points>

## Test plan
<how to verify>

Closes #$ARGUMENTS

🤖 Generated with [Claude Code](https://claude.com/claude-code)"

Report the PR URL when done.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 62 lines · 15 tokens per session scan A 66bd5321ef4f

Subscribe to this mod's changes

implement-issue is a skill published in the GitHub repository alexmond/jhelm (4 stars, last pushed 8d ago), licensed Apache-2.0. It adds 15 tokens to every session and 339 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

evergreen

Evergreen CI infrastructure, configuration validation. Use when modifying .evergreen/ config, preparing to submit changes or understanding the Evergreen test matrix.

mongodb/mongo-java-driver · 31 tokens

sync-agents-docs

Sync AGENTS.md files, skills, and references after buildSrc or convention changes. Use after modifying build plugins, formatting rules, testing conventions, or task names to keep documentation consistent.

mongodb/mongo-java-driver · 43 tokens

ai-article

AI 类文章撰写。三种风格:安装教程、产品评测、面试八股。覆盖 AI Coding 工具实测、AI 开发框架应用、大模型测评、Agent/Skills/RAG 技术讲解。.

itwanger/toBeBetterJavaer · 57 tokens

job-article

根据指定选题,按照二哥的写作风格完成求职/校招/面试/职场类文章撰写。专注于秋招春招建议、公司薪资爆料+学习路线、面经八股解析、求职心态与球友故事分享。触发关键词:写一篇求职文章、秋招、春招、校招、offer、面经、薪资、面试、八股、简历、求职建议、球友故事、学习路线等。.

itwanger/toBeBetterJavaer · 118 tokens

video-cover-image

Generate matched 3:4, 16:9, and 4:3 short-video cover images from toBeBetterJavaer video scripts or AI/Java technical topics. Use when the user asks for 视频封面, 封面图, 横版和竖版, 小红书/抖音/B站/快手封面, pure-text covers with 白色大字+黄色小字, reference-image-matched covers, or wants a repeatable cover workflow for Markdown scripts under…

itwanger/toBeBetterJavaer · 113 tokens

video-script

为短视频/口播生成或优化脚本。适用于 AI 技术科普、Agent/Skill/RAG 等技术概念讲解、工具实测、热点拆解类短视频。支持两种模式:给定主题从零产出口播稿、对已有口播稿进行优化。触发关键词包括:口播、口播稿、视频脚本、短视频文案、录视频、拍视频、video script。.

itwanger/toBeBetterJavaer · 99 tokens