mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +00:00
Release 1.1.2 — the default path works end to end
Fix release for 1.1.1: the minimal path end to end, engine commands that run on Godot, Unity and Unreal, hook warnings you can see, and verdicts that say when they could not check. Details in CHANGELOG.md; upgrade steps in UPGRADING.md (v1.1.1 → v1.1.2). Fixes #67 Fixes #131 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WuJn2FdynEybfL5KC697nJ
This commit is contained in:
Donchitos
co-authored by
Claude Opus 5.5
Claude Opus 5.5
parent
7ed2c3e9c4
commit
b21fa0f7f2
@@ -3,7 +3,7 @@ name: tech-debt
|
||||
description: "Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register."
|
||||
argument-hint: "[scan|add|prioritize|report]"
|
||||
user-invocable: true
|
||||
allowed-tools: Read, Glob, Grep, Write, AskUserQuestion, Bash(bash "*/.claude/skills/tech-debt/../../hooks/yaml-helper.sh" resolve_config *)
|
||||
allowed-tools: Read, Glob, Grep, Write, Edit, AskUserQuestion, Bash(bash "*/.claude/skills/tech-debt/../../hooks/yaml-helper.sh" resolve_config *)
|
||||
model: sonnet
|
||||
---
|
||||
|
||||
@@ -30,7 +30,8 @@ If no subcommand is provided, output usage and stop. Verdict: **FAIL** — missi
|
||||
|
||||
## Phase 2A: Scan Mode
|
||||
|
||||
Search the codebase for debt indicators:
|
||||
Search the **code root** (resolve per `.claude/docs/code-root-resolution.md`:
|
||||
`src/`, `Assets/` or `Source/` by engine) for debt indicators:
|
||||
|
||||
- `TODO` comments (count and categorize)
|
||||
- `FIXME` comments (these are bugs disguised as debt)
|
||||
@@ -50,10 +51,11 @@ Categorize each finding:
|
||||
- **Performance Debt**: Known slow paths, unoptimized queries, memory issues
|
||||
|
||||
**Before presenting anything, establish that there was something to scan.**
|
||||
Count the source files the scan actually covered. If that count is **zero** —
|
||||
no `src/` directory, or it holds no source files — report:
|
||||
Count the source files the scan actually covered. If the code root is
|
||||
unresolved, report `NOT ASSESSED — code root unresolved` and stop as below. If
|
||||
that count is **zero** — the code root is absent, or holds no source files — report:
|
||||
|
||||
> **NOT ASSESSED — no source files to scan.** `src/` contains no code, so
|
||||
> **NOT ASSESSED — no source files to scan.** The code root contains no code, so
|
||||
> "no debt indicators found" would be a statement about an empty search, not
|
||||
> about the codebase. Run this once implementation is under way.
|
||||
|
||||
@@ -69,7 +71,11 @@ Present the findings to the user.
|
||||
|
||||
Ask: "May I write these findings to `docs/tech-debt-register.md`?"
|
||||
|
||||
If yes, update the register (append new entries, do not overwrite existing ones). Verdict: **COMPLETE** — scan findings written to register.
|
||||
If yes, update the register, never overwriting it. **Match before appending:** a
|
||||
finding with the same file and the same kind of debt as an existing `Open` entry
|
||||
updates that entry instead of adding a duplicate. An existing `Open` entry whose
|
||||
pattern is no longer in its file is proposed as `Resolved [date]` — list those and
|
||||
include them in the same approval. Verdict: **COMPLETE** — scan findings written to register.
|
||||
|
||||
If no, stop here. Verdict: **BLOCKED** — user declined write.
|
||||
|
||||
@@ -77,7 +83,7 @@ If no, stop here. Verdict: **BLOCKED** — user declined write.
|
||||
|
||||
## Phase 2B: Add Mode
|
||||
|
||||
Ask the user for the description, affected files, and impact if left unfixed (plain text prompts).
|
||||
Ask the user for the description and affected files (plain text prompts).
|
||||
|
||||
Then use `AskUserQuestion` to collect the **category**:
|
||||
- Prompt: "What category does this tech debt belong to?"
|
||||
@@ -97,11 +103,21 @@ Then use `AskUserQuestion` to collect the **estimated fix effort**:
|
||||
- `[C] L — Large (3–7 days)`
|
||||
- `[D] XL — Extra Large (over 1 week)`
|
||||
|
||||
Then use `AskUserQuestion` to collect the **impact if left unfixed** — the
|
||||
register's Impact column, which `/tech-debt prioritize` scores:
|
||||
- Prompt: "What does this cost if it is never fixed?"
|
||||
- Options: `[A] Low` / `[B] Med` / `[C] High` / `[D] Critical`
|
||||
|
||||
Present the complete new entry to the user.
|
||||
|
||||
Ask: "May I append this entry to `docs/tech-debt-register.md`?"
|
||||
**Match before appending:** if an existing `Open` entry already has the same
|
||||
file and the same category, show it to the user and ask whether to update that
|
||||
entry instead of adding a duplicate.
|
||||
|
||||
If yes, append the entry. Verdict: **COMPLETE** — entry added to register.
|
||||
Ask: "May I append this entry to `docs/tech-debt-register.md`?" (or, on a match,
|
||||
"May I update the existing entry instead?")
|
||||
|
||||
If yes, append the entry (or update the matched one). Verdict: **COMPLETE** — entry added to register.
|
||||
|
||||
If no, stop here. Verdict: **BLOCKED** — user declined write.
|
||||
|
||||
@@ -109,9 +125,15 @@ If no, stop here. Verdict: **BLOCKED** — user declined write.
|
||||
|
||||
## Phase 2C: Prioritize Mode
|
||||
|
||||
Read the debt register at `docs/tech-debt-register.md`.
|
||||
Read the debt register at `docs/tech-debt-register.md`. If it does not exist:
|
||||
Verdict: **NOT ASSESSED** — no register at `docs/tech-debt-register.md`; run
|
||||
`/tech-debt scan` first. Stop.
|
||||
|
||||
Score each item by: `(impact_if_unfixed × frequency_of_encounter) / fix_effort`
|
||||
Score each item from its own columns: `impact ÷ effort`, with Impact `Low` 1,
|
||||
`Med` 2, `High` 3, `Critical` 4 and Effort `S` 1, `M` 2, `L` 3, `XL` 4, rounded to
|
||||
one decimal and written to Priority. Higher scores first; ties go to the older
|
||||
`Added` date. An item whose Impact or Effort is `—` gets no score: list it after
|
||||
the scored items as "not scored — [column] not judged" rather than guessing one.
|
||||
|
||||
Re-sort the register by priority score and recommend which items to include in the next sprint.
|
||||
|
||||
@@ -127,12 +149,15 @@ If no, stop here. Verdict: **BLOCKED** — user declined write.
|
||||
|
||||
## Phase 2D: Report Mode
|
||||
|
||||
Read the debt register. Generate summary statistics:
|
||||
Read the debt register. If it does not exist: Verdict: **NOT ASSESSED** — no
|
||||
register to report on; run `/tech-debt scan` first. Stop.
|
||||
|
||||
- Total items by category
|
||||
- Total estimated fix effort
|
||||
- Items added vs resolved since last report
|
||||
- Trending direction (growing / stable / shrinking)
|
||||
Generate summary statistics:
|
||||
|
||||
- Open items by category, and total estimated fix effort for them
|
||||
- Items added and items resolved during the current sprint, from each entry's
|
||||
`Added` date and its `Resolved [date]` status
|
||||
- Trending direction (growing / stable / shrinking) — added vs resolved in that window
|
||||
|
||||
Flag any items that have been in the register for more than 3 sprints.
|
||||
|
||||
@@ -152,11 +177,32 @@ Output the report to the user. This mode is read-only — no files are written.
|
||||
Last updated: [Date]
|
||||
Total items: [N] | Estimated total effort: [T-shirt sizes summed]
|
||||
|
||||
| ID | Category | Description | Files | Effort | Impact | Priority | Added | Sprint |
|
||||
|----|----------|-------------|-------|--------|--------|----------|-------|--------|
|
||||
| TD-001 | [Cat] | [Description] | [files] | [S/M/L/XL] | [Low/Med/High/Critical] | [Score] | [Date] | [Sprint to fix or "Backlog"] |
|
||||
| ID | Category | Description | Files | Effort | Impact | Priority | Status | Added | Sprint |
|
||||
|----|----------|-------------|-------|--------|--------|----------|--------|-------|--------|
|
||||
| TD-001 | [Cat] | [Description] | [files] | [S/M/L/XL] | [Low/Med/High/Critical] | [Score] | [Open / Resolved YYYY-MM-DD / Accepted — reason] | [YYYY-MM-DD] | [Sprint to fix or "Backlog"] |
|
||||
```
|
||||
|
||||
Every skill that adds a row — this one, and `/story-done` when it logs
|
||||
deviations as debt — writes all ten columns in this order, and a skill that
|
||||
creates the file writes the header and table head above first:
|
||||
|
||||
- **ID** — `TD-` and three digits, one above the highest ID already in the
|
||||
register (`TD-001` in a new one). IDs are never reused.
|
||||
- **Category** — one of the six categories under Scan Mode, written without
|
||||
"Debt": `Architecture`, `Code Quality`, `Test`, `Documentation`, `Dependency`,
|
||||
`Performance` — the spelling `/story-done` writes, so Report Mode groups them once.
|
||||
- **Description** — what the debt is and why it was taken on.
|
||||
- **Files** — the affected paths, comma-separated; `—` when the debt has no single file.
|
||||
- **Effort** — `S`, `M`, `L` or `XL`, as in Add Mode; `—` if not yet estimated.
|
||||
- **Impact** — `Low`, `Med`, `High` or `Critical`: the cost if left unfixed; `—`
|
||||
if not yet judged.
|
||||
- **Priority** — the score `/tech-debt prioritize` writes; `—` until it runs.
|
||||
- **Status** — `Open` when added. `Resolved YYYY-MM-DD` records the day the debt
|
||||
was fixed; `Accepted — reason` records a conscious decision to keep it.
|
||||
- **Added** — the day the row was written, `YYYY-MM-DD`. Report Mode counts items
|
||||
added and resolved from this date and the `Resolved` date.
|
||||
- **Sprint** — the sprint scheduled to fix it, or `Backlog`.
|
||||
|
||||
### Rules
|
||||
- Tech debt is not inherently bad — it is a tool. The register tracks conscious decisions.
|
||||
- Every debt entry must explain WHY it was accepted (deadline, prototype, missing info)
|
||||
|
||||
Reference in New Issue
Block a user