Skip to content

smorky850612/Aurakit / skills/aura

All-in-one fullstack dev engine. /aura: 46 modes (build/fix/clean/deploy/review/spec/lore/ax/experiment/payment/debug/qa/orchestrate/escalate+), 6-layer security with 32 hooks, tiered models (ZERO/ECO/PRO/MAX), 8 languages, 16 specialized agents, SPEC/EARS/TRUST5/XLOOP/RALF/Autopus absorbed. ~55% token savings.

FileKindSize
SKILL.mdskill md29.2 KB
resources/agent-security.mdmarkdown4.2 KB
resources/agent-spawning.mdmarkdown5.9 KB
resources/agent-team.mdmarkdown5.7 KB
resources/archive-pipeline.mdmarkdown3.5 KB
resources/autopus-agent-teams.mdmarkdown6.8 KB
resources/autopus-ax-annotation.mdmarkdown6.1 KB
resources/autopus-executor-profiles.mdmarkdown9.9 KB
resources/autopus-experiment-loop.mdmarkdown5.9 KB
resources/autopus-lore-commit.mdmarkdown6.0 KB
resources/autopus-pipeline-v2.mdmarkdown8.5 KB
resources/autopus-spec-system.mdmarkdown4.8 KB
resources/autopus-validator-gates.mdmarkdown7.0 KB
resources/autopus-worktree-isolation.mdmarkdown4.6 KB
resources/baas-pipeline.mdmarkdown3.8 KB
resources/batch-pipeline.mdmarkdown4.9 KB
resources/brainstorming.mdmarkdown4.7 KB
resources/branch-finishing.mdmarkdown4.7 KB
resources/build-pipeline.mdmarkdown12.0 KB
resources/build-resolvers-cpp.mdmarkdown10.0 KB
resources/build-resolvers-go.mdmarkdown1.2 KB
resources/build-resolvers-java.mdmarkdown9.1 KB
resources/build-resolvers-kotlin.mdmarkdown8.7 KB
resources/build-resolvers-python.mdmarkdown9.0 KB
resources/build-resolvers-rust.mdmarkdown1.2 KB
resources/build-resolvers-swift.mdmarkdown11.9 KB
resources/build-resolvers.mdmarkdown1.6 KB
resources/business-skills.mdmarkdown7.0 KB
resources/cache-engineering.mdmarkdown6.6 KB
resources/clean-pipeline.mdmarkdown6.5 KB
resources/common-protocol.mdmarkdown7.4 KB
resources/config-schema.mdmarkdown3.0 KB
resources/cross-harness.mdmarkdown16.6 KB
resources/deploy-enterprise.mdmarkdown9.0 KB
resources/deploy-pipeline.mdmarkdown6.9 KB
resources/design-pipeline.mdmarkdown3.2 KB
resources/desktop-pipeline.mdmarkdown3.5 KB
resources/discovery-protocol.mdmarkdown3.3 KB
resources/e2e-pipeline.mdmarkdown7.7 KB
resources/explain-pipeline.mdmarkdown972 B
resources/fix-pipeline.mdmarkdown5.6 KB
resources/framework-patterns.mdmarkdown8.3 KB
resources/gap-check.mdmarkdown3.4 KB
resources/install-guide.mdmarkdown3.4 KB
resources/instinct-system.mdmarkdown6.8 KB
resources/iterate-pipeline.mdmarkdown2.5 KB
resources/language-reviewers.mdmarkdown18.5 KB
resources/loop-pipeline.mdmarkdown3.5 KB
resources/mcp-configs.mdmarkdown4.7 KB
resources/migrate-pipeline.mdmarkdown1.5 KB
resources/mobile-pipeline.mdmarkdown3.5 KB
resources/mode-reference.mdmarkdown6.1 KB
resources/model-routing.mdmarkdown9.1 KB
resources/orchestration-patterns.mdmarkdown5.9 KB
resources/payment-lemonsqueezy.mdmarkdown5.6 KB
resources/payment-pipeline.mdmarkdown10.6 KB
resources/payment-polar.mdmarkdown3.6 KB
resources/payment-steppay.mdmarkdown4.8 KB
resources/payment-stripe.mdmarkdown6.7 KB
resources/payment-toss.mdmarkdown7.2 KB
resources/pipeline-guide.mdmarkdown6.1 KB
resources/plan-pipeline.mdmarkdown2.4 KB
resources/pm-pipeline.mdmarkdown4.5 KB
resources/qa-pipeline.mdmarkdown8.8 KB
resources/report-pipeline.mdmarkdown3.0 KB
resources/review-pipeline.mdmarkdown8.0 KB
resources/rollback-pipeline.mdmarkdown1.3 KB
resources/security-rules.mdmarkdown17.5 KB
resources/snippets-guide.mdmarkdown4.6 KB
resources/status-dashboard.mdmarkdown5.3 KB
resources/style-guide.mdmarkdown2.7 KB
resources/systematic-debugging.mdmarkdown5.7 KB
resources/tdd-pipeline.mdmarkdown4.4 KB

resources/gap-check.md

View on GitHub
# AuraKit — Gap Check (설계 vs 구현 비교)

> REVIEW 모드 또는 `/aura gap:` 명령에서 로딩. 독립 실행 가능.

---

## 목적

설계 문서(Plan/Spec)와 실제 구현 코드 사이의 격차를 정량적으로 측정한다.
Match Rate를 0~100%로 표시하고 미구현 항목과 초과 구현 항목을 분류한다.

---

## 실행 순서

### Step 1: 설계 문서 위치 감지

```
우선순위:
1. 사용자가 명시한 경로
2. .aura/plan.md
3. .aura/design.md
4. docs/PLAN.md, docs/DESIGN.md, docs/SPEC.md
5. README.md (기능 목록 섹션)
→ 없으면: "설계 문서를 찾을 수 없습니다. 경로를 지정해주세요." 안내
```

### Step 2: 구현 파일 탐색 (Scout, model: haiku/sonnet(MAX))

```bash
# 주요 소스 파일 탐색
find src -type f \( -name "*.ts" -o -name "*.tsx" -o -name "*.py" -o -name "*.go" \) \
  | grep -v node_modules | grep -v .test.

# API 엔드포인트 추출
grep -rn "app\.\(get\|post\|put\|delete\|patch\)" src/
grep -rn "router\.\|route(" src/
grep -rn "export async function\|export function" src/app/api/

# 컴포넌트 목록 추출
find src -name "*.tsx" -o -name "*.jsx" | grep -v test

# 함수/클래스 목록 추출
grep -rn "^export\|^class\|^function\|^const " src/ | head -100
```

### Step 3: 설계 항목 추출

설계 문서에서 구현 요구사항 파싱:
- `[ ]` / `[x]` 체크박스 → 기능 목록
- `## Features` / `## 기능` 섹션 → 기능 목록
- API 엔드포인트 목록 (`GET /api/...`, `POST /api/...`)
- 컴포넌트 목록 (`<ComponentName>`)
- 함수/서비스 목록 (`functionName()`, `ServiceName`)

### Step 4: 매핑 분석

```
설계 항목 → 구현 코드 1:1 매핑:

✅ 구현됨   — 설계 항목이 코드에 존재
❌ 미구현   — 설계에 있지만 코드에 없음
⚠️ 부분구현 — 함수는 있지만 비어 있거나 TODO 상태
🆕 초과구현 — 설계에 없지만 코드에 추가됨
```

### Step 5: Match Rate 계산

```
Match Rate = (구현됨 + 부분구현 * 0.5) / 전체 설계 항목 * 100

기준:
≥ 90% → ✅ 설계 충실 (배포 가능)
70~89% → ⚠️ 부분 구현 (우선순위 보완 필요)
50~69% → ❌ 미흡 (추가 구현 필요)
< 50%  → 🔴 초기 단계 (대부분 미구현)
```

---

## 출력 포맷

```markdown
# AuraKit Gap Check Report
분석 시각: [ISO 8601]
설계 문서: [경로]
분석 범위: [파일 수]개 소스 파일

---

## 📊 Match Rate: [N]%

| 상태 | 항목 수 | 비율 |
|------|---------|------|
| ✅ 구현됨 | N | N% |
| ⚠️ 부분구현 | N | N% |
| ❌ 미구현 | N | N% |
| 🆕 초과구현 | N | — |

---

## ❌ 미구현 항목 ([N]개)

1. `[기능명]` — 설계: [설명] | 위치: 미생성
2. `GET /api/[endpoint]` — 라우트 핸들러 없음
...

## ⚠️ 부분구현 항목 ([N]개)

1. `[기능명]` @ `[파일:라인]` — TODO 주석 또는 빈 함수
...

## 🆕 설계 외 추가 항목 ([N]개)

1. `[기능명]` @ `[파일]` — 설계서에 미포함
...

---

## 🔧 권장 액션

Match Rate [N]%:
→ [다음 단계 제안]
→ `/aura build:[미구현 항목]` 으로 보완 가능
```

---

## 빠른 실행 명령

```
/aura gap:               → .aura/plan.md 자동 탐색
/aura gap:docs/SPEC.md   → 특정 문서 지정
/aura review:gap         → REVIEW 모드 내 gap check
```

---

*Gap Check — Match Rate 90% 이상이면 배포 준비 완료*
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall