Code Review
imbenrabi/Financial-Modeling-Prep-MCP-Server
Review a PR or working diff against this repo's intent layer (the AGENTS.md hierarchy), toolception pitfalls, and core invariants.
Use this standalone skill when the user asks to mine a repo's existing coding conventions for future AI coding, generate or refresh project rules with AGENTS.md/CLAUDE.md pointers, create Cursor or…
Install Spec Rule Miner
$ npx skills add leo-kuang-ai/spec-first --skill spec-rule-miner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install leo-kuang-ai/spec-first spec-rule-miner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/leo-kuang-ai/spec-first.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/spec-rule-miner .claude/skills/spec-rule-miner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "spec-rule-miner" agent skill from https://github.com/leo-kuang-ai/spec-first/tree/master/skills/spec-rule-miner into .claude/skills/spec-rule-miner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-rule-miner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/leo-kuang-ai/spec-first/tree/master/skills/spec-rule-minerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add leo-kuang-ai/spec-first --skill spec-rule-miner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install leo-kuang-ai/spec-first spec-rule-miner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/leo-kuang-ai/spec-first.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/spec-rule-miner .agents/skills/spec-rule-miner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spec-rule-miner" agent skill from https://github.com/leo-kuang-ai/spec-first/tree/master/skills/spec-rule-miner into .agents/skills/spec-rule-miner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-rule-miner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add leo-kuang-ai/spec-first --skill spec-rule-miner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install leo-kuang-ai/spec-first spec-rule-miner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/leo-kuang-ai/spec-first.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/spec-rule-miner .cursor/skills/spec-rule-miner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spec-rule-miner" agent skill from https://github.com/leo-kuang-ai/spec-first/tree/master/skills/spec-rule-miner into .cursor/skills/spec-rule-miner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-rule-miner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/leo-kuang-ai/spec-first.git --path skills/spec-rule-miner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add leo-kuang-ai/spec-first --skill spec-rule-miner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install leo-kuang-ai/spec-first spec-rule-miner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/leo-kuang-ai/spec-first.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/spec-rule-miner .gemini/skills/spec-rule-miner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spec-rule-miner" agent skill from https://github.com/leo-kuang-ai/spec-first/tree/master/skills/spec-rule-miner into .gemini/skills/spec-rule-miner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-rule-miner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install leo-kuang-ai/spec-first spec-rule-minerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add leo-kuang-ai/spec-first --skill spec-rule-miner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/leo-kuang-ai/spec-first.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/spec-rule-miner .github/skills/spec-rule-miner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spec-rule-miner" agent skill from https://github.com/leo-kuang-ai/spec-first/tree/master/skills/spec-rule-miner into .github/skills/spec-rule-miner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-rule-miner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add leo-kuang-ai/spec-first --skill spec-rule-miner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install leo-kuang-ai/spec-first spec-rule-miner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/leo-kuang-ai/spec-first.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/spec-rule-miner .opencode/skills/spec-rule-miner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spec-rule-miner" agent skill from https://github.com/leo-kuang-ai/spec-first/tree/master/skills/spec-rule-miner into .opencode/skills/spec-rule-miner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-rule-miner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
spec-rule-miner- GitHub stars
- 107
- Token cost
- ~1.2k tokens
- SKILL.md length
- 267 words
- Files
- 12 (incl. references)
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use this standalone skill when the user asks to mine a repo's existing coding conventions for future AI coding, generate or refresh project rules with AGENTS.md/CLAUDE.md pointers, create Cursor or…
- Works in 8 steps: 明确… → 盘点仓库形态：根目录、主要语言、源码目录、测试目录、配置文件、包/应用边界、生成物… → 过滤读取范围：跳过依赖、构建产物、锁文件、minified… → …
- Asks to mine a repos existing coding conventions for future AI coding
- SKILL.md covers Purpose, When To Use, When Not To Use and Inputs, plus 5 more sections
- Runs JavaScript and Shell scripts from its folder
What it does
Spec Rule Miner is an agent skill from leo-kuang-ai/spec-first. Use this standalone skill when the user asks to mine a repo's existing coding conventions for future AI coding, generate or refresh project rules with AGENTS.md/CLAUDE.md pointers, create Cursor or Qoder rule files from actual code evidence, or make AI-generated code follow a specific project's habits. Do not use for confirmed team policy governance, normal code review/debug/refactor work, linter/formatter configuration, generic best practices, unsupported tool rule files such as .cursorrules or .kiro/steering…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files, including reference files (for example `evals/cases/no-preview-no-write.yaml`, `evals/cases/r2-debug-request-routes-out.yaml` and `evals/cases/review-request-routes-out.yaml`).
It sits in Development, covering Linting and formatting, Agent instruction files and Code review. The repository describes itself as: 仓库原生 AI Coding Harness —— 把一次性 AI 对话变成可治理、可验证、可沉淀的工程闭环 · spec-first.cn. The licence is MIT.
When your agent uses it
- Asks to mine a repos existing coding conventions for future AI coding
- Refresh project rules with AGENTS.md/CLAUDE.md pointers
- Qoder rule files from actual code evidence
- Make AI-generated code follow a specific projects habits
Example prompts
- “/spec-rule-miner”
Requirements
- Node.js
- A Bash shell
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- 明确 target_repo。父级多仓工作区必须先锁定一个目标仓库；不清楚时只问一个问题。
- 盘点仓库形态：根目录、主要语言、源码目录、测试目录、配置文件、包/应用边界、生成物/依赖目录和已有 agent rule 文件；多包 workspace 必须识别具体子项目范围。
- 过滤读取范围：跳过依赖、构建产物、锁文件、minified 文件、二进制、vendored/generated 代码；大仓库或多包仓库使用分层抽样并在 preview 和 closeout 中披露样本包、未覆盖子项目和适用范围。
- 读取并记录证据。抽取前先读 Pattern Categories，用其中类别组织证据；大仓库可按其中 capability-class 边界使用 code-graph / project-graph 候选缩小阅读范围，但规则证据必须回到当前源码；配置已强制的…
- 合成规则：按 frequency x deviation from defaults 排序，保留高频且偏离默认的做法；多包规则必须区分跨包通用模式、包级专属模式和历史例外，旧项目反例只能写成“新增代码优先”或“不扩大例外”；除非证据在适用范围内压倒性一致，不使用全仓库绝对措辞。…
- Preview：展示将写入独立规则文件的规则块、入口引用文件、word count、采样/证据限制、适用包范围、历史例外、refresh diff/no-op 判断，以及每个规则组的代表性 source refs。规则正文不要包含挖掘过程元说明。
- 写入前读 Write Targets，按目标文件的 marker、frontmatter、pointer/inline 规则执行。默认把完整规则写入 docs/ai/project-rules.md，并让 AGENTS.md 与 CLAUDE.md 指向该文件。
- 收尾输出：列出写入文件、规则字数、是否采样、未写入的近邻工具文件、需要用户手动检查的限制；如果没有写文件，说明 preview-only 状态；如果因 headless 走默认写入，必须说明 headless_default_write 的证据来源。
What it can do on your machine
Read from SKILL.md and the folder at commit 74655dc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (JavaScript and Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Spec Rule Miner loads about 1.2k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 143 tokens; SKILL.md has 267 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from leo-kuang-ai/spec-first at commit 74655dc, republished under its MIT licence (© leo-kuang-ai). 267 words, ~1,174 tokens.
Download SKILL.mdSave it as
.claude/skills/spec-rule-miner/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.- name
- spec-rule-miner
- description
- Use this standalone skill when the user asks to mine a repo's existing coding conventions for future AI coding, generate or refresh project rules with AGENTS.md/CLAUDE.md pointers, create Cursor or Qoder rule files from actual code evidence, or make AI-generated code follow a specific project's habits. Do not use for confirmed team policy governance, normal code review/debug/refactor work, linter/formatter configuration, generic best practices, unsupported tool rule files such as .cursorrules or .kiro/steering rules, or generated runtime mirror edits.
Spec Rule Miner
Purpose
spec-rule-miner 从目标仓库的真实代码中提炼项目级 AI 编码规则，把完整规则写入独立规则文件，并让 AGENTS.md / CLAUDE.md 这类 host 入口文件引用该文件。它是 standalone skill，不是 spec-* public workflow。
核心产物是 <=1000 words 的项目规则块，规则必须来自当前目标仓库证据，而不是语言默认、个人偏好或通用最佳实践。
When To Use
- 使用本 skill：用户要“分析项目风格”“学习代码规范”“生成项目规则”“挖掘编码习惯”“让 AI 像团队一样写代码”，或明确要生成
AGENTS.md/CLAUDE.md引用入口、Cursor/Qoder 规则文件。
When Not To Use
- 不使用本 skill：用户要审查当前 diff、修复代码、重构、调试、写 lint/format 配置、生成通用语言规范，或治理 confirmed team policy。
- 近邻路由：confirmed team policy governance 已退役，不再提供专用入口；代码质量评审走
spec-code-review；实际实现或修复走spec-work（bug 根因排查走spec-debug）；创建或修改 spec-first source skill 走spec-write-skill。命中近邻路由时必须在回复中点名目的地 skill（例如：「这是代码评审请求，属于spec-code-review」）——只解释不匹配而不指路，owner 依然无路可走。点名之后不得在本会话内替目的地干活：直接修 bug、直接做代码评审、直接实现需求，都是把别的 workflow 的职责搬进 rule-miner 执行；用户的即时指令（「顺手修了」「直接审了」）不构成跨 workflow 代行授权——正确动作始终是点名目的地并交还路由。
Inputs
target_repo：必须是一个明确的本地目标仓库。- 当前仓库的人写源码、测试、配置和已有 agent rule 文件。
- 用户指定的输出目标；未指定时使用默认目标。
Outputs
rules_block：写入独立规则文件的纯规则正文，使用spec-rule-miner-start/spec-rule-miner-endmarkers。evidence_summary：每个规则组的代表性文件路径和样本限制；不写入规则文件，除非用户明确要求。target_files：默认独立规则文件、入口 pointer 文件与用户指定输出文件，说明 pointer 还是 inline。limitations：小样本、大仓库/多包抽样、混合语言、生成代码占比高、历史例外、冲突模式跳过、图候选未回源、refresh no-op、headless 默认写入等限制。
Hard Boundaries
- 只读目标仓库代码；不要修改业务源码、测试、构建配置或 formatter/linter 配置。
- Host-projected copies are outside this skill's rule targets；具体禁区见 Write Targets。宿主投影过期时从 source 运行
spec-first init修复。 - 写入独立规则文件和引用入口前必须 preview 规则正文和目标文件；交互可用时等待用户确认。只有用户明确要求直接写入，或宿主/调用参数明确证明当前运行是 headless/non-interactive，才使用默认目标；普通聊天里用户暂未回复不能算 headless。默认写入必须在 closeout 记录
headless_default_write、目标文件和限制。 - 不覆盖用户已有规则。读取目标文件后，只替换
spec-rule-minermarkers 内的旧块；无 markers 时追加；疑似旧版无 marker 输出时先询问替换还是追加。 - 非首次执行必须先重新取证并生成 candidate rules block，再与现有 canonical marked block / pointer 对比；无实质变化时不重写文件，closeout 记录
refresh_noop、采样范围和限制；有变化时 preview diff 后只替换 marker 内内容。 - 每条规则必须有当前仓库证据：默认至少 2 个文件支撑；小仓库样本不足时降级说明 sample-size；不确定或 50/50 分裂的模式不写成规则。
- 不泄露敏感信息：密钥、内部 URL、私有包名、账号、生产路径、安全实现细节只用于判断，不进入规则正文。
Workflow
- 明确
target_repo。父级多仓工作区必须先锁定一个目标仓库；不清楚时只问一个问题。 - 盘点仓库形态：根目录、主要语言、源码目录、测试目录、配置文件、包/应用边界、生成物/依赖目录和已有 agent rule 文件；多包 workspace 必须识别具体子项目范围。
- 过滤读取范围：跳过依赖、构建产物、锁文件、minified 文件、二进制、vendored/generated 代码；大仓库或多包仓库使用分层抽样并在 preview 和 closeout 中披露样本包、未覆盖子项目和适用范围。
- 读取并记录证据。抽取前先读 Pattern Categories，用其中类别组织证据；大仓库可按其中 capability-class 边界使用
code-graph/project-graph候选缩小阅读范围，但规则证据必须回到当前源码；配置已强制的 formatter/linter 规则只记录为“已由工具处理”，不要重复写入 AI 规则。 - 合成规则：按
frequency x deviation from defaults排序，保留高频且偏离默认的做法；多包规则必须区分跨包通用模式、包级专属模式和历史例外，旧项目反例只能写成“新增代码优先”或“不扩大例外”；除非证据在适用范围内压倒性一致，不使用全仓库绝对措辞。必须包含至少一个 hidden association 和至少一个 anti-pattern，除非证据明确不存在，并在 preview 限制中说明。规则正文可以包含适用范围和例外边界，这不算挖掘过程元说明。 - Preview：展示将写入独立规则文件的规则块、入口引用文件、word count、采样/证据限制、适用包范围、历史例外、refresh diff/no-op 判断，以及每个规则组的代表性 source refs。规则正文不要包含挖掘过程元说明。
- 写入前读 Write Targets，按目标文件的 marker、frontmatter、pointer/inline 规则执行。默认把完整规则写入
docs/ai/project-rules.md，并让AGENTS.md与CLAUDE.md指向该文件。 - 收尾输出：列出写入文件、规则字数、是否采样、未写入的近邻工具文件、需要用户手动检查的限制；如果没有写文件，说明 preview-only 状态；如果因 headless 走默认写入，必须说明
headless_default_write的证据来源。
Failure Modes
- 目标仓库没有可分析源码：不生成空规则，说明需要先有代码样本。
- 用户请求
.cursorrules、.kiro/steering/**、GitHub Copilot、Trae 或其他未支持规则文件：说明目标不在当前支持范围内，不猜路径、不写 pointer。 - 旧版无 marker 规则块无法安全识别：先询问“迁移到独立规则文件还是追加 pointer”。
- 证据不足、模式冲突或生成代码占比过高：降级为 limitations，不把不确定模式写成规则。
- 重新挖掘后与现有 marked block 无实质变化：不要为更新时间戳、排序或同义改写而重写文件；输出
refresh_noop和本次验证过的 source refs / limitations。
Quality Checks
- 规则块 <=1000 words；中文按连续中文字符粗略折算，宁可少写。
- 每条规则都能指向当前目标仓库证据；路径在文件树中真实存在。
- 规则只描述“当前项目如何做”，不提出重构建议，不评价团队好坏。
- 不把 language/framework 默认、formatter/linter 已强制项或生成代码习惯写成项目规则。
- 多包或混合框架仓库中，跨包规则只写稳定通用模式；包级规则必须带适用范围，并提示改具体子项目先跟随本包现有结构。
- 存在历史例外或旧项目反例时，用“新增代码优先沿用主模式”“不要扩大历史例外”这类收窄表达；不要写成“全仓库统一/只/永远/不得”的绝对事实。
docs/ai/project-rules.md是默认 canonical full rules；AGENTS.md、CLAUDE.md和其他非 inline 工具文件默认只写 pointer。
© leo-kuang-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 11 other files (references) in skills/spec-rule-miner of leo-kuang-ai/spec-first.
- SKILL.md
- evals/cases/no-preview-no-write.yaml
- evals/cases/r2-debug-request-routes-out.yaml
- evals/cases/review-request-routes-out.yaml
- evals/eval.yaml
- evals/fixtures/repos/mini-ledger/README.md
- evals/fixtures/repos/mini-ledger/package.json
- evals/fixtures/repos/mini-ledger/src/server.js
- evals/fixtures/scripts/check-preview-first.sh
- evals/trigger-cases.json
- references/pattern-categories.md
- references/write-targets.md
Open the folder on GitHubat commit 74655dc
Compare with similar skills
Spec Rule Miner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Spec Rule Miner this skillleo-kuang-ai/spec-first | 107 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Code Reviewimbenrabi/Financial-Modeling-Prep-MCP-Server | 150 | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Add Plugin Ruleeslint-config/airbnb-extended | 131 | — | ~646 | Automated safety check: Pass | MIT | |
| Lint Repository Markdowncodsen/codsen | 214 | — | ~832 | Automated safety check: Pass | MIT | |
| Shipmillionco/react-doctor | 15k | — | ~716 | Automated safety check: Pass | Custom licence | |
| Promptkitmicrosoft/PromptKit | 111 | — | ~420 | Automated safety check: Pass | MIT |
Similar skills
Add Plugin Rule
eslint-config/airbnb-extended
Fix the "<Plugin Updated with <rule" build error from script/checkUpdates.ts by adding a new or deprecated plugin rule to the right rules/ file.
Lint Repository Markdown
codsen/codsen
Keep the repository's linted Markdown passing npm run lint:markdown.
Ship
millionco/react-doctor
Take the current branch from done-coding to merge-ready in one pass — review the diff against AGENTS.md, deslop, commit and push, open a PR using rule-validate's PR copy, then babysit until mergeable.
- Official
Promptkit
microsoft/PromptKit
PromptKit composition engine. An agent skill from microsoft/PromptKit.
Megingiard Code Review
stormpanda/megingiard
Conduct a thorough code review of the current Git branch or specific files in Megingiard.
More from leo-kuang-ai/spec-first
All 35 skills in this repoSpec App Consistency Audit
leo-kuang-ai/spec-first
Audit mobile App PRD/Figma/local-source consistency across page routes, KMP/Clean Architecture, components, analytics, i18n, engineering quality, and industry lenses before runtime validation; use…
Spec Handoff
leo-kuang-ai/spec-first
Create a durable cross-session handoff or resume from a user-selected continuity source.
Spec Pov
leo-kuang-ai/spec-first
Give a decisive, project-grounded verdict on an external input — judged against the current project, not in the abstract.
Spec Resolve PR Feedback
leo-kuang-ai/spec-first
Resolve PR review feedback by evaluating validity and fixing issues with conflict-aware resolver dispatch.
Spec Riffrec Feedback Analysis
leo-kuang-ai/spec-first
Analyze explicit Riffrec product-feedback captures, including riffrec-.zip, the Riffrec session.json + events.json + recording.webm + voice.webm bundle, or media/notes the user identifies as a…
Spec Compound
leo-kuang-ai/spec-first
Document a recently solved problem or durable project vocabulary in docs/solutions/ or CONCEPTS.md.
Related
Categories
Questions about Spec Rule Miner
What does Spec Rule Miner do?
Use this standalone skill when the user asks to mine a repo's existing coding conventions for future AI coding, generate or refresh project rules with AGENTS.md/CLAUDE.md pointers, create Cursor or…. Spec Rule Miner is an agent skill from leo-kuang-ai/spec-first.md pointers, create Cursor or Qoder rule files from actual code evidence, or make AI-generated code follow a specific project's habits.
When should I use Spec Rule Miner?
Spec Rule Miner fits situations like: asks to mine a repos existing coding conventions for future AI coding; refresh project rules with AGENTS.md/CLAUDE.md pointers; qoder rule files from actual code evidence; make AI-generated code follow a specific projects habits.
How do I install Spec Rule Miner in Claude Code?
Run `npx skills add leo-kuang-ai/spec-first --skill spec-rule-miner -a claude-code`. Or copy the skill folder (skills/spec-rule-miner in leo-kuang-ai/spec-first) into .claude/skills/spec-rule-miner in your project. Claude Code loads it when a task matches its description.
How do I install Spec Rule Miner in Codex?
Run `npx skills add leo-kuang-ai/spec-first --skill spec-rule-miner -a codex`. Or copy the skill folder (skills/spec-rule-miner in leo-kuang-ai/spec-first) into .agents/skills/spec-rule-miner in your project. Codex loads it when a task matches its description.
Can I use Spec Rule Miner in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add leo-kuang-ai/spec-first --skill spec-rule-miner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec-rule-miner, .gemini/skills/spec-rule-miner, .github/skills/spec-rule-miner and .opencode/skills/spec-rule-miner in your project.
What does Spec Rule Miner need to run?
Going by SKILL.md and its folder, Spec Rule Miner needs JavaScript and a shell for the scripts in its folder. Our summary lists: Node.js; A Bash shell.
Does Spec Rule Miner access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Spec Rule Miner safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Spec Rule Miner use?
Spec Rule Miner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Spec Rule Miner use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.6k tokens, read only when the agent opens those files.
What are the alternatives to Spec Rule Miner?
Skills that share tags, products or a category with Spec Rule Miner: Code Review (imbenrabi/Financial-Modeling-Prep-MCP-Server, 150 stars), Add Plugin Rule (eslint-config/airbnb-extended, 131 stars), Lint Repository Markdown (codsen/codsen, 214 stars) and Ship (millionco/react-doctor, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Spec Rule Miner?
leo-kuang-ai (a GitHub user) maintains it in leo-kuang-ai/spec-first, which has 107 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 8, 2026.
Source: leo-kuang-ai/spec-first on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.