A code-review guide based on Martin Fowler’s ideas about refactoring, code structure, and readable design. Refactoring means improving code’s structure without changing what it does.
A .NET instrumentation workflow that adds structured EventSource events and configures automatic crash dumps with dotnet-monitor. EventSource records selected runtime events that can be collected later for diagnosis.
A debugging helper that adds structured runtime log messages to .NET code using the standard logging system. It follows an error path through methods, branches, loops, and external calls.
Import external documents into the project archive. Two modes: → records (format conversion with TL;DR) for specs and reports, or → knowledge (multi-agent parallel organization with dedup/merge) for technical references and wiki dumps. Use when user wants to import external docs, zread output, spec documents, or…
A project workflow for compiling software, publishing its build output, and running the published application. It uses commands defined in a project file and supports running the published app on Windows.
A fitting tool for correcting coarse machine positioning by comparing point-cloud coordinates with their known world coordinates. It analyzes the errors and fits correction parameters for the current positioning process.
A code-review workflow focused on making code shorter, clearer, and closer to the project's real needs. It checks for overdesign, unnecessary abstractions, confusing names, duplicated types, redundant code, and unused defensive logic.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
A commit workflow that stages project changes and creates a Chinese Conventional Commit message, using a format such as a change type followed by a Chinese summary.
A document-creation workflow for making welding records and reports in a specified Feishu cloud-documents folder. It can also prepare a summary and, after confirmation, send the document link through a Feishu webhook.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
A workflow for sending text messages to a Feishu group through a webhook, which is a URL that lets software post messages to another service. It uses a PowerShell 7 script and UTF-8 text files for Chinese messages.
A structured method for moving selected changes between Git branches when the branches have diverged significantly. Instead of merging everything at once, it groups changes by purpose and rebuilds each approved group on the target branch.
A guided workflow for creating a GitLab issue, which is a tracked record of a bug, task, or feature request. It helps turn a developer’s description into an issue with the project’s required labels.
A workflow for creating a GitLab merge request, which is a request to review and merge code from one branch into another. It checks the repository state, target branch, authentication, and existing requests before creating one.
A set of instructions for managing GitLab project work, including issues, labels, milestones, and merge requests. GitLab is a service for hosting code and coordinating changes with a team.
Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: