ycs77-skills

Plugin ycs77-skills from marketplace ycs77 in ycs77/skills. Commands read from the repo's manifest — 3 days ago.

Skills (34)

• 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.

• commit-message

  Generates concise, intent-driven Git commit messages in imperative mood. Use when the user asks to create, write, draft, make, generate, or suggest a commit message, says "commit these changes" or "what should I commit?", or asks for help with a Git commit.

• 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.

• 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.

• github-release-notes

  Generate GitHub release notes for the upcoming version, following the Keep a Changelog 1.1.0 spec. Use when the user is preparing a release and asks to "draft release notes", "generate release notes", "create GitHub release notes", "產生 release notes", "準備發布", "產生發布說明", or similar pre-release phrasin

• 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.

• no-verify

  Skip verification steps; only linting, typechecks, and formatting are allowed

• 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.

• scan-repo

  GitHub 開源專案安全掃描工具。當使用者貼上 GitHub URL、詢問某個套件或專案是否安全可信、想在安裝前評估風險，或提到「幫我看一下這個 repo」、「這個專案安不安全」、「我想用這個開源套件」、「這個工具可以信任嗎」時，務必使用此 skill。輸出專案概覽、靜態弱點分析、供應鏈風險、Issues 安全回報、維護者評估與風險總結。

• scan-skill

  當使用者想審查 AI Agent skill 目錄的安全風險時使用，例如「掃描 skill」、「安全審查」、「檢查技能安全性」、「scan skills」、「audit skill」、「check skill for risks」、「security audit skill」。遞迴掃描所有 SKILL.md 及相關程式碼，透過靜態 pattern 比對與 AI 語意分析，輸出含風險等級分類與改善建議的 Markdown 安全報告。

• 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

  Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

• triage

  Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

• wait-what

  Stop. That last message did not land: re-pitch it.

• wayfinder

  Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

• wizard

  Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can pe

• write-social-post

  撰寫像在通訊群組跟同溫層分享一個發現的社群貼文——把文章、趨勢、開源專案、技術工具寫成有觀點、有判斷、口語自然的分享文。適合行動端與群組快速閱讀。觸發：分享文、社群貼文、寫一篇分享、貼群組、把文章改寫成分享。

• writing-for-agents

  Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

• ycs77-vue

  Lucas Yang's opinionated Vue 3 conventions for SFC block order, inline props/emits types, reactive form state, complex ref type assertions, same-name bindings, and template props access.