tdp

Apply a local Git stash for testing before running tests

Revert the applied local test stash after testing is complete

Generate a commit message from the fixed format declared inside this skill. Use when the user asks for commit message, git commit title, 提交訊息, commit 訊息, or wants a project-specific message style without re-checking git history.

Write or update C# comments, including XML documentation comments plus single-line and multi-line explanatory comments, so a new engineer with no project background can understand the code. Use when implementing or revising C# classes, fields, properties, methods, constructors, or other members that need durable documentation comments.

Inspect project databases with DBHub read-only MCP tools, decide environment scope, and deliver standardized SQL scripts under sql files/local-db, sql files/test-db, and sql files/main-db. Use when feature work, bug fixing, schema investigation, data checking, seed data, migration prep, or deployment preparation depends on one or more databases exposed by the current workspace MCP tools.

Archive the specs folder and SQL work-item folders for a completed bugfix or feature branch. Use when a branch is merged or the work is done and specs/<type>/<slug> and sql files/*-db/<slug> folders should be moved to their respective archives locations under specs/archives/ and sql files/archives/.

Define a frontend skill entry that points to repository-local implementation, component reuse, file placement, formatting, and documentation standards for frontend work.

Implement plan.md tasks in order by delegating coding and categorized AC review to subagents. Use when plan.md already exists and each task should loop implement -> parallel category review reports -> read review reports until COMPLETE, while the final build task starts from build review first, where n must be replaced with the actual task number, without running final test-plan verification.

Convert supported local documents to Markdown through the workspace MarkItDown MCP server by staging the input under the markitdown_workdir_path and calling the tool with a file:///workdir/... URI.

Read and record durable project facts, decisions, constraints, and user-requested "記住" notes in MCP memory. Use when current work may depend on previously stored repo context, or when you should remember new repo-specific context for future work.

Set up or update plugin configuration in .claude/settings.local.json and create required companion files. Use when installing the plugin for the first time or when adding or adjusting environment variables and config files for db-management, memory, markitdown, or testing-and-proof skills.

Start a new bugfix or feature workflow for this repo. Use when a new requirement needs its own bugfix/ or feature/ branch, matching specs folder, and an initial goal.md created through user discussion before planning or coding.

Execute a requirement test-plan.md and write proof back into each test-n.md. Use when a bugfix or feature already has test-plan.md and the user wants ordered verification, browser screenshots, or non-browser evidence. This skill must determine the appropriate build command and run command based on the current project type, apply and restore the local test stash around each server-backed verification task, and delegate each verification task to a subagent that writes the corresponding test-n.md. Replace the n in every test-n file name with the actual task number.

Write plan.md, test-plan.md, and decomposed test-n.md files from an approved goal.md. Use when a requirement already has goal.md and now needs single-session implementation tasks with categorized AC, mandatory static checks, a final build task, and final verification tasks with evidence rules. Replace the n in every test-n file name with the actual task number.