菜单
Use when a feature is complete or wrapping up implementation in a Rails + React app. Records how the feature was built as a docs file and captures new reusable patterns into each repo's conventions file.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/marvs/kantan-dev --skill kantan-finish-feature命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when planning a feature or before writing implementation code in a Rails + React app. Produces an approved implementation plan, asking clarifying questions and grounding the plan in repo conventions and prior feature docs. Never starts implementation.
Use when implementation is complete, before reporting or marking any feature as done, and before finishing a feature in a Rails + React app. Mandatory review step of the Kantan workflow — never skip it. Performs an expert Rails + React code review of the changes against the plan, the repo conventions, and universal best practices.
Use when implementing Rails backend code — models, services, controllers, jobs, or APIs. Follows the backend repo's own conventions, applies test-driven development, and keeps the test suite and linter green.
正在显示 SKILL.md
| name | kantan-finish-feature |
| description | Use when a feature is complete or wrapping up implementation in a Rails + React app. Records how the feature was built as a docs file and captures new reusable patterns into each repo's conventions file. |
Run this after kantan-review-feature has passed (no Critical or Major findings remaining) and tests and linters are green on both stacks.
Before anything else, read <backend-root>/.kantan-dev/reviews/YYYYMMDD_feature_name.md (same slug as the idea/plan).
kantan-review-feature first, then return here.Verdict: APPROVED, STOP — blocking findings remain. Resolve them via the review loop first.APPROVED.Write every document and chat message from this skill in ASD-STE100 Simplified Technical English — a restricted form of English built for technical documents that a non-native reader must get right on one reading. Later agent sessions read these files too.
endpoint stays "endpoint", never "route" or "API surface".Create <backend-root>/.kantan-dev/docs/YYYYMMDD_feature_name.md (same slug as the idea/plan). One consolidated doc covering backend and frontend. Include:
Purpose: future agent sessions read these for context. Be concrete.
Review the changes for anything generic and reusable (not feature-specific): new service/controller/model patterns, testing helpers, component/API/state patterns, library integrations, migration conventions.
For each reusable pattern, update the relevant repo's conventions file — write to AGENTS.md if it exists, otherwise CLAUDE.md. Backend patterns go in the backend's file; frontend patterns go in that frontend's file. Keep entries concise and prescriptive (tell future agents what to do, not what was done).
Do NOT run git add or git commit. Leave all changes — code, docs, and conventions updates — for the user to review and push.