メニュー
Run QLTY lint and format checks during development to catch issues early, not just before commit. Use after significant code changes. Trigger phrases: "run linter", "check code quality", "format before commit".
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/DojoGenesis/plugins --skill qlty-during-developmentコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Run a bounded kata roll over the project's bring queue — start a session with an explicit target (reps or minutes), surface and stage exactly one bring per tick, log the outcome only on the human's word, then advance. Use when the user says "start a roll", "roll for N reps", "do a 25-minute roll", "tick", "next rep", "resolve this tick", "skip this tick", or "pause/resume/end the roll".
Set up the kata roll in a project that already runs (or is starting) the bring loop — confirm bring/ exists, explain where the roll's own ledger lives, walk through the opt-in timer, and make the two-plugin coexistence with bring-loop explicit. Use when the user says "set up kata-harness", "install the roll plugin", "add rolls on top of bring-loop", or asks how the timed roll relates to their daily bring.
Produces markdown memory artifacts (conversation summaries, seed files, philosophical reflections, doc updates) and a dated compression log by distilling a long conversation into its essential decisions and learnings. For the lighter, routine end-of-session wrap-up, use `session-compression` instead — this skill is for a long conversation that needs the fuller multi-artifact treatment. Use when: "compress this context", "distill this conversation", "create a memory artifact", "condense this history", "extract key wisdom before handoff".
SOC 職業分類に基づく
SKILL.md を表示中
| name | qlty-during-development |
| description | Run QLTY lint and format checks during development to catch issues early, not just before commit. Use after significant code changes. Trigger phrases: "run linter", "check code quality", "format before commit". |
| user-invocable | false |
Run QLTY checks during code writing to catch issues early.
Run QLTY after significant code changes:
# Quick lint check
qlty check
# Format code
qlty fmt
# Check specific files
qlty check src/sdk/providers.ts
# Auto-fix issues
qlty check --fix
After writing code:
qlty check on changed filesqlty fmt to ensure formatting