Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/tomevault-io/skills-registry --skill ghe-report명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
| Use when this capability is needed.
> Use when this capability is needed.
Review architecture and API design for the vfs-s3 project. Use when the user mentions @architect, asks to review an issue's design, discuss module boundaries, API shape, or architectural decisions for vfs-s3. Also trigger when the user wants to create an ADR (Architecture Decision Record) or evaluate a technical approach for the project. Intended for dispatch from Codex automation or Claude routines; GitHub trigger phrase: @vfs-s3-bot please prepare design doc Use when this capability is needed.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | ghe-report |
| description | | Use when this capability is needed. |
THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS.
Violation of this law invalidates all work produced.
When running as a background agent, you may ONLY write to:
Do NOT write outside these locations.
ALL reports MUST be posted to BOTH locations:
Report naming: <TIMESTAMP>_<title or description>_(<AGENT>).md
Timestamp format: YYYYMMDDHHMMSSTimezone
Example: 20251206200000GMT+01_status_report_(Hermes).md
ALL 11 agents write here: Athena, Hephaestus, Artemis, Hera, Themis, Mnemosyne, Hermes, Ares, Chronos, Argos Panoptes, Cerberus
REQUIREMENTS/ is SEPARATE - permanent design documents, never deleted.
Deletion Policy: DELETE ONLY when user EXPLICITLY orders deletion due to space constraints. DO NOT delete during normal cleanup.
Respects .claude/ghe.local.md:
enabled: If false, return minimal reportnotification_level: verbose/normal/quiet - affects detail levelstale_threshold_hours: Used for stale thread detectionPurpose: Generate detailed reports with metrics, health assessment, or epic analysis. More comprehensive than quick status.
Performance indicators and trends:
Workflow compliance assessment:
Single epic deep dive:
Spawn reporter agent with appropriate report type:
reporter(type="metrics") → Performance report
reporter(type="health") → Compliance report
reporter(type="epic", epic="epic-name") → Epic report
## GitHub Elements Metrics Report
### Throughput
| Metric | Value | Trend |
|--------|-------|-------|
| Features completed | N | +/- vs last week |
| Bugs fixed | N | +/- vs last week |
### Cycle Times
| Phase | Avg Duration | Issues Processed |
|-------|--------------|------------------|
| DEV | N sessions | N |
| TEST | N sessions | N |
| REVIEW | N sessions | N |
### Quality Metrics
- First-pass REVIEW rate: N%
- Demotion rate: N%
- Test coverage (avg): N%
## GitHub Elements Health Report
### Compliance Status
| Rule | Status | Notes |
|------|--------|-------|
| One thread at a time | PASS/FAIL | |
| Phase order | PASS/FAIL | |
| Checkpoint frequency | PASS/WARN | |
### Stale Threads
[Threads with no activity > 24h]
### Violation History
[Recent violations and resolutions]
### Overall Health
[HEALTHY / WARNINGS / CRITICAL]
## Epic Report: [Epic Name]
### Thread History
| Issue | Type | Status | Duration |
|-------|------|--------|----------|
### Current Phase
[Current phase with progress]
### Key Decisions
[Technical decisions made]
### Remaining Work
[Estimated remaining effort]
This skill provides DETAILED ANALYSIS. For a quick current-state overview, use ghe-status instead.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.