์Šคํ‚ฌ ghe-status
๐Ÿ“ฆ

ghe-status

์•ˆ์ „

View GitHub Elements Workflow Status

GitHub Elements users need quick visibility into their active threads and workflow state before starting work. This read-only skill provides an instant overview of active threads, phase distribution, and workflow health without modifying anything.

์ง€์›: Claude Codex Code(CC)
๐Ÿ“Š 69 ์ ์ ˆํ•จ
1

์Šคํ‚ฌ ZIP ๋‹ค์šด๋กœ๋“œ

2

Claude์—์„œ ์—…๋กœ๋“œ

์„ค์ • โ†’ ๊ธฐ๋Šฅ โ†’ ์Šคํ‚ฌ โ†’ ์Šคํ‚ฌ ์—…๋กœ๋“œ๋กœ ์ด๋™

3

ํ† ๊ธ€์„ ์ผœ๊ณ  ์‚ฌ์šฉ ์‹œ์ž‘

ํ…Œ์ŠคํŠธํ•ด ๋ณด๊ธฐ

"ghe-status" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. What's the GitHub Elements status?

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • ## GitHub Elements Status Report
  • ย 
  • ### Active Threads
  • | Issue | Type | Phase | Epic | Assignee | Last Activity |
  • |-------|------|-------|------|----------|---------------|
  • | #42 | Feature | DEV | User Auth | @developer1 | 2 hours ago |
  • | #38 | Bug | TEST | Login Flow | @developer2 | 30 minutes ago |
  • ย 
  • ### Phase Distribution
  • DEV: 1 active | TEST: 1 active | REVIEW: 0 active
  • ย 
  • ### Available Work
  • - #45: Add dark mode support (Ready)
  • - #47: Fix memory leak in worker (Ready)
  • ย 
  • ### Workflow Health
  • - Violations: 0
  • - Checkpoint frequency: 85%

"ghe-status" ์‚ฌ์šฉ ์ค‘์ž…๋‹ˆ๋‹ค. Show me what threads are active

์˜ˆ์ƒ ๊ฒฐ๊ณผ:

  • ## Active Threads Overview
  • ย 
  • **Total Active:** 3 threads
  • ย 
  • **By Phase:**
  • - DEV: 1 thread
  • - TEST: 2 threads
  • - REVIEW: 0 threads
  • ย 
  • **By Type:**
  • - Features: 2
  • - Bugs: 1
  • ย 
  • See full status above for details.

๋ณด์•ˆ ๊ฐ์‚ฌ

์•ˆ์ „
v5 โ€ข 1/23/2026

This is a read-only skill that only queries and displays GitHub Elements workflow state. Static analysis flagged markdown documentation formatting (backticks for file paths and timestamps) and YAML frontmatter text patterns as security issues. All findings are false positives. The skill has no code execution, file system access, or network operations - it only spawns the reporter agent to query GitHub API. Safe for publication.

1
์Šค์บ”๋œ ํŒŒ์ผ
135
๋ถ„์„๋œ ์ค„ ์ˆ˜
0
๋ฐœ๊ฒฌ ์‚ฌํ•ญ
5
์ด ๊ฐ์‚ฌ ์ˆ˜
๋ณด์•ˆ ๋ฌธ์ œ๋ฅผ ์ฐพ์ง€ ๋ชปํ–ˆ์Šต๋‹ˆ๋‹ค
๊ฐ์‚ฌ์ž: claude ๊ฐ์‚ฌ ์ด๋ ฅ ๋ณด๊ธฐ โ†’

ํ’ˆ์งˆ ์ ์ˆ˜

38
์•„ํ‚คํ…์ฒ˜
100
์œ ์ง€๋ณด์ˆ˜์„ฑ
85
์ฝ˜ํ…์ธ 
22
์ปค๋ฎค๋‹ˆํ‹ฐ
100
๋ณด์•ˆ
91
์‚ฌ์–‘ ์ค€์ˆ˜

๋งŒ๋“ค ์ˆ˜ ์žˆ๋Š” ๊ฒƒ

Quick Session Start Check

When starting a Claude session, quickly see what threads are active, what phase work is in, and what is available to claim before beginning new tasks.

Daily Workflow Overview

Get a birds-eye view of all ongoing work, identify bottlenecks in TEST or REVIEW phases, and see where attention is needed.

Before Claiming Work

Check what is already in progress and what unclaimed work is available before deciding what to work on next.

์ด ํ”„๋กฌํ”„ํŠธ๋ฅผ ์‚ฌ์šฉํ•ด ๋ณด์„ธ์š”

Basic Status Check 
What's the GitHub Elements status?
Active Threads Query 
Show me what threads are active right now
Personal Work Context 
What am I currently working on?
Workflow Health Check 
Show me the workflow state and any violations

๋ชจ๋ฒ” ์‚ฌ๋ก€

  • Use ghe-status at the start of every session to establish context before working
  • Check phase distribution to identify bottlenecks (accumulation in TEST or REVIEW indicates issues)
  • Combine with ghe-report when you need detailed metrics or health analysis

ํ”ผํ•˜๊ธฐ

  • Do not use ghe-status when you need to claim work (use ghe-claim instead)
  • Do not expect detailed reports - use ghe-report for comprehensive metrics
  • Do not assume this skill can modify issue state - it is purely read-only

์ž์ฃผ ๋ฌป๋Š” ์งˆ๋ฌธ

What is the difference between ghe-status and ghe-report?
ghe-status provides a quick read-only overview of active threads and basic workflow state. ghe-report provides detailed metrics, health analysis, and epic-specific reports. Use status for quick checks, report for deep analysis.
Can ghe-status modify my issues?
No. ghe-status is completely read-only. It only queries GitHub API and displays information. To modify issues, claim work, or transition phases, use other skills like ghe-claim, ghe-checkpoint, or ghe-transition.
How often should I check the status?
Check status at the start of every session to establish context. Check again after completing work to verify changes propagated correctly. Frequent checks help track workflow health over time.
What do the phase distributions mean?
Phases represent workflow stages: DEV (active development), TEST (verification), and REVIEW (final approval). Accumulation in any phase indicates potential bottlenecks. Balanced distribution suggests smooth workflow progress.
Does ghe-status work with private repositories?
Yes. ghe-status works with private repositories as long as the GitHub API token has appropriate read permissions for issues. The skill respects existing GitHub authentication.
What are workflow violations?
Workflow violations are instances where GitHub Elements conventions were not followed, such as missing checkpoints, improper phase transitions, or missing required labels. The status report flags these for attention.

๊ฐœ๋ฐœ์ž ์„ธ๋ถ€ ์ •๋ณด

์ž‘์„ฑ์ž

Emasoft

๋ผ์ด์„ ์Šค

MIT

๋ฆฌํฌ์ง€ํ† ๋ฆฌ

https://github.com/Emasoft/ghe-marketplace/tree/main/plugins/ghe/skills/ghe-status

์ฐธ์กฐ

main

ํŒŒ์ผ ๊ตฌ์กฐ

๐Ÿ“„ SKILL.md