メニュー
Use when you need to check whether a GitHub issue or PR is still relevant, stale, or already resolved — without preparing full context or downloading media.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ge-analyze |
| description | Use when you need to check whether a GitHub issue or PR is still relevant, stale, or already resolved — without preparing full context or downloading media. |
Use this skill for quick triage — checking whether an issue or PR is worth working on, finding related PRs/commits, or assessing staleness. This does NOT download media or prepare full context documents.
ge package installedgh CLI authenticatedimport ge
analysis = ge.analyze_issue('owner/repo', 42)
Returns a dict with:
| Field | Type | Description |
|---|---|---|
state | str | "open" or "closed" |
age_days | int | Days since issue was created |
last_activity_days | int | Days since last comment or event |
labels | list[str] | Issue labels |
related_prs | list[dict] | PRs that reference this issue |
related_commits | list[dict] | Commits that reference this issue |
referenced_files | list[dict] | Files mentioned in the issue body, with existence check |
signals | list[str] | Human-readable signal descriptions |
recommendation | str | One of: proceed, investigate, likely_resolved |
proceed — Issue is open, active, and unresolved. Safe to work on.investigate — Mixed signals. There may be related merged PRs, recent activity suggesting partial resolution, or the issue is very old. Ask the user before investing effort.likely_resolved — Issue is closed, or has strong resolution signals (merged fix PRs, closing comments). Confirm with the user that they still want work done.analysis = ge.analyze_pr('owner/repo', 7)
Returns a dict with:
| Field | Type | Description |
|---|---|---|
state | str | "open", "closed", or "merged" |
merged | bool | Whether the PR has been merged |
draft | bool | Whether it's a draft PR |
mergeable | str | Merge status ("MERGEABLE", "CONFLICTING", etc.) |
ci_state | str | CI/check status |
review_states | dict | Review verdicts by reviewer |
linked_issues | list | Issues linked to this PR |
files_changed | int | Number of files changed |
signals | list[str] | Human-readable signal descriptions |
recommendation | str | One of the values below |
proceed — PR is open and ready for work or review.needs_changes — Reviewers requested changes. Focus on addressing their feedback.resolve_conflicts — Merge conflicts exist. Resolve them first.draft_wip — PR is a draft. It may be incomplete.already_merged — PR was already merged. Confirm with user what they want.closed_unmerged — PR was closed without merging. Confirm with user.Verify whether files mentioned in an issue still exist on the default branch:
from ge.analysis import check_referenced_files
results = check_referenced_files('owner/repo', ['src/auth.py', 'config/settings.yaml'])
# Returns list of dicts with 'path', 'exists', and 'ref' fields
If the analysis says proceed and the user wants you to actually work on the issue, switch to the main ge skill — it runs ge.prepare() which fetches everything (comments, media, full analysis) and writes a structured context document.
Behavioural policy for running unattended. Use when you have been launched in headless / auto-permission mode (e.g. by `ge run-roadmap` or `ge run-triage`) and there is no user available to answer questions. Converts every clarifying question into a logged decision so progress continues.
Triage and resolve a cross-repo issue backlog. Use when launched by `ge run-triage` against multiple repos — Phase A classifies and orders issues into a `TriageBacklog`; Phase B executes them one at a time (failing test → confirm red → fix → confirm green → open PR, then stop). Stops at PR; merging is a separate later phase.
Execute a roadmap of tasks end-to-end using GitHub as durable memory. Use when launched against a roadmap issue (typically by `ge run-roadmap`) — take the next todo task, do it, verify it, mark it done, log decisions, and repeat. Survives context exhaustion because each work unit rehydrates from GitHub.
Use when asked to work on a GitHub issue, PR, or discussion. Resolves flexible input (URL, folder, number), confirms with the user, prepares context, and guides the workflow.
Use when you need to prepare, read, or refresh full context for a GitHub issue, PR, or discussion — fetching data, downloading media, and writing structured context documents.