본문으로 건너뛰기
cccskills
무료GitHub에 공개

graphify-triage

Use this skill when the user wants to turn code graph analysis into tracked GitHub issues — "audit the architecture", "find god nodes", "triage architectural debt", "run graphify and log issues", "what's over-coupled in this codebase", "create issues from graphify findings", "check for structural problems", "scan for architectural smells", or any request that combines codebase topology analysis with issue tracking. This skill runs graphify to build a dependency graph, parses GRAPH_REPORT.md for god nodes and structural patterns, converts findings into GitHub issue payloads, and optionally pushes them to the repo. It bridges static analysis and project management in a single automated pass. Requires graphify and gh CLI.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree
연동 도구GitHub
설치 방법 보기

포함된 파일(3)

  • SKILL.md3.8 KB
  • resources/templates/gaia_node.json417 B
  • scripts/triage.py5.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Graphify Triage

What This Skill Does

Graphify Triage is a two-phase pipeline:

  1. Audit — runs graphify on the codebase, reads graphify-out/GRAPH_REPORT.md, and extracts god nodes (high-centrality over-coupled components) and suggested audit questions. Saves structured issue payloads to a JSON file for review.
  2. Sync — pushes the reviewed payloads to GitHub as labelled issues via the gh CLI.

The separation matters: always audit first and review the payloads before syncing. This gives the user a chance to prune or edit before issues appear in the tracker.

Dependencies

  • graphify — AST extraction and graph generation. Must be installed and on PATH.
  • gh (GitHub CLI) — authenticated (gh auth login) before running sync.

Quick Start

# Phase 1: generate and review proposed issues
uv run ~/.claude/skills/graphify-triage/scripts/triage.py audit --path . --output payloads.json

# Inspect payloads.json, edit or remove entries as needed, then:

# Phase 2: push to GitHub
uv run ~/.claude/skills/graphify-triage/scripts/triage.py sync --input payloads.json

To target a specific repo (e.g. when the CWD origin differs):

uv run ~/.claude/skills/graphify-triage/scripts/triage.py sync --input payloads.json --repo owner/repo

Workflow Steps

  1. Confirm graphify is installed (graphify --version). If missing, install it first — the audit step will fail silently otherwise.
  2. Run audit. The script calls graphify . --update internally, so the graph is always fresh.
  3. Open payloads.json and review the proposed issue titles and bodies. Remove or edit any that are false positives.
  4. Confirm gh auth status shows authenticated before proceeding to sync.
  5. Run sync. Issues are created with architecture/audit labels. If the repo lacks those labels, gh may prompt interactively — create them in advance to keep the run non-interactive.

What the Audit Parses

The script extracts three sections from graphify-out/GRAPH_REPORT.md:

SectionWhat it becomes
## God NodesOne issue: "[Architectural Refactor] Decouple God Nodes…" listing the top 3
## Surprising ConnectionsCaptured but currently informational only (not converted to issues)
## Suggested QuestionsOne issue per question: "[Audit] …" with context from the report

Pitfalls to Avoid

Stale graph: if you made significant changes since the last graphify run, the report may not reflect them. The audit command always passes --update to graphify, so this is only a risk if you're re-syncing an old payloads.json.

Missing labels: gh issue create --label architecture fails silently if the label doesn't exist in the target repo. Create labels upfront:

gh label create architecture --color 0075ca
gh label create audit --color e4e669

Wrong repo: sync infers the repo from the git remote. Pass --repo owner/repo explicitly when running from a clone that points somewhere other than the intended tracker.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

ci-churn

무료

Measure CI churn cost for a pull request: how many commits and how many CI-compute seconds were burned on avoidable "fix the CI" push rounds. Use when you want to understand the efficiency cost of a PR's iteration cycle, get actionable pre-push check suggestions, or include a churn summary in a pipeline report. Triggers: "ci churn", "how much CI did we burn", "avoidable commits", "ci efficiency", "wasted CI time", "churn report", "/ci-churn". Called automatically by /fp-drift at pipeline close.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree232026년 10월 17일 업데이트

design-gate

무료

Produce the rendered evidence a human-gated frontend PR owes its reviewer: capture each changed surface (plus the before state for anything modified, plus mobile width), then generate one self-contained local HTML page the founder can open and review without checking anything out. Use when a PR is gated by the "Frontend changes are HUMAN-GATED" section of CLAUDE.md, or when the user says "/design-gate", "screenshot evidence for this PR", "prep this for founder review", "build the design evidence page", "what does this look like before and after". The page comes from a template script, not hand-written markup. Output is session-local and never committed. Do NOT use for non-gated changes: typo/grammar/factual fixes in an unchanged block, dead link targets, alt/ARIA fixes with no visual change, cache-bust bumps, or refactors with no rendered diff.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree232026년 10월 17일 업데이트

design-iteration

무료

One-fix-at-a-time, approval-gated design fix recovery. Given a checklist of fixes (handover doc, CHECKLIST.md, or inline list), applies each individually, presents a diff, and waits for an explicit APPROVE / REJECT / NO CHANGES decision before committing. Trigger phrases: /design-iteration, "go through the checklist one by one", "fix these one at a time", "bucket recovery", "design fix pass".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree232026년 10월 17일 업데이트

dev-calibrate

무료

Playbook for correcting a named skill's star level to match its computed Trust Magnitude grade, with an independent post-calibration verification pass and a CLI-logged timeline event (never hand-written). Use when: recalibrating a skill's level, fixing a stale or drifted star rating, running a batch of `gaia dev calibrate` corrections, or confirming a past calibration actually landed. Triggers: "calibrate <skill>", "recalibrate the trust magnitude backlog", "promote/demote <skill> to N stars", "why is <skill> still N stars", "verify a calibration actually landed", "Hall of Heroes ranking is wrong".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree232026년 10월 17일 업데이트

epic-close

무료

Close out a completed EPIC / sprint end-to-end: author a fact-verified meta-post announcing what shipped, archive the EPIC's handovers, snapshot orchestrator memory, gate the integration→main merge on CI-green + explicit human go, drive the version bump (merge-commit conventions that auto-sync classifies), and verify the release reached the registry/PyPI. Use when the user says "close out EPIC <n>", "wrap up the sprint", "ship the meta shift", "/epic-close", or asks to finalize an integration branch that is ready to merge to main. Generalizes the EPIC 1002 (Yggdrasil II) close-out. This skill orchestrates — it authors founder docs directly (superadmin) and delegates code/regen to workers; it NEVER merges to main without the human gate.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree232026년 10월 17일 업데이트

ev-adversarial-audit

무료

Run this skill for Phase 3 of the evidence verification pipeline — the adversarial audit step. Use when you need to check the evidence data lake for bad data before ingestion: dead links, wrong URL formats (tree/ vs blob/), subjective wording ("elite", "high-quality"), stale migration notes, benchmark catalog misuse/vendor-claim leakage, or skills whose star evidence conflicts with classified evidence level. Triggers on phrases like: "audit the data lake", "adversarial check", "ev-adversarial-audit", "check for noise in evidence", "flag bad evidence", "run the audit phase", "quality check the by-type files", or any reference to Phase 3 of the pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree232026년 10월 17일 업데이트

gaia-research의 스킬 모두 보기

이 스킬의 문제 신고