How do I install the Gwt Spec To Issue Migration skill?

Run npx skillmds@latest add majiayu000/gwt-spec-to-issue-migration-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gwt Spec To Issue Migration safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gwt Spec To Issue Migration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gwt Spec To Issue Migration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gwt Spec To Issue Migration?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gwt Spec To Issue Migration by majiayu000

Name: Gwt Spec To Issue Migration
Rating: 4.2 (5 reviews)
Author: majiayu000

Gwt Spec To Issue Migration

Migrate existing local SPEC directories (specs/SPEC-*) to GitHub Issue-first specs (gwt-spec label) using the bundled migration script. Use when asked to replace local spec.md/plan.md/tasks.md based workflow with GitHub Issue based management.

majiayu000 Updated Sep 22, 2026 567 repo stars

File contents

gwt Spec to Issue Migration

Overview

Use this skill only for repositories that still carry legacy local spec trees from a pre-Issue-first workflow.

Migrate local specs/SPEC-* directories to GitHub Issues (gwt-spec label), then remove the legacy local source of truth.

This skill uses:

.gemini/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.sh
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 and review planned migration count and deletion targets
Run actual migration
Verify migrated issues exist (gwt-spec label)
Confirm legacy local spec files were removed on success

Commands

Dry-run

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

Dry-run with explicit specs directory

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

Execute migration

bash ".gemini/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.sh"

Verify report

cat migration-report.json

Note: migration-report.json is deleted automatically after a fully successful migration cleanup. It remains available for dry-run and failure cases.

Verify created issues

gh issue list --label gwt-spec --state all --limit 200

Expected Behavior

Auto-detects local specs/ under $GWT_PROJECT_ROOT or the current repository
If no SPEC-* directory exists, exits successfully with empty report ([])
Migrates sections from spec.md, plan.md, tasks.md and related artifacts
Writes per-spec result to migration-report.json
Shows planned deletions during --dry-run
Deletes migrated local spec directories, detected legacy workflow leftovers, and migration-report.json after a fully successful cleanup

Notes

For safety, always run --dry-run first.
Artifact files in contracts/ and checklists/ are migrated as issue comments.
After migration, ongoing spec updates should use Issue-first operations (gwt-spec-ops).
This skill is for external legacy import only; gwt's normal spec workflow should never recreate repository-local spec bundles.

---name: gwt-spec-to-issue-migration-3description: Migrate existing local SPEC directories (specs/SPEC-*) to GitHub Issue-first specs (gwt-spec label) using the bundled migration script. Use when asked to replace local spec.md/plan.md/tasks.md based workflow with GitHub Issue based management.---# gwt Spec to Issue Migration## OverviewUse this skill only for repositories that still carry legacy local spec trees from a pre-Issue-first workflow.Migrate local `specs/SPEC-*` directories to GitHub Issues (`gwt-spec` label), then remove the legacy local source of truth.This skill uses:- `.gemini/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.sh`- `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 Workflow1. Inspect source specs directory (auto-detection or explicit `--specs-dir`)2. Run dry-run and review planned migration count and deletion targets3. Run actual migration4. Verify migrated issues exist (`gwt-spec` label)5. Confirm legacy local spec files were removed on success## Commands### Dry-run```bashbash ".gemini/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.sh" --dry-run```### Dry-run with explicit specs directory```bashbash ".gemini/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.sh" --dry-run --specs-dir "<path-to-specs>"```### Execute migration```bashbash ".gemini/skills/gwt-spec-to-issue-migration/scripts/migrate-specs-to-issues.sh"```### Verify report```bashcat migration-report.json```Note: `migration-report.json` is deleted automatically after a fully successful migration cleanup. It remains available for dry-run and failure cases.### Verify created issues```bashgh issue list --label gwt-spec --state all --limit 200```## Expected Behavior- Auto-detects local `specs/` under `$GWT_PROJECT_ROOT` or the current repository- If no `SPEC-*` directory exists, exits successfully with empty report (`[]`)- Migrates sections from `spec.md`, `plan.md`, `tasks.md` and related artifacts- Writes per-spec result to `migration-report.json`- Shows planned deletions during `--dry-run`- Deletes migrated local spec directories, detected legacy workflow leftovers, and `migration-report.json` after a fully successful cleanup## Notes- For safety, always run `--dry-run` first.- Artifact files in `contracts/` and `checklists/` are migrated as issue comments.- After migration, ongoing spec updates should use Issue-first operations (`gwt-spec-ops`).- This skill is for external legacy import only; gwt's normal spec workflow should never recreate repository-local spec bundles.

Frequently asked questions