akiojin/gwt-spec-search
.codex/skills/gwt-spec-search/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add akiojin/gwt gwt-spec-searchInstall 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 29, 2026, 3:01 PM32.2s1 file scanned
SKILL.md
- name:
- gwt-spec-search
- description:
- 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.
SPEC Search
gwt maintains a vector search index of SPEC Issues using ChromaDB embeddings (model: intfloat/multilingual-e5-base). SPECs are stored as gwt-spec labeled GitHub Issues and cached locally at ~/.gwt/cache/issues/. The index is stored at ~/.gwt/index/<repo-hash>/worktrees/<worktree-hash>/specs/ and is rebuilt from the cache. Use gwt issue spec pull --all to refresh the cache before searching.
SPEC search first for spec integration
When the user asks any of the following, use SPEC search before manual file grep or directory listing:
- "既存仕様を探して"
- "どの SPEC に統合するべきか"
- "関連する SPEC を探して"
- "この機能の仕様は？"
- "重複する SPEC はないか確認して"
Minimum workflow:
- Run
search-specswith 2-3 semantic queries derived from the request - Pick the canonical existing spec if found
- Only fall back to creating a new spec when no suitable canonical spec exists
Environment
When the gwt TUI launches an agent pane, the following env vars are exported automatically:
GWT_PROJECT_ROOT— absolute path of the active worktreeGWT_REPO_HASH— SHA256[:16] of the normalized origin URLGWT_WORKTREE_HASH— SHA256[:16] of the canonicalized worktree absolute path
SPEC search command
~/.gwt/runtime/chroma-venv/bin/python3 ~/.gwt/runtime/chroma_index_runner.py \
--action search-specs \
--repo-hash "$GWT_REPO_HASH" \
--worktree-hash "$GWT_WORKTREE_HASH" \
--project-root "$GWT_PROJECT_ROOT" \
--query "your search query" \
--n-results 10
If the SPEC index does not yet exist, the runner builds it inline (full mode) from the repo-scoped Issue cache and emits NDJSON progress on stderr before returning the search result.
To force a full re-index (normally handled by the watcher / auto-build):
~/.gwt/runtime/chroma-venv/bin/python3 ~/.gwt/runtime/chroma_index_runner.py \
--action index-specs \
--repo-hash "$GWT_REPO_HASH" \
--worktree-hash "$GWT_WORKTREE_HASH" \
--project-root "$GWT_PROJECT_ROOT" \
--mode full
SPEC search output format
{"ok": true, "specResults": [
{"spec_id": "1939", "title": "gwt-spec: Semantic search platform", "status": "open", "phase": "phase/review", "dir_name": "#1939", "distance": 0.08}
]}
When to use
- Spec integration: find the canonical spec before creating or updating
- Task start: search for specs related to the assigned feature
- Duplicate check: verify no existing spec covers the same scope
- Architecture understanding: discover how features are specified
Notes
search-specsrefreshes the worktree-scoped SPEC index from the repo-scoped Issue cache before non-TUI searches- The runner auto-builds the index when missing (use
--no-auto-buildto suppress) - Uses semantic similarity (not just keyword matching)
- Lower distance values indicate higher relevance
- For file search, use
gwt-project-searchinstead - For GitHub Issue search, use
gwt-issue-searchinstead
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-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
akiojin/gwt-project-search
data-ai
VerifiedTrustedCommunity
Semantic search over project source files using vector embeddings. Use when the user asks to search project files, find related implementation files, or locate source files for a feature, bug, or concept.
3SKILL.mdUpdated Apr 15, 2026