بنقرة واحدة
dotfiles
يحتوي dotfiles على 17 من skills المجمعة من yuk1ty، مع تغطية مهنية على مستوى المستودع وصفحات skill داخل الموقع.
Skills في هذا المستودع
Orchestrates the full development workflow: research → plan → implement, with human review checkpoints between each phase. Use this skill when starting to implement a new feature end-to-end.
Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Control herdr from inside it. Manage workspaces and tabs, split panes, spawn agents, read output, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDR_ENV=1).
Monitor a PR's CI, re-arm on each iteration, ignore known-flaky errors, stop when green
Reads annotations left by the user and updates the entire document based on their content.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
This is a task to create an implementation plan. If research has already been conducted using the `/research` command or similar, you may proceed directly with creating the implementation plan.
Conduct thorough pre-task research to deeply understand the structure of code areas targeted for modification. Use this skill whenever the user asks you to investigate, explore, analyze, or understand a codebase before making changes — especially before implementing new features, fixing bugs, or refactoring. Trigger this skill when the user says things like "research X", "understand how Y works", "investigate Z before implementing", "/research", or when they're about to make changes and clearly need deep context first. Don't wait to be explicitly asked — if someone is about to modify unfamiliar code, proactively research it first.
Control herdr from inside it. Manage workspaces and tabs, split panes, spawn agents, read output, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDR_ENV=1).
日本語の技術文書・書籍原稿の文章規範。整形(一文一行、引用ブロック、脚注、コラム記法)、段落と論証の構成(パラグラフライティング)、論証の厳密さ(ツッコミどころの除去)、読み手の負荷の管理、視点と語り、演出の抑制、LLM っぽい空句の禁止、冗長の排除を定める。日本語で技術書の章、草稿、記事、解説文を書くとき、または推敲・リライトするときに使用する。
Implement features using Kent Beck's Test-Driven Development (TDD) methodology. Use this skill when the user asks to write code via TDD, follow the Red-Green-Refactor cycle, or build a feature test-first. Guides the workflow of building a test list, writing one failing test at a time, making it pass with minimal production code, and refactoring before moving to the next test.
Create a git commit
Implement features using Kent Beck's Test-Driven Development (TDD) methodology. Use this skill when the user asks to write code via TDD, follow the Red-Green-Refactor cycle, or build a feature test-first. Guides the workflow of building a test list, writing one failing test at a time, making it pass with minimal production code, and refactoring before moving to the next test.
Conduct thorough pre-task research to deeply understand the structure of code areas targeted for modification. Use this skill whenever the user asks you to investigate, explore, analyze, or understand a codebase before making changes — especially before implementing new features, fixing bugs, or refactoring. Trigger this skill when the user says things like "research X", "understand how Y works", "investigate Z before implementing", "/research", or when they're about to make changes and clearly need deep context first. Don't wait to be explicitly asked — if someone is about to modify unfamiliar code, proactively research it first.
This is a task to create an implementation plan. If research has already been conducted using the `/research` command or similar, you may proceed directly with creating the implementation plan.
Create a git commit