ask-matt
無料Ask which skill or flow fits your situation. A router over the skills in this repo.
日本語の概要は準備中です。原文の説明を表示しています。
Create or change Knock workflows from code. Use when adding a Notification kind, changing a workflow's template or category, or when a trigger returns 404 because the workflow is missing.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Knock workflows are code. Every one is pushed and committed by npm run knock:push-workflows through Knock's Management API, so the dashboard and scripts/knock-wizard.sh stay out of the loop.
The script reads two sources of truth:
WORKFLOWS and CATEGORY_KEYS in app/lib/notifications.knock.server.ts, which also send the Notification.TEMPLATES in scripts/push-knock-workflows.ts. It is typed by NotificationKind, so a new kind fails the typecheck until its template is added.npm run typecheck.npm run knock:push-workflows. It upserts and commits every workflow in Development, overwriting what's there, so re-running it is the fix for any drift. Add -- --promote production to promote them to Production.Done when the script prints a ✓ for every workflow.
The script needs KNOCK_SERVICE_TOKEN and KNOCK_FEED_CHANNEL_ID in .env. The app's secret key only triggers workflows and is rejected by the Management API. When the token is missing, ask the human to create one in the Knock dashboard, under account settings → Service tokens.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Ask which skill or flow fits your situation. A router over the skills in this repo.
日本語の概要は準備中です。原文の説明を表示しています。
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/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Database schema changes — generate the migration, update the seed, reseed. Use when editing `app/db/schema.ts`, when adding or altering a table, column, or enum, or when `npm run db:seed` fails to start.
日本語の概要は準備中です。原文の説明を表示しています。
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 discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
日本語の概要は準備中です。原文の説明を表示しています。