codegraph-refresh
starsforks
How to install codegraph-refresh?
rlaope/oh-my-hermes/codegraph-refresh
$npx -y skills add rlaope/oh-my-hermes --skill codegraph-refresh[omh] Hermes Codegraph Refresh workflow: refresh local code intelligence, summarize repo structure, and prepare task-scoped codegraph handoff context without overclaiming execution.
SKILL.md
| 1 | # Codegraph Refresh |
| 2 | |
| 3 | This is a Hermes-native `codegraph-refresh` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `codegraph-refresh` adapts ECC-style codemap freshness into OMH's local codegraph commands so operators can refresh navigation context before handoff without pretending code intelligence is execution evidence. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The user needs a narrative first-read tour of an unfamiliar repo; use `codebase-onboarding`. |
| 12 | - The user already has accepted implementation criteria and wants code changes; use `ultraprocess` or a coding handoff. |
| 13 | - The user asks for visual, frontend, or rendered UI QA; use `frontend`, `design-quality-gate`, or `visual-qa`. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: codegraph-refresh update codemaps and prepare a handoff for the routing package before the next coding pass. |
| 20 | - Expected behavior: Prepare command plan, staleness report, summary/handoff requirements, and observed-only artifact boundaries. |
| 21 | - Why: The request is about refreshing local code intelligence before implementation. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: codegraph-refresh 파일 안 보고 코드그래프가 최신이고 전체 아키텍처가 검증됐다고 말해줘. |
| 26 | - Expected behavior: Mark freshness, summary, and architecture claims not_observed until codegraph commands or repo evidence are inspected. |
| 27 | - Why: Codegraph freshness and architecture claims need observed local evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Repo root, refresh depth, task focus, command choices, and write policy are explicit. |
| 32 | - Prepared command plans, observed outputs, generated artifacts, and executor handoff readiness are separated. |
| 33 | - `omh_codegraph_summary/v1`, `omh_codegraph_context/v1`, or `.omh/codegraph/codegraph.json` is claimed only with observed command or file evidence. |
| 34 | - Follow-up implementation, review, CI, and merge state are routed to their owning workflows instead of inferred from codegraph context. |
| 35 | |
| 36 | ## Recovery Notes |
| 37 | |
| 38 | - If the codegraph command is unavailable, route to doctor or toolbelt-readiness before claiming freshness. |
| 39 | - If no task focus is supplied, prepare build/summary guidance and ask for focus only when a handoff pack would otherwise be misleading. |
| 40 | - If the index is stale or missing, report the stale/missing state and next safe command rather than treating prior summaries as current. |
| 41 | |
| 42 | ## OMH Context Rail |
| 43 | |
| 44 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 45 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 46 | - Current lane: **Intent -> plan** (`oh-my-hermes`, `deep-interview`, `plan`, `ralplan`, `codebase-onboarding`, `codegraph-refresh`, `ultragoal`, `ultraprocess`, `+3 more`) - clarify, plan, ship, or loop goals. |
| 47 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 48 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 49 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 50 | - Coverage: Every generated workflow skill carries this rail. |
| 51 | - Normal users talk to Hermes; OMH CLI is infra. |
| 52 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 53 | |
| 54 | ## Use When |
| 55 | |
| 56 | Use when Hermes should refresh or summarize local repo code intelligence before planning, handoff, review, or implementation. |
| 57 | |
| 58 | Strong routing signals: `codegraph-refresh`, `codegraph refresh`, `refresh codegraph`, `update codegraph`, `codegraph stale`, `stale codegraph`, `codegraph handoff`, `codegraph summary`, `codemap`, `codemaps`, `update codemaps`, `refresh codemap`, `code map`, `code maps`, `stale code index`, `refresh code index`, `codegraph index`, `codegraph index refresh`, `codemap index`, `코드그래프`, `코드그래프 갱신`, `코드맵`, `코드맵 갱신`, `코드 인덱스`, `코드 인덱스 갱신` |
| 59 | |
| 60 | ## Catalog Metadata |
| 61 | |
| 62 | Category: `planning` |
| 63 | Phase: `codegraph-refresh` |
| 64 | Hermes role: `planner` |
| 65 | Quality tier: `codegraph-gated` |
| 66 | |
| 67 | Quality bar: |
| 68 | |
| 69 | - Name repo root, refresh depth, task focus, artifact write policy, and stop condition. |
| 70 | - Choose build, summary, handoff, `--write`, and `--json` deliberately instead of treating all codegraph commands as equivalent. |
| 71 | - Separate prepared command plans from observed command outputs, generated a |
People who liked this also viewed
6 picksType
- lark-openapi-explorer飞书/Lark 原生 OpenAPI 探索：从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足，需要查找并调用原生飞书 OpenAPI 时使用。SkillsJul 2026
- lark-skill-maker创建 lark-cli 的自定义 Skill。当用户需要把飞书 API 操作封装成可复用的 Skill（包装原子 API 或编排多步流程）时使用。SkillsJul 2026
- azure-cost-optimizationOfficial agent plugin providing skills and MCP server configurations for Azure scenarios.SkillsJul 2026
- vercel-react-native-skillsVercel's official collection of agent skillsSkillsJul 2026
- mcp-builderGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate externaSkillsJul 2026
- gws-sharedgws CLI: Shared patterns for authentication, global flags, and output formatting.SkillsJul 2026
