What is gwt-spec-to-issue-migration?

A migration workflow for moving older project specifications into GitHub Issues, GitHub's system for tracking work and requirements. It supports local specification folders and older issue formats, then retires the old source after a successful migration.

Use it to preview and perform migrations, verify that specification issues were created, and retire the older specification files or issue bundles.

It helps keep one current source of truth for specifications and checks the planned changes before modifying or removing legacy files.

How akiojin/llmlb configures Gemini CLI

Reuse

Borrowing it

Nothing to install: this file belongs to akiojin/llmlb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/akiojin/llmlb/develop/.gemini/skills/gwt-spec-to-issue-migration/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/akiojin/llmlb

Made for: Gemini CLI.

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/akiojin/llmlb/gwt-spec-to-issue-migration/github.svg)](https://agentmods.dev/skills/akiojin/llmlb/gwt-spec-to-issue-migration)

Your own site

<a href="https://agentmods.dev/skills/akiojin/llmlb/gwt-spec-to-issue-migration"><img src="https://agentmods.dev/badge/skills/akiojin/llmlb/gwt-spec-to-issue-migration/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/akiojin/llmlb/gwt-spec-to-issue-migration"><img src="https://agentmods.dev/badge/skills/akiojin/llmlb/gwt-spec-to-issue-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 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.00048	$0.00931
Opus 5.5	$0.00019	$0.00372
Sonnet 5.5	$0.00010	$0.00186
Haiku 4.5	$0.00005	$0.00093

Measured 8d ago against content hash 891994d9f400, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gwt-spec-to-issue-migration 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 8d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/migrate-specs-to-issues.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.gemini/skills/gwt-spec-to-issue-migration/SKILL.md · 102 lines

How it starts

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

gwt Spec to Issue Migration

Overview

Use this skill for legacy spec migrations:

local specs/SPEC-* directories from a pre-Issue-first workflow
existing gwt-spec Issues that still keep the canonical bundle in the Issue body

Migrate legacy sources to artifact-first gwt-spec Issues, then remove or retire the old source of truth.

This skill uses:

.gemini/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.mjs
crates/gwt-core/src/git/issue_spec.rs

Preconditions

Run in repository root
gh auth status is authenticated for target repo
Branch policy is respected (no branch creation/switching unless user requests)
$GWT_PROJECT_ROOT environment variable is available; prefer it over CWD for repo resolution

Standard Workflow

Inspect source specs directory (auto-detection or explicit --specs-dir)
Run dry-run automatically and review planned migration count and deletion targets
If the user explicitly asked to migrate or convert, continue into actual migration after the dry-run
Verify migrated issues exist (gwt-spec label)
Confirm legacy local spec files or body-canonical bundles were retired on success
Ask the user only when migration intent is unclear or the requested scope does not obviously include the detected destructive changes

Commands

Dry-run

node ".gemini/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.mjs" --dry-run

Dry-run with explicit specs directory

node ".gemini/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.mjs" --dry-run --specs-dir "<path-to-specs>"

Execute migration

node ".gemini/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.mjs"

Dry-run existing body-canonical issue migration

node ".gemini/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.mjs" --dry-run --convert-existing-issues

Execute existing body-canonical issue migration

Read the full file on GitHub · 102 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

scripts/migrate-specs-to-issues.sh 9.9 KB runs code

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.

8d ago First seen · 102 lines · 48 tokens per session scan A 891994d9f400

Subscribe to this mod's changes

gwt-spec-to-issue-migration is a skill published in the GitHub repository akiojin/llmlb (10 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 931 once invoked, about $0.0002 per session on Opus 5.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-10-21.

Git and workflow Project management

antfu-issue-triage

Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…

antfu/skills · 76 tokens

mcore-split-pr

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

NVIDIA/skills · 25 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 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

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 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 zai-glm-flash smoke test), open code review (ocr)…

vybestack/llxprt-code · 88 tokens

llmlb: Skill for Gemini CLI