GET STARTED · FIRST SEARCH

Installation and first search

Follow this minimal path to find inflections and read results with the native CLI. For Node.js, use the lightweight npm CLI below. Installation and CLI selection explains differences in file traversal and output.

Native CLI installation

On macOS and Linux, Homebrew installs the executable and matching morphology resources. See the installation guide for other distributions and source builds.

brew install seokminhong/brew/kfind
kfind --check-data

First search

걷다 is the lemma to find, and --pos verb specifies a verb. Standard input lets you try it without creating a file.

printf '길을 걸었다.\n' | kfind --pos verb 걷다

The result displays the source line 길을 걸었다.. It finds the inflected form 걸었다 even though its spelling differs from the query. A match returns exit code 0; no match returns 1; an error returns 2.

To search files, add paths after the query. -n is the native CLI option for line numbers.

kfind -n 걷다 src docs

Open the source at the reported path and line to check its meaning. With no paths, kfind searches piped input, or the current directory in an interactive terminal. Follow no-match checks when results differ from your expectations.

Lightweight npm CLI

On Node.js 20 or later, this command searches for the same lemma. The npm CLI outputs the matched substring, unlike native line output.

printf '길을 걸었다.\n' | npx @kfind/kfind@1.1.0 --pos verb 걷다

Use the JavaScript API to search strings in an application. The package does not include the full-POS lexicon; callers supply any additional resources required by the API as bytes.

POS, phrases, and alternatives

Use n: for nouns and v: for verbs. Spaces form an ordered phrase on the same line; | searches for any one of its single-atom alternatives.

kfind 'n:사용자 v:검증하다' src
kfind 'v:걷다 | n:사용자 | n:검증' src
kfind --literal 걸었다 docs

--literal searches the exact input form. Read query syntax for quoting and tags, and phrase search for gap limits.

Automation output

With the native CLI, specify resources, POS, boundary, and output explicitly. any returns broader candidates, so inspect their source context and exclude irrelevant results.

kfind --embedded --boundary any --pos verb --json 걷다 src

JSON Lines distinguishes native byte coordinates from npm UTF-16 coordinates. No matches does not guarantee that no relevant content exists.

Agent integration

Agents can run the commands above directly. To install session instructions and pre-execution hooks, read skill installation. Integration hooks block Korean patterns in rg, grep, and git grep unless fixed-string mode is explicit. Exact searches with -F, --fixed-strings, or fgrep are allowed.