chore(rebar): Pier_T_rebar 작업 폴더 초기 구성 및 외부 의존 파일 통합

- Code\rebar_pipeline, review_pipeline, pier-program을 정션에서 실제 폴더로 전환
- Code\rhino_mcp 및 CLAUDE_rhino배경.md 추가, .mcp.json은 PYTHONPATH로 새 위치 사용
- pier-program 내부 .git 제거(이력은 backup\pier-program_20261028.bundle에 보관)
- worktree 가이드 반영(CLAUDE.local.md, HANDOFF.md)
- D:\Rhino-MCP 경로 참조를 새 위치로 치환

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
ahnyongjooandClaude Sonnet 5.5 committed 2026-10-28 11:20:18 +09:00
commit 964a841de1
3978 files changed
+58013356

No files matched your search

@@ -0,0 +1,97 @@
---
name: skill-status
classification: workflow
classification-reason: "Reports loaded skill inventory across core and project layers. Read-only status check workflow."
deprecation-risk: none
description: |
Show loaded skill inventory — hmcmkit core vs project-local, conflicts, coverage gaps.
Triggers: skill-status, skill list, 스킬 상태, 스킬 목록.
argument-hint: "/skill-status [--detail] [--conflicts]"
user-invocable: true
allowed-tools:
- Read
- Glob
- Grep
- Bash
---
# skill-status - Skill Inventory Report
로드된 스킬 목록을 core(hmcmkit 기본)와 project-local로 구분하여 표시.
## Command: `/skill-status`
### Step 1: Scan Core Skills
1. Read hmcmkit core skills directory:
`~/.ai-agent/plugins/cache/hmcmkit-marketplace/hmcmkit/*/skills/`
2. For each skill directory, read SKILL.md frontmatter:
- name, classification, description (first line)
3. Count total core skills
### Step 2: Scan Project-Local Skills
1. Read project skills directory:
`.ai-agent/skills/project/*/SKILL.md`
2. For each skill, read frontmatter
3. Count total project skills
### Step 3: Detect Conflicts
1. Compare skill names between core and project
2. If same name exists in both: mark as "override" (project wins)
3. If project skill triggers overlap with core: mark as "shadow"
### Step 4: Display Report
```
Skill Status Report
====================
Layer: hmcmkit Core (v1.6.2)
Skills: 28 loaded
-----------------------------------------------
Name | Type | Classification
--------------------|------------|---------------
pdca | workflow | PDCA lifecycle
enterprise | workflow | Enterprise init
hmcmkit-rules | capability | Auto-apply rules
code-review | workflow | Code analysis
... (truncated)
Layer: Project-Local (hunikflow)
Skills: 8 loaded
-----------------------------------------------
Name | Type | Classification
--------------------|------------|---------------
btw | workflow | BTW suggestions
skill-create | workflow | Skill generator
skill-status | workflow | This report
hunikflow-model | capability | @Flow patterns
hunikflow-proxy | capability | DataProxy patterns
hunikflow-domain | capability | ERP domain logic
hunikflow-i18n | capability | i18n CSV guide
hunikflow-dynamic-api| capability | Dynamic API guide
Conflicts: 0 overrides, 0 shadows
Summary: 36 total skills (28 core + 8 project)
```
### Options
**`/skill-status --detail`**: Show full descriptions and trigger keywords for each skill.
**`/skill-status --conflicts`**: Show only skills with naming conflicts or trigger overlaps.
## Skill Layer Priority
```
Priority (high to low):
1. .ai-agent/skills/project/ (project-local, git-tracked)
2. ~/.ai-agent/plugins/.../skills/ (hmcmkit core, plugin-managed)
3. ~/.ai-agent/skills/ (user global, if any)
```
When a project skill has the same name as a core skill, the project skill takes precedence.
This is the "2-layer override" pattern.