Review code for quality, simplicity, and common mistakes before declaring work complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this when writing or reviewing Haskell code. Covers error handling, type safety, idiomatic patterns, HLint compliance, Aeson usage, and testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
undefined or error as placeholdersMaybe/Either cases explicitly — no silent ignoringText over Stringnewtype wrappers for domain typeshead, tail, and other partial functionsOverloadedRecordDot (add pragma to modules that use the syntax)DisambiguateRecordFields and DuplicateRecordFields for simple field namesencode/decode on itIf .hlint.yaml exists in the project root, run hlint on every modified file. Fix ALL warnings before considering the task complete.
If ghcid.txt exists in the project, check it after every code change for compile errors. Do not proceed until it is clean. If this file does not exist, use whatever build workflow the project documents.
When adding or deleting .hs modules: update the .cabal file, or run hpack if package.yaml exists.
If the project uses relude (check .cabal or package.yaml dependencies), also follow RELUDE.md for idiomatic substitutions.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Review code for quality, simplicity, and common mistakes before declaring work complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Do a task end-to-end — implement, PR, CI loop, ship. ONLY invoke when the user explicitly types `/do` or `$do`; never auto-select from a natural-language request, even one that sounds like an end-to-end task.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Iteratively study and apply elegant coding patterns. Each iteration - understand the code, research what simple and elegant code looks like, apply learnings, verify with CI. Use as a standalone refactoring pass or when the user asks to make code more elegant, simple, or idiomatic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit code for correctness and rigor — logic errors, silent error swallowing, wishful thinking, and unjustified fallbacks. This is not a style review; it's a logic review. Use when you want a focused correctness audit separate from the full code-police pass.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write engaging PR titles and descriptions for any forge (GitHub today; Bitbucket planned). Use when creating or updating PRs. Leads with narrative paragraphs and reaches for lists, tables, and diagrams when content is genuinely structured.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.