ncaq/konoka

ncaq/konoka

Skill Claude CodeCodex

Part of commit

Commit message style guidelines. Use when writing or proposing git commit messages, including direct git commit commands outside the /commit skill.

ncaq/konoka

Skill Claude CodeCodex

Part of commit

Generate a commit message from staged changes, then let the user review before committing in manual mode or commit without confirmation in auto mode. Use when the user wants to commit changes or create a git commit.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Use bracket or with-style functions to guarantee resource cleanup even on exceptions instead of separate do blocks. Use when writing or reviewing Haskell code that acquires and releases resources.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Update Cabal project index-state to the latest timestamp. Use when it needs to bump the cabal index-state.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Use cabal with --disable-optimization for development builds and tests, and add --enable-tests to avoid rebuilds. Use when running or suggesting cabal build or test commands in Haskell development.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Do not throw exceptions from pure code with error or throw, give exceptions structured types, and never silently swallow errors in IO. Use when writing or reviewing Haskell error handling, exceptions, or IO code.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Explicitly enumerate Haskell module exports instead of exporting everything implicitly, and use re-export sparingly. Use when writing or reviewing Haskell module export lists.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Do not discard a function's final value with return (), pure (), or void; adjust the type to return the value and let the caller discard it when unneeded. Use when writing or reviewing Haskell functions that return unit or discard results.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

A Haskell custom Prelude library, meaning a replacement for the language’s usual starter module. It provides a single `Himari` import for commonly used types, functions, environment handling, and logging.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Prefer MonadIO and MonadUnliftIO type classes over using IO directly, and avoid redundant liftIO. Use when writing or reviewing Haskell IO actions, monad transformers, or type class abstractions.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Haskell language extension and language edition (GHC2024/GHC2021) selection policy. Use when configuring or reviewing Haskell language extensions, cabal default-extensions, or default-language.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Use the lens library, generating accessors with makeFieldsId for NoFieldSelectors records, export accessors together with their type classes, and prefer lens or OverloadedRecordDot over pattern matching. Use when writing or reviewing Haskell code that uses lens, records, or field access.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Avoid mutable variables like IORef, STRef, and ST in Haskell and prefer immutable records. Use STM variables such as TVar for thread communication. Use when writing or reviewing Haskell code that uses mutable state or concurrency.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Avoid partial functions such as head, fromJust, read, and (!!) in Haskell. Prefer total functions, Maybe-returning variants, and other safe alternatives. Use when writing or reviewing Haskell code that accesses lists, parses strings, or handles Maybe.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Prefer Text over String for text data, and use ByteString for binary or non-Unicode data. Use when writing or reviewing Haskell code that handles strings, text, or byte data.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Distinguish mkName and newName in Template Haskell. Use mkName to capture existing names and newName for fresh non-colliding names. Use when writing or reviewing Template Haskell code that generates names.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

When testing Either values, compare the value directly with shouldBe instead of checking isLeft, so test failures show the actual value. Use when writing or reviewing Haskell test code that asserts on Either or similar values.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Name Haskell test modules after the module under test with a Spec suffix in the same namespace. Use when writing or reviewing Haskell test module names or test file organization.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Avoid overusing threadDelay because time-dependent code is unstable and unportable. Prefer synchronization variables like TMVar or retry combinators. Use when writing or reviewing Haskell code that delays threads, waits, or polls.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Forbid unsafe Haskell functions such as unsafePerformIO, unsafeCoerce, and other unsafe-prefixed functions. Use when writing or reviewing Haskell code that uses any unsafe-prefixed function.

ncaq/konoka

Skill Claude CodeCodex

Part of haskell-tasuke

Do not disable GHC or hlint warnings. Suppress them only per module with OPTIONSGHC or annotations for justified exceptions. Use when writing or reviewing Haskell code, cabal files, or hlint configuration that disables warnings.

ncaq/konoka

Skill Claude CodeCodex

Part of kyosei

Use when you need to review code for quality, maintainability, and adherence to best practices. Examples: After implementing a new feature or function When refactoring existing code Before committing significant changes When uncertain about code quality.

ncaq/konoka

Skill Claude CodeCodex

Part of kyosei

Review dependency changes and impact. Use when analyzing PR dependency additions, removals, and version changes.

ncaq/konoka

Skill Claude CodeCodex

Part of kyosei

Use when you need to verify that code documentation is accurate, complete, and up-to-date. Use this skill after: Implementing new features that require documentation updates Modifying existing APIs or functions Completing a logical chunk of code that needs documentation review Preparing code for review/release.