add-language-hook
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: add-language-hook
description: Add a chunking hook for a new or existing language in the ingest pipeline. Use when this capabil…
category: ai
runtime: no special runtime
---
# add-language-hook output preview
## PART A: Task fit
- Use case: Add a chunking hook for a new or existing language in the ingest pipeline. Use when this capability is needed. Hooks live in src/core/domains/ingest/pipeline/chunker/hooks/<language>/. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Step 1: Check if the language directory exists / Step 2: Understand the hook interface / Step 3: Create the hook file” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Add a chunking hook for a new or existing language in the ingest pipeline. Use when this capability is needed. Hooks live in src/core/domains/ingest/pipeline/chunker/hooks/<language>/. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Step 1: Check if the language directory exists / Step 2: Understand the hook interface / Step 3: Create the hook file” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Step 1: Check if the language directory exists / Step 2: Understand the hook interface / Step 3: Create the hook file”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: add-language-hook
description: Add a chunking hook for a new or existing language in the ingest pipeline. Use when this capabil…
category: ai
source: tomevault-io/skills-registry
---
# add-language-hook
## When to use
- Add a chunking hook for a new or existing language in the ingest pipeline. Use when this capability is needed. Hooks l…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Step 1: Check if the language directory exists / Step 2: Understand the hook interface / Step 3: Create the hook file” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "add-language-hook" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Step 1: Check if the language directory exists / Step 2: Understand the hook interface / Step 3: Create the hook file
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Add Language Hook
Add a chunking hook for a new or existing language in the ingest pipeline.
Hooks live in src/core/domains/ingest/pipeline/chunker/hooks/<language>/.
Step 1: Check if the language directory exists
Look in chunker/hooks/ for an existing <language>/ directory.
- Exists — you're adding a new hook to an existing language. Read
<language>/index.tsto see the current hook chain. - Doesn't exist — you're adding hooks for a new language. Create
<language>/directory.
Step 2: Understand the hook interface
Read chunker/hooks/types.ts. Every hook implements:
interface ChunkingHook {
name: string;
process: (ctx: HookContext) => void;
}
HookContext provides:
- Read-only:
containerNode,validChildren,code,codeLines,config - Mutable:
excludedRows,methodPrefixes,methodStartLines,bodyChunks
Hooks mutate the context in order. Earlier hooks populate state that later hooks
read (e.g., comment-capture populates excludedRows, body-chunker reads it).
Step 3: Create the hook file
Create hooks/<language>/<hook-name>.ts. Follow existing patterns:
comment-capture.ts— extracts doc comments, marks rows as excludedclass-body-chunker.ts— splits large class bodies into method-level chunks
Name the exported hook: <language><Purpose>Hook (e.g.,
rubyCommentCaptureHook, typescriptBodyChunkingHook).
Step 4: Create or update the barrel
hooks/<language>/index.ts exports the ordered hook array:
import type { ChunkingHook } from "../types.js";
import { myCommentCaptureHook } from "./comment-capture.js";
import { myBodyChunkingHook } from "./class-body-chunker.js";
export const <language>Hooks: ChunkingHook[] = [
myCommentCaptureHook, // Order matters: comment-capture first
myBodyChunkingHook, // Body chunker reads excludedRows
];
Step 5: Register in language config
Edit chunker/config.ts. Find the language entry in LANGUAGE_DEFINITIONS and
add the hooks property:
import { <language>Hooks } from "./hooks/<language>/index.js";
// In LANGUAGE_DEFINITIONS:
<language>: {
// ... existing config ...
hooks: <language>Hooks,
},
If the language doesn't exist in LANGUAGE_DEFINITIONS, add the full entry with
loadModule, extractLanguage, chunkableTypes, and hooks.
Step 6: Write tests
Tests go in tests/core/domains/ingest/pipeline/chunker/hooks/<language>/.
Follow existing test patterns in typescript/ or ruby/ directories.
Each hook should have its own test file testing the process() function with a
real HookContext (use createHookContext() from types.ts).
Step 7: Verify
npx tsc --noEmit
npx vitest run tests/core/domains/ingest/pipeline/chunker/hooks/<language>/
Source: artk0de/TeaRAGs-MCP — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review