メニュー
Stamp or verify a markdown doc's version/hash against the code it documents using the @repo/hashy CLI. Trigger on "hash this doc", "stamp AGENTS.md", "update doc hash", "hashy", "version this markdown", "check doc drift", or after editing an ideal-example doc.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Learning memos: concept → use case → example. Output markdown | mdx | html. Back = scenario OR code snippet. Trigger: memo, flashcard, /do-memo. Too broad → split first.
Conversion copywriter for homepage/landing/pricing/feature/about page copy. Use for "write copy," "improve this copy," "rewrite this page," "headline help," "CTA copy," "value prop," "tagline," "above the fold," "this copy is weak," "make this more compelling." Not for email copy (emails skill), popup copy (popups skill), pure line-edit of existing copy (copy-editing skill).
React UI component best practices for building consistent, accessible, and maintainable component libraries. Use this skill when writing, reviewing, or optimizing React components, styling patterns, or component APIs.
Accessibility auditor for HTML markup or live URLs. Trigger on "check accessibility", "audit a11y", "review HTML", "check-html", or pasted URL/code for a11y review.
Requirements Inference & Specification Architect. Use it when you're not sure that your requirements are clear enough for the engineering team to start working on them. This skill will ask you a series of questions to clarify any ambiguities in your requirements and produce a final, detailed specification document.
Generate a commitlint-compliant commit message with a description, prompt user for approval, and run git commit. Use when user asks to commit, create a commit, generate a commit message, or wants to stage and commit changes. NEVER runs git push. Uses git diff --cached to understand staged changes.
| name | hashy |
| description | Stamp or verify a markdown doc's version/hash against the code it documents using the @repo/hashy CLI. Trigger on "hash this doc", "stamp AGENTS.md", "update doc hash", "hashy", "version this markdown", "check doc drift", or after editing an ideal-example doc. |
Thin wrapper over the @repo/hashy CLI. Run it, report the result. Do not
re-implement hashing, edit frontmatter by hand, or read implementation files
yourself — the CLI owns that.
Check all inputs before running. Missing required → ask once, then continue.
| # | Input | Required | Rule |
|---|---|---|---|
| 1 | Module dir | Yes | Directory whose code is hashed. Missing → ask "Which module directory?". |
| 2 | Doc file | No | Markdown file inside the dir. Default AGENTS.md. |
| 3 | Mode | No | stamp (default, writes) or check (verify only, no writes). |
AGENTS.md) + mode (default stamp).pnpm --filter @repo/hashy buildnode packages/hashy/dist/cli.js <module-dir> <doc-file>node packages/hashy/dist/cli.js <module-dir> <doc-file> --checknode packages/hashy/dist/cli.js --manifest hashy.modules.txt<module-dir> <doc-file> line to
hashy.modules.txt so CI verifies it.version + hash (stamp) or pass/drift (check).check drift: report the stored vs computed hash and offer to re-stamp.version, hash, and file count.version/hash.AGENTS.md; default mode is stamp.check mode writes nothing — use it for verification and CI parity.