akiojin/gwt-fix-issue
.codex/skills/gwt-fix-issue/SKILL.md
Use when the user wants to resolve an existing GitHub Issue by number or URL, especially when the workflow should continue through a direct fix unless a SPEC is needed.
$ install --global
skillsauthnpx skillsauth add akiojin/gwt gwt-fix-issueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:48 PM1.8s1 file scanned
SKILL.md
- name:
- gwt-fix-issue
- description:
- Use when the user wants to resolve an existing GitHub Issue by number or URL, especially when the workflow should continue through a direct fix unless a SPEC is needed.
gwt-fix-issue
Public task entrypoint for resolving an existing GitHub Issue.
When to use
- The Issue number or URL is already known
- The user says "fix issue #N", "resolve issue", or similar
- The user wants an issue-first workflow without choosing between issue/spec/build internals
Do not use this for new work intake. Use gwt-register-issue instead.
Ownership
- Gather the issue facts and related code context
- Decide direct-fix vs SPEC-needed
- Carry direct-fix work through implementation and verification
- Hand off to the visible SPEC flow only when broader design work is required
Workflow
- Verify that
gwt issue viewandgwt issue commentscan access the target issue. - Gather facts with
gwt issue view,gwt issue comments, linked PR inspection, andpython3 ".claude/skills/gwt-fix-issue/scripts/inspect_issue.py" --repo "." --issue "<number or URL>". - Decide direct-fix vs spec-needed. Prefer direct fix for clear corrective work; prefer
gwt-discussionwhen behavior design or broader scope definition is required. - If the change is a clear direct fix, continue through
gwt-build-specand finish verification. - Post progress and closure comments through
gwt issue comment. - Return the result in the current user's language.
Guardrails
- Agent-facing Issue workflow must use
gwt issue ...as the canonical CLI surface. - Direct
gh issue ...commands are not part of the normal path. - Do not treat the issue body as the source of truth for SPEC artifacts once a SPEC owner exists.
Related Skills
akiojin/tui-design
tools
VerifiedTrustedCommunity
Create distinctive, production-grade terminal user interfaces. Use when building TUI components with ratatui, CLI output styling, or xterm.js terminal rendering. Triggers: 'design TUI', 'terminal UI', 'TUIデザイン', 'ターミナルUI', 'ratatui widget'
3SKILL.mdUpdated Apr 15, 2026
akiojin/gwt-spec-search
testing
VerifiedTrustedCommunity
Semantic search over SPEC Issues (GitHub Issue cache at ~/.gwt/cache/issues/) using vector embeddings. Use when searching for existing specs, finding related specs, checking for duplicate specs, or determining which spec owns a scope. Mandatory preflight before gwt-discussion when the work may need a SPEC owner. Use when user says 'search specs', 'find related specs', 'check for duplicate specs', or asks which spec owns a scope.
3SKILL.mdUpdated Apr 15, 2026
akiojin/gwt-search
testing
VerifiedTrustedCommunity
Mandatory preflight before gwt-discussion, gwt-register-issue, and gwt-fix-issue. Use proactively before creating any SPEC or Issue owner or before reusing an existing one. Searches SPEC Issues, GitHub Issues, and project files via ChromaDB. Triggers: 'search', 'find related', 'check duplicates'.
3SKILL.mdUpdated Apr 15, 2026
akiojin/gwt-register-issue
business
VerifiedTrustedCommunity
Use when the user wants to register new work from a bug report, idea, or task description and an existing GitHub Issue number is not already known.
3SKILL.mdUpdated Apr 15, 2026