メニュー
Query the XerahS src knowledge graph for architecture, dependencies, and symbol relationships. Use when exploring how modules connect, finding paths between types, or orienting on unfamiliar areas of src/.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ShareX/XerahS --skill graphifyコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Orchestrate XerahS release flow in strict order: run maintenance prep first, update-changelog second (optional only if docs/CHANGELOG.md is intentionally absent), verify build, bump/commit/push/tag while syncing Chocolatey version metadata, monitor GitHub Actions every 2 minutes, ensure standard release notes content, then apply repo release-channel policy (ShareX/XerahS = pre-release; KovaForge/XerahS = full latest release). On failures, inspect logs, fix root cause, and retry with the next patch release.
Triage pasted or file-backed XerahS startup, runtime, capture, history, or debug logs. Use when a user asks whether logged errors are still valid, wants fixes from a log excerpt, or needs repeated log noise reduced to a small verified bug list with code-level follow-through.
Rules and workflows for updating docs/CHANGELOG.md with user-facing, consolidated release notes (not commit logs). Includes version grouping, noise filtering, platform/XIP-aware bullets, and GitHub tag-linked headings.
SOC 職業分類に基づく
SKILL.md を表示中
| name | graphify |
| description | Query the XerahS src knowledge graph for architecture, dependencies, and symbol relationships. Use when exploring how modules connect, finding paths between types, or orienting on unfamiliar areas of src/. |
Canonical graph lives at:
docs/architecture/graphify-out/
See README.
Full cross-agent kickoff prompt (copy-paste + skill/tool path index):
developers/guidelines/GRAPHIFY_AGENT_PROMPT.md
Use graphify first for:
src/Do not block ordinary file edits or line-level debugging on graphify. After orientation, use Read/Grep as usual.
Repo-local binary (preferred):
G=.tools/graphify-venv/bin/graphify
GRAPH=docs/architecture/graphify-out/graph.json
If the venv is missing:
python3 -m venv .tools/graphify-venv
.tools/graphify-venv/bin/pip install -U pip graphifyy
Commands:
$G query "<question>" --graph "$GRAPH"
$G path "<A>" "<B>" --graph "$GRAPH"
$G explain "<concept>" --graph "$GRAPH"
$G affected "<symbol>" --graph "$GRAPH"
A root symlink graphify-out → docs/architecture/graphify-out may exist so default CLI paths work.
docs/architecture/graphify-out/GRAPH_REPORT.md — hubs / god nodes / suggested questionsdocs/architecture/graphify-out/GRAPH_TREE.html — lighter browser viewdocs/architecture/graphify-out/graph.html — full force graph (large)Full rebuild (preferred — scopes to src/, refreshes graph + tree + symlink):
scripts/update-graphify.sh
Incremental update (no --graph flag — path comes from the repo-root
graphify-out/ symlink. NEVER pass --graph to update; NEVER pass
. (whole-repo root) when you only want src/):
$G update src
After very large refactors, prefer the full scripts/update-graphify.sh
over an incremental update — the graph's clustering benefits from a clean
rebuild after structural changes.
Help caveat: graphify <subcommand> --help is unreliable; use
top-level graphify --help only.