What is git-issue-updater-skill?

A tool that adds progress comments to GitHub issues or JIRA tickets after related Git commits. GitHub issues and JIRA tickets are work items used to track software tasks and bugs.

Use it to find issue references in commit messages, summarize commit changes, add links or hashes, and verify that the update was posted.

It connects code changes to the work item and keeps a dated record of who changed what, when, and in which commit.

git-issue-updater-skill — Skill for OpenCode by darellchua2

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.

Any agent

npx skills add darellchua2/opencode-config-template --skill git-issue-updater-skill

Clone the repo

git clone --depth 1 https://github.com/darellchua2/opencode-config-template

Made for: OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/git-issue-updater-skill.svg)](https://agentmods.dev/skills/darellchua2/opencode-config-template/git-issue-updater-skill)

Your own site

<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/git-issue-updater-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/git-issue-updater-skill.svg" alt="Measured on agentmods" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,764 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.05764
Opus 5	$0.00016	$0.02882
Sonnet 5	$0.00007	$0.01153
Haiku 4.5	$0.00003	$0.00576

Measured 3d ago against content hash 74345f4d47a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade B, and why

git-issue-updater-skill scanned grade B with 2 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 3d 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

- Fallback: REST comment — `curl -u email:token -X POST https://<site>.atlassian.net/rest/api/3/issue/<KEY>/comment -d '{"body":"..."}'` (cloudId: `curl https://<site>.atlassian.net/_edge/tenant_info`).

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Fallback: REST comment — `curl -u email:token -X POST https://<site>.atlassian.net/rest/api/3/issue/<KEY>/comment -d '{"body":"..."}'` (cloudId: `curl https://<site>.atlassian.net/_edge/tenant_info`).

opencode_app/.opencode/skills/git-issue-updater-skill/SKILL.md · 791 lines

How it starts

The opening of the file, as written. The whole thing — 791 lines — stays where its author put it; the contents beside it link to each section on GitHub.

What I do

I provide automatic issue progress updates for both GitHub and JIRA after commits are made:

Extract Commit Details: Get latest commit info: hash, message, author, date, time, files changed
Determine Issue Reference: Extract GitHub issue number (#123) or JIRA ticket key (PROJECT-123) from commit message
Format Update Comment: Create consistent documentation with user, date, time, changes summary
Support Multiple Platforms: Add comments to GitHub issues or JIRA tickets
Include Metadata: Add commit link (GitHub) or hash (JIRA), user info, timestamp
Handle Incremental Updates: Support multiple commits with cumulative or per-commit updates
Verify Updates: Confirm comment was successfully added to issue/ticket

When to use me

Use this framework when:

You need to track commit progress in GitHub issues or JIRA tickets
You've made commits and want to update the associated issue/ticket
You want consistent documentation of progress with timestamps and user info
You're creating a workflow that makes commits and should update issues
You need traceability between commits and issues
You want to maintain consistency in issue/ticket comments
You're working with teams that require progress updates in issues

This is a framework skill - it provides issue update functionality that other skills use.

MCP Availability Guard (JIRA branch only)

GitHub comments go through gh — always available. JIRA comments use atlassian_addCommentToJiraIssue, and the atlassian MCP server is disabled by default (opt-in):

If atlassian_* tools are absent from your tool list, do NOT attempt or hallucinate them.
Interactive: offer per-project enable via opencode-repo-setup-skill (effective next session).
Fallback: REST comment — curl -u email:token -X POST https://<site>.atlassian.net/rest/api/3/issue/<KEY>/comment -d '{"body":"..."}' (cloudId: curl https://<site>.atlassian.net/_edge/tenant_info).
Otherwise: report the JIRA update as skipped — commit detection and GitHub updates are unaffected.

Read the full file on GitHub · 791 lines

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.

3d ago First seen · 791 lines · 33 tokens per session scan B 74345f4d47a3

Subscribe to this mod's changes

git-issue-updater-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 5,764 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Git and workflow Project management git-workflow

git-ship

An automated Git release workflow that takes code changes through a branch, commit, pull request, review checks, squash merge, and return to the main branch. A pull request is a request to review and merge changes into a shared branch.

oil-oil/git-ship · 273 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…

vybestack/llxprt-code · 87 tokens