What is generate-contributor-guide?

A skill that studies a codebase to document its real development conventions and maintainer preferences. It can produce a contributor guide or a shorter set of repository rules.

Use it for onboarding, researching contribution patterns, or creating repository-local contributor documentation from code and project files.

It helps new contributors and coding agents follow how the repository is actually built, tested, organized, and reviewed.

generate-contributor-guide — Skill for Claude Code by JerryLookupU

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add JerryLookupU/klein-harness --skill generate-contributor-guide

Clone the repo

git clone --depth 1 https://github.com/JerryLookupU/klein-harness

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jerrylookupu/klein-harness/generate-contributor-guide/github.svg)](https://agentmods.dev/skills/jerrylookupu/klein-harness/generate-contributor-guide)

Your own site

<a href="https://agentmods.dev/skills/jerrylookupu/klein-harness/generate-contributor-guide"><img src="https://agentmods.dev/badge/skills/jerrylookupu/klein-harness/generate-contributor-guide/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jerrylookupu/klein-harness/generate-contributor-guide"><img src="https://agentmods.dev/badge/skills/jerrylookupu/klein-harness/generate-contributor-guide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,710 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00056	$0.01710
Opus 5	$0.00028	$0.00855
Sonnet 5	$0.00011	$0.00342
Haiku 4.5	$0.00006	$0.00171

Measured 10d ago against content hash 49d3b0c492d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

generate-contributor-guide scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/generate-contributor-guide/SKILL.md · 236 lines

How it starts

The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.

This Skill Is For

这个 skill 用于回答一个更具体的问题：

这个仓库的内部开发者到底怎么写代码、怎么组织改动、怎么验证和提交，而不是 README 表面上怎么说？

适合这些场景：

初次接手陌生仓库
外部贡献者要先对齐 maintainer 风格
项目已经有文档，但真实代码习惯散落在源码和提交历史里
需要把“贡献约定”沉淀成 Klein worker 可消费的热路径规范

这个 Skill 负责什么

识别技术栈和主要架构层
读取现有贡献文档、控制面文档和工程配置
抽样分析代表性代码文件，提炼真实约定
生成完整分析稿
在需要时把稳定规则蒸馏进 .harness/standards.md 或项目 AGENTS.md

这个 Skill 不负责什么

默认把唯一输出写死到 .claude/contributor-guide.md
把一堆泛化最佳实践伪装成“本仓库约定”
在证据不足时瞎编风格规则
无端重写整份 AGENTS.md 或 .harness/standards.md

Preferred Output Surfaces

先选一个完整分析稿落点，不要默认双写：

.harness/research/contributor-guide.md
- 仓库已经有 .harness/
- 这份分析主要给 orchestrator / worker / operator 消费
- 更像 repo-local research memo
docs/contributor-guide.md
- 用户希望提交到仓库
- 仓库更偏 docs-first
- 需要给人类贡献者长期阅读

可选蒸馏输出：

.harness/standards.md
- 适合可执行、可验证、稳定的工程规则
项目根 AGENTS.md 的一个小型 managed section
- 只适合短小的协作/执行规则
- 不要把整份 contributor guide 倒进去

Read Order

先读 repo-local 规则面，再读代码。

默认顺序：

README.md
项目根 AGENTS.md（如果存在）
.harness/standards.md（如果存在）
CONTRIBUTING.md / .github/CONTRIBUTING.md
.github/PULL_REQUEST_TEMPLATE.md / issue templates
lint / format / test / build 配置
最近 40 到 80 条 git history
各层代表性源码和测试

如果仓库已经有 contributor guide：

先读它
再判断应该更新、补充，还是另写 research memo

Progressive Disclosure

不要一次性把整个仓库读完。

先识别当前栈，再读取 references/analysis-checklist.md 里对应的部分。

只加载相关 section：

repo-wide
JS / TS backend
React / frontend
Python
Go
Ruby / Rails
tests / CI / release

Working Order

1. 先判断目标是“研究稿”还是“热规范”

默认先写完整分析稿，再决定要不要蒸馏。

不要上来就改：

.harness/standards.md
AGENTS.md

2. 检测技术栈与主要层

优先看：

package.json
go.mod
pyproject.toml
Cargo.toml
Gemfile
pom.xml
*.csproj

然后识别主要层：

models / entities
handlers / controllers / API
services / jobs / background work
frontend components / state / styling
tests
CI / release / commit flow

如果某层文件很少，把它并入相邻层，不要机械分太细。

3. 读已有规则，不要只看源码

Read the full file on GitHub · 236 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/analysis-checklist.md 2.4 KB

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 236 lines · 56 tokens per session scan A 49d3b0c492d0

Subscribe to this mod's changes

generate-contributor-guide is a skill published in the GitHub repository JerryLookupU/klein-harness (11 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 1,710 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens