oh-my-customcodex 0.1.0

package/templates/.claude/skills/dev-refactor/SKILL.md

@@ -0,0 +1,234 @@
+---
+name: dev-refactor
+description: Refactor code for better structure and patterns
+scope: core
+argument-hint: "<file-or-directory> [--lang <language>] [--spec]"
+user-invocable: true
+---
+
+# Code Refactoring Skill
+
+Refactor code for better structure, naming, and patterns using language-specific expert agents.
+
+## When NOT to Use
+
+| Scenario | Better Alternative |
+|----------|--------------------|
+| Renaming only (no structural change) | IDE rename refactoring or `sed` |
+| Formatting cleanup | Run formatter (`prettier`, `gofmt`, `black`) |
+| No test coverage for target code | Write tests first (`/structured-dev-cycle`) |
+| Moving files between directories | `git mv` via mgr-gitnerd |
+
+**Pre-execution check**: Verify test coverage exists for the refactoring target. Refactoring without tests risks silent regressions.
+
+## Pre-flight Guards
+
+Before executing the refactoring workflow, the agent MUST run these checks:
+
+### Guard 1: Test Coverage Check
+**Level**: WARN
+**Check**: Verify test files exist for the refactoring target
+```bash
+# For target file src/module/foo.ts, check for:
+# - src/module/foo.test.ts
+# - src/module/foo.spec.ts
+# - tests/module/foo.test.ts
+# - test/module/foo.test.ts
+# - __tests__/module/foo.test.ts
+# For Go: foo_test.go in same package
+# For Python: test_foo.py or foo_test.py
+```
+**Action**: `[Pre-flight] WARN: No test file found for {target}. Refactoring without tests risks silent regressions. Consider writing tests first (/structured-dev-cycle).`
+
+### Guard 2: Rename-Only Detection
+**Level**: INFO
+**Check**: If the user request is purely about renaming (no structural change)
+```
+# Keyword detection in user request
+keywords: rename, 이름 변경, 이름 바꿔, rename variable, rename function
+# AND no structural keywords
+structural_keywords: extract, split, merge, restructure, reorganize, decompose
+```
+**Action**: `[Pre-flight] INFO: For rename-only refactoring, IDE rename (F2) or sed is faster and safer (handles all references). Proceeding with full refactoring.`
+
+### Guard 3: Formatting-Only Request Detection
+**Level**: INFO
+**Check**: If the request is about formatting or style cleanup
+```
+# Keyword detection
+keywords: format, formatting, indent, indentation, 포맷, 스타일, whitespace, spacing
+```
+**Action**: `[Pre-flight] INFO: For formatting cleanup, run the appropriate formatter (prettier, gofmt, black, rustfmt). Proceeding with full refactoring.`
+
+### Guard 4: File Move Detection
+**Level**: INFO
+**Check**: If the request is about moving files between directories
+```
+# Keyword detection
+keywords: move file, move to, 파일 이동, 옮겨, relocate, reorganize files
+# AND no code-level changes mentioned
+```
+**Action**: `[Pre-flight] INFO: For file moves without code changes, use git mv via mgr-gitnerd to preserve git history.`
+
+### Display Format
+
+```
+[Pre-flight] dev-refactor
+├── Test coverage: WARN — no test file for src/utils.ts
+├── Rename-only: PASS
+├── Formatting-only: PASS
+└── File move: PASS
+Result: PROCEED WITH CAUTION (0 GATE, 1 WARN, 0 INFO)
+```
+
+If any GATE: block and suggest prerequisite.
+If any WARN: show warning, ask user to confirm.
+If only PASS/INFO: proceed automatically.
+
+## Parameters
+
+| Name | Type | Required | Description |
+|------|------|----------|-------------|
+| path | string | yes | File or directory to refactor |
+
+## Options
+
+```
+--lang, -l       Language (auto-detected if not specified)
+                 Values: go, python, rust, kotlin, typescript, java
+--focus, -f      Focus area (structure, naming, patterns, all)
+--dry-run        Show proposed changes without applying
+--verbose, -v    Detailed output
+```
+
+## Workflow
+
+```
+0. Run pre-flight guards (MUST complete before proceeding)
+1. Detect language (or use --lang)
+2. Select appropriate expert agent
+3. Load language-specific skill
+4. Analyze code structure
+5. Propose refactoring changes
+6. Apply changes (if not --dry-run)
+```
+
+## Agent Selection
+
+| File Extension | Agent | Skill |
+|----------------|-------|-------|
+| .go | lang-golang-expert | go-best-practices |
+| .py | lang-python-expert | python-best-practices |
+| .rs | lang-rust-expert | rust-best-practices |
+| .kt | lang-kotlin-expert | kotlin-best-practices |
+| .ts, .tsx | lang-typescript-expert | typescript-best-practices |
+| .java | be-springboot-expert | springboot-best-practices |
+| .jsx, .js (React) | fe-vercel-agent | react-best-practices |
+
+## Refactoring Categories
+
+| Category | Description |
+|----------|-------------|
+| structure | File/module organization, package structure |
+| naming | Variable, function, type naming conventions |
+| patterns | Design patterns, idiomatic code |
+| duplication | Extract common code, reduce repetition |
+| complexity | Simplify complex functions, reduce nesting |
+
+## Output Format
+
+### Dry Run
+```
+[dev:refactor src/utils.go --dry-run]
+
+┌─ Agent: lang-golang-expert (sw-engineer)
+├─ Skill: go-best-practices
+└─ File: src/utils.go
+
+Analysis:
+
+[Structure] Lines 10-45
+  Issue: Function too long (35 lines)
+  Suggest: Extract helper functions
+
+[Naming] Line 12
+  Issue: Abbreviation in function name
+  Found: func procData()
+  Suggest: func processData()
+
+[Patterns] Lines 20-30
+  Issue: Repeated error handling pattern
+  Suggest: Create handleError() helper
+
+Proposed Changes:
+  1. Extract lines 15-25 into validateInput()
+  2. Rename procData → processData
+  3. Create handleError() helper function
+
+No changes made (dry-run mode).
+Run without --dry-run to apply changes.
+```
+
+### Apply Changes
+```
+[dev:refactor src/utils.go]
+
+┌─ Agent: lang-golang-expert (sw-engineer)
+├─ Skill: go-best-practices
+└─ File: src/utils.go
+
+Refactoring:
+
+[1/3] Extracting validateInput()...
+  ✓ Created function at line 50
+  ✓ Updated calls at lines 15, 22
+
+[2/3] Renaming procData → processData...
+  ✓ Renamed function definition
+  ✓ Updated 3 call sites
+
+[3/3] Creating handleError() helper...
+  ✓ Created function at line 60
+  ✓ Replaced 5 error handling blocks
+
+Summary:
+  Changes applied: 3
+  Lines modified: 28
+  Functions added: 2
+  Functions renamed: 1
+
+Recommendation: Run tests to verify changes.
+```
+
+## Spec Mode (`--spec`)
+
+When the `--spec` flag is present, refactoring is guided by the target's canonical specification:
+
+### Workflow
+
+1. **Load spec**: Read `.codex/specs/<agent-name>.spec.md` (generated by `/omcodex:takeover`)
+   - If spec doesn't exist, run takeover first: `/omcodex:takeover <name>`
+2. **Extract invariants**: Parse the spec's `## Invariants` section as pre-flight guard constraints
+3. **Refactor**: Perform normal refactoring (per existing workflow)
+4. **Verify invariants**: After refactoring, check each invariant still holds:
+   ```
+   [Spec Verification]
+   ├── ✓ Invariant 1: {description} — PASS
+   ├── ✓ Invariant 2: {description} — PASS
+   └── ✗ Invariant 3: {description} — FAIL (reason)
+   ```
+5. **Regenerate spec**: If refactoring changed the contract, run `/omcodex:takeover <name>` to update
+
+### When to Use
+
+| Scenario | Use `--spec`? |
+|----------|--------------|
+| Refactoring agent internals | Yes — preserves declared invariants |
+| Renaming/restructuring skill | Yes — ensures contract stability |
+| Simple code cleanup | No — overhead not justified |
+| Adding new capability | No — spec will change anyway |
+
+### Prerequisites
+
+- `.codex/specs/<name>.spec.md` must exist (or will be auto-generated via takeover)
+- Target must be an agent or skill (not arbitrary code)

package/templates/.claude/skills/dev-review/SKILL.md

@@ -0,0 +1,172 @@
+---
+name: dev-review
+description: Review code against language-specific best practices
+scope: core
+argument-hint: "<file-or-directory> [--lang <language>]"
+user-invocable: true
+---
+
+# Code Review Skill
+
+Review code for best practices using language-specific expert agents.
+
+## When NOT to Use
+
+| Scenario | Better Alternative |
+|----------|--------------------|
+| Formatting/style issues only | Run linter or formatter directly (`prettier`, `gofmt`, `black`) |
+| Single syntax error | IDE/LSP diagnostics |
+| Auto-generated code | Skip — generated code follows its own conventions |
+| Pre-commit quick check | Git hooks with linter integration |
+
+**Pre-execution check**: If the issue is purely formatting, run the appropriate formatter first.
+
+## Pre-flight Guards
+
+Before executing the review workflow, the agent MUST run these checks:
+
+### Guard 1: Auto-generated Code Detection
+**Level**: WARN
+**Check**: Scan target files for auto-generation markers
+```bash
+# Detection patterns (any match = WARN)
+grep -rl "DO NOT EDIT" {target} 2>/dev/null
+grep -rl "auto-generated" {target} 2>/dev/null
+grep -rl "@generated" {target} 2>/dev/null
+# File pattern detection
+# *.gen.*, *.pb.go, */generated/*, */proto/*, *_generated.*, *.g.dart
+```
+**Action**: `[Pre-flight] WARN: Auto-generated code detected in {file}. Generated code follows its own conventions — review may produce false positives. Continue? [Y/n]`
+
+### Guard 2: Formatting-Only Changes Detection
+**Level**: INFO
+**Check**: If reviewing changed files (not full codebase), check if changes are formatting-only
+```bash
+# If git diff is available for the target
+git diff --stat {target} | grep -E '^\s+\d+ files? changed'
+# Compare with whitespace-ignored diff
+git diff -w {target}
+# If -w diff is empty but regular diff has changes → formatting only
+```
+**Action**: `[Pre-flight] INFO: Changes in {file} appear to be formatting-only. Consider running the appropriate formatter instead (prettier, gofmt, black).`
+
+### Guard 3: Single Syntax Error Detection
+**Level**: INFO
+**Check**: If target is a single file and the request mentions "error", "syntax", or "broken"
+```
+# Keyword detection in user request
+keywords: error, syntax, broken, doesn't compile, won't build
+# Single file check
+target is exactly 1 file (not a directory)
+```
+**Action**: `[Pre-flight] INFO: For single syntax errors, IDE/LSP diagnostics are faster. Proceeding with full review.`
+
+### Guard 4: Linter/Formatter Available Detection
+**Level**: INFO
+**Check**: Detect if a project-appropriate linter exists
+```bash
+# Check for linter configs in project root
+ls .eslintrc* .prettierrc* biome.json .golangci.yml pyproject.toml .rubocop.yml 2>/dev/null
+```
+**Action**: `[Pre-flight] INFO: Linter config found ({config}). For style-only issues, run the linter directly.`
+
+### Display Format
+
+```
+[Pre-flight] dev-review
+├── Auto-generated code: PASS
+├── Formatting-only changes: INFO — whitespace changes in src/util.ts
+├── Single syntax error: PASS
+└── Linter available: INFO — .eslintrc.json found
+Result: PROCEED (0 GATE, 0 WARN, 2 INFO)
+```
+
+If any GATE: block and suggest alternative.
+If any WARN: show warning, ask user to confirm.
+If only PASS/INFO: proceed automatically.
+
+## Parameters
+
+| Name | Type | Required | Description |
+|------|------|----------|-------------|
+| path | string | yes | File or directory to review |
+
+## Options
+
+```
+--lang, -l       Language (auto-detected if not specified)
+                 Values: go, python, rust, kotlin, typescript, java
+--focus, -f      Focus area (style, performance, security, all)
+--verbose, -v    Detailed output
+```
+
+## Workflow
+
+```
+0. Run pre-flight guards (see ## Pre-flight Guards)
+1. Detect language (or use --lang)
+2. Select appropriate expert agent
+3. Load language-specific skill
+4. Analyze code against best practices
+5. Generate review report
+```
+6. **Artifact persistence** (optional): Review agent saves findings to:
+   ```
+   .codex/outputs/sessions/{YYYY-MM-DD}/dev-review-{HHmmss}.md
+   ```
+   With metadata header:
+   ```markdown
+   ---
+   skill: dev-review
+   date: {ISO-8601 with timezone}
+   query: "{original user query}"
+   ---
+   ```
+   The review agent creates the directory and writes the artifact before returning results (R010 compliance).
+
+## Agent Selection
+
+| File Extension | Agent | Skill |
+|----------------|-------|-------|
+| .go | lang-golang-expert | go-best-practices |
+| .py | lang-python-expert | python-best-practices |
+| .rs | lang-rust-expert | rust-best-practices |
+| .kt | lang-kotlin-expert | kotlin-best-practices |
+| .ts, .tsx | lang-typescript-expert | typescript-best-practices |
+| .java | be-springboot-expert | springboot-best-practices |
+| .jsx, .js (React) | fe-vercel-agent | react-best-practices |
+
+## Output Format
+
+```
+[dev:review src/main.go]
+
+┌─ Agent: lang-golang-expert (sw-engineer)
+├─ Skill: go-best-practices
+└─ File: src/main.go
+
+Review Results:
+
+[Style] Line 15
+  Issue: Variable name should be camelCase
+  Found: user_name
+  Suggest: userName
+
+[Error Handling] Line 42
+  Issue: Error not checked
+  Found: file.Close()
+  Suggest: if err := file.Close(); err != nil { ... }
+
+[Performance] Line 78
+  Issue: Inefficient string concatenation in loop
+  Found: str += item
+  Suggest: Use strings.Builder
+
+Summary:
+  Style: 1 issue
+  Error Handling: 1 issue
+  Performance: 1 issue
+  Total: 3 issues
+
+Recommendation: Fix error handling issues first.
+```