smartkit

Plugin smartkit in wenyue/SmartKit. Commands read from the repo's manifest — today.

Skills (59)

• maintain-third-party-skills

  Assess or implement first-time adoption and upgrades of third-party Skills maintained by this repository, identifying selection, integration risks, and necessary local adaptations.

• translate-agent-artifacts

  Translate final English first-party Rules and Skills into caller-specified Simplified-Chinese mirrors, including mirror moves and deletions.

• upgrade-smartkit

  Advance this repository's SmartKit release version and assess whether its changes require project setup migration.

• write-setup-authoring-blueprints

  Write or revise project authoring blueprints under setup-assets/blueprints for future project Rules or Skills.

• write-shared-rules-and-skills

  Author or revise one portable cross-project SmartKit Rule or Skill.

• change-set-verification

  在交接前验证已完成的连贯变更集，执行限定范围的规范化和项目必需检查，并报告有证据支持的结果。

• prepare-worktree-environment

  在已选定的 linked Git worktree 创建后首次使用、有证据表明当前任务所需环境前提缺失或过时，或用户明确请求准备时，为其准备环境并报告就绪状态。

• collect-todos

  将任务收集到项目声明的任务跟踪器，留待以后处理。

• create-worktree

  当会改变仓库状态的工作需要隔离的关联 Git worktree 时使用。

• diagnose-agent-session

  诊断一个当前或已结束的 Agent 会话中疑似异常的 token 用量、费用或执行情况。

• finish-worktree

  完成隔离 Git 关联工作树中的工作，完成后清理，或为未完成工作或明确的后续用途保留。

• maintain-project-config

  维护随项目共享、仅保留在本机，或备份到独立个人配置仓库的项目 Agent 配置。

• refactor-code

  重构一个具体代码目标，保留受支持的调用者可见行为和外部契约；或将开放式架构改进探索路由到相应流程。

• rename-code

  重命名一个已确定的代码符号或受版本控制的仓库路径，包括公开名称。

• review-for-humans

  按文件解释 PR、分支和本地改动，判断合理性与优雅性，协助用户选择后续行动。

• rule-code-comment

  用于涉及代码注释或文档注释的工作，包括覆盖范围判断和用户要求的评估。

• rule-code

  用于涉及任何语言代码的工作，包括用户要求的代码政策评估。

• rule-cpp

  用于 C++ 工作，包括用户要求的代码政策评估。

• rule-error-handling

  用于涉及操作结果或错误行为的工作，包括用户要求的评估。

• rule-flutter

  用于 Dart 或 Flutter 工作，包括用户要求的代码政策评估。

• rule-go

  用于 Go 工作，包括用户要求的代码政策评估。

• rule-python

  用于 Python 工作，包括用户要求的代码政策评估。

• setup-project-agents

  设置项目 Agent 并准备首版 OpenWiki，或从配置仓库更新或恢复本地配置。

• what-changes

  在实施前，以只读范围报告审查累积的预期改动。

• what-if

  判断用户提出的想法是否优于现状和替代方案，给出独立结论而不采取行动。

• write-rules-and-skills

  编写、修订或重写一个英文 Rule 或 Agent Skill。

• ask-matt

  Ask which skill or flow fits your situation. A router over the skills in this repo.

• code-review

  Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them s

• codebase-design

  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.

• diagnosing-bugs

  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

• diagram-design

  Create branded architecture, architecture delta, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, exploded axonometric, axonometric plan, Venn, py

• domain-modeling

  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

• grill-me

  A relentless interview to sharpen a plan or design.

• grill-with-docs

  A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

• grilling

  Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

• handoff

  Compact the current conversation into a handoff document for another agent to pick up.

• implement-spec

  Implement the result of /to-spec and /to-tickets in code.

• implement

  Implement a piece of work based on a spec or set of tickets.

• improve-codebase-architecture

  Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

• openwiki

  Search and read an existing repository OpenWiki when requested or needed to resolve a concrete architecture or dependency uncertainty, or initialize and update one through the resumable page-job lifecycle.

• ponytail-audit

  Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding explained in plain language. One-shot report, changes nothing. Use for "audit this codebase", "review the whole repo", "fin

• ponytail-debt

  List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report; saves a file only when authorized. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.

• ponytail-review

  Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain language. Use for technical-quality reviews of changes, commits

• ponytail

  Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains abo

• pr

  Use when writing a PR body.

• prototype

  Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

• research

  Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

• retro

  Conduct a retrospective on a coding session.

• setup-matt-pocock-skills

  Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

• tdd

  Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

• teach

  Teach the user a new skill or concept, within this workspace.

• to-questionnaire

  Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

• to-spec

  Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

• to-tickets
• triage
• wait-what
• wayfinder
• wizard
• writing-for-agents

Similar plugins