Development skills

Component type definitions, settings schemas, directory patterns, and validation rules for the fullstack-typescript tech pack.

The English summary is being prepared. Showing the original description.

Use when EZ_math_model coder or packaging fails repeatedly with the same error and needs root-cause analysis instead of another blind retry.

The English summary is being prepared. Showing the original description.

Use after EZ_math_model coding has produced src/*.py and before packaging when code quality, reuse, vectorization, naming, or unnecessary complexity should be reviewed without changing behavior.

The English summary is being prepared. Showing the original description.

Render a dashboard of the current Claude Code session — message counts, token usage, cache read/write, dollar cost, context %, lines changed, cost-per-turn sparkline, and a tool-call histogram — parsed from the session transcript JSONL by a bundled bash script. One bash call, zero analysis, zero confirmation. Optionally pass a session id to inspect a different session. Use when the user asks for session stats, usage, token or cost breakdown, or a session dashboard.

The English summary is being prepared. Showing the original description.

Draft a changelog for the next release by summarizing git commits since the last tag. Use only when the user asks to draft release notes, write a changelog entry, or prepare the next version's notes — never trigger automatically.

The English summary is being prepared. Showing the original description.

Phase 5 of 5 — triage-first review orchestrator; dispatches up to 17 domain checks in parallel and compiles one report. Use only when the user asks to run Phase 5 or review a PR, branch, or set of changes — never trigger automatically after writing code.

The English summary is being prepared. Showing the original description.

After an issue's PR has squash-merged on GitHub and its issue has closed: fast-forward the default branch, remove the issue-numbered nested worktree (.worktrees/<issue#>), and delete the local feature branch. Use when the user says to finish, tear down, or clean up a lane or worktree for a merged issue.

The English summary is being prepared. Showing the original description.

Install genuine per-session cost tracking for Claude Code by wiring bundled logger scripts into the user's statusline — preserving any existing statusline and hooks. Use when the user asks to set up, install, enable, or repair cost tracking / cost logging / session cost capture. Idempotent; safe to re-run.

The English summary is being prepared. Showing the original description.

Copy this repo's skills into another agent harness's skills directory by name — resolves the harness alias to its path via scripts/sync-targets.json and runs sync-skills.sh. Use only when the user asks to copy/sync/push the skills to another harness (oh-my-pi, opencode, kimi, codex, etc.) — never trigger automatically.

The English summary is being prepared. Showing the original description.

Systematic code review checklist and pre-commit quality gates for PRs. Use when: reviewing pull requests, checking code quality, before committing code. Keywords: review, PR, pull request, checklist, quality, commit, 審查, 檢查, 簽入.

The English summary is being prepared. Showing the original description.

Run verification commands and confirm output before claiming success

The English summary is being prepared. Showing the original description.

Create isolated git worktrees with smart directory selection and safety verification

The English summary is being prepared. Showing the original description.

Name code by what it does in the domain, not how it's implemented or its history

The English summary is being prepared. Showing the original description.

Choose names that fully and accurately describe what the variable represents

The English summary is being prepared. Showing the original description.

Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features

The English summary is being prepared. Showing the original description.

Use each variable for exactly one purpose - no hybrid coupling or hidden meanings

The English summary is being prepared. Showing the original description.

Write comments explaining WHAT and WHY, never temporal context or history

The English summary is being prepared. Showing the original description.

Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation

The English summary is being prepared. Showing the original description.

Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search

The English summary is being prepared. Showing the original description.

Validate at every layer data passes through to make bugs impossible

The English summary is being prepared. Showing the original description.

Systematically trace bugs backward through call stack to find original trigger

The English summary is being prepared. Showing the original description.

Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.

The English summary is being prepared. Showing the original description.

Try 2-3 different approaches before implementing - don't settle for first design you think of

The English summary is being prepared. Showing the original description.

Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)

The English summary is being prepared. Showing the original description.