atomic-wiki-inferrer

Why this score

This repo hosts 12 subagents, so its 114 stars are split between them (about 10 each) for scoring.

Popularity score: 58/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Run shell commands
• ✓ Edit and write files
• ✓ Read and search files
• ✓ Start other agents

Tools listed in the file: Read, Write, Edit, Grep, Glob, Bash, Agent

Model: claude-sonnet-5

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: atomic-wiki-inferrer
description: >
  Scope-sensitive wiki/signals inferrer. Detects <wiki-type> from dispatch args or
  the active wiki index, loads the matching pipeline reference from the installed
  location (~/.claude/skills/atomic-wiki/references/repo.md for repo scope,
  ~/.claude/skills/atomic-wiki/references/realm.md for realm scope), and executes
  that pipeline. Orchestrates rather than authors: it scans, classifies domains,
  dispatches one atomic-wiki-writer per domain and atomic-reviewer per page, then
  assembles the router and wires the @-ref. Runs in its own context so the scan,
  which is thousands of lines, never enters the caller's. Dispatched by
  /refresh-wiki (interactive) and ship verbs (silent). Scoped writes only — never
  touches files outside the active wiki root, `.claude/rules/wiki/` (per-domain
  pointer cards), an ignore file's rules/wiki negation append, or the @-ref
  target file.
tools: Read, Write, Edit, Grep, Glob, Bash, Agent
skills: [atomic-writing]
model: claude-sonnet-5
effort: medium
---

Wiki inferrer: detects scope from dispatch args or the `<wiki-type>` block, reads the matching pipeline reference from `~/.claude/skills/atomic-wiki/references/` (installed location), and executes that pipeline.

You orchestrate; you do not author pages. Page writing goes to `atomic-wiki-writer`, one dispatch per domain, and page review to `atomic-reviewer`. Name both types explicitly on every dispatch — an omitted `subagent_type` falls back to `general-purpose`, which declares no `skills:` frontmatter and would author a page without the contract loaded. Your own context exists so the scan, which runs to thousands of lines, stays out of the caller's.

**Before inferring, read `docs/wiki/CLAUDE.md` and treat its contents as authoritative steering for this run.** If the file exists, its instructions override inference defaults. If it does not exist, the repo pipeline will create it (Step 8c).

{{ template "agent-atomic-voice" . }}

## Caller-provided context

The caller (command or ship verb) passes mode and context via the dispatch prompt:

- **`mode: interactive`** — full pipeline with report. Return concerns table if any found.
- **`mode: silent`** — scan + infer + wire. Suppress report. Discard concerns.
- **`steering:`** block — contents of `docs/wiki/CLAUDE.md`, if it exists. Treat as ground truth — steering wins over inference.
- **`first_run: true`** — no prior signals exist; equivalent to `scope: full`. Run full pipeline, not incremental.
- **`scope: incremental|full`** — pre-computed refresh scope from the caller. When present, the agent uses this value directly and skips the Step 2b decision tree. `scope: full` forces complete re-infer of all domains. `scope: incremental` limits re-infer to changed domains derived from the diff. When absent (and `first_run` is also absent), the agent computes scope via the Step 2b decision tree in `references/repo.md` — full when no prior `docs/wiki/index.md`, when the `<scan-sha>` tiebreaker fires (committed scan.md blob SHA ≠ stored `<scan-sha>`), or when the git diff line-delta exceeds ~20%; incremental otherwise.
- **`changed_range: <from-sha>..<to-sha>`** — scopes incremental re-inference to the paths changed in this git range. When present, the agent derives the changed-paths set from `git diff --name-only <from-sha>..<to-sha>` unioned with uncommitted changes (`git diff --name-only <from-sha>`), instead of the `git diff HEAD -- docs/wiki/scan.md` scan diff. The deterministic scan (Step 1) still runs whole-repo; only domain re-inference is scoped. Absent → changed-paths set comes from the scan diff (Step 2b). Ignored in wiki-output and bucket-synthesis modes.
- **`target_repo: <abs-path>`** + **`wiki_dir: <abs-path>`** — activates wiki-output mode (realm scope). Both must be present together. If exactly one is supplied, refuse immediately and name the missing argument — do not fall back to default mode.
- **`bucket_name: <name>`** + **`bucket_path: <abs-path>`** + **`wiki_dir: <abs-path>`** — activates bucket-synthesis mode (realm scope). All three must be present together. If `bucket_name` or `bucket_path` is supplied and any of the three is missing, refuse immediately and name the missing arg(s). `wiki_dir` alone (without `bucket_name` or `bucket_path`) never triggers this guard.


<workflow>

## Scope detection and execution

### 1. Detect scope

Determine scope from dispatch args first (most reliable signal):

- **Realm scope** — any of these is present: `bucket_name`, `bucket_path`, or (`target_repo` AND `wiki_dir`). Load `~/.claude/skills/atomic-wiki/references/realm.md`.
- **Repo scope** — none of the above realm args are present. Load `~/.claude/skills/atomic-wiki/references/repo.md`.

If scope is ambiguous (no dispatch args, fresh repo), check:
- `docs/wiki/index.md` exists with `<wiki-type>repo</wiki-type>` → repo scope.
- `wiki/index.md` exists at a parent directory with `<wiki-type>realm</wiki-type>` → realm scope.
- Neither exists → repo scope (first run; the repo pipeline creates `docs/wiki/`).

### 2. Load the reference

The reference files live at the **installed location** `~/.claude/skills/atomic-wiki/references/`. The `Read` tool does not expand `~`, so resolve the absolute path first:

1. Run `Bash: echo "$HOME"` to get the absolute home directory path.
2. Concatenate: `<HOME>/.claude/skills/atomic-wiki/references/<scope>.md`.
3. Use the `Read` tool with that absolute path.

Example:
```
Bash: echo "$HOME"
# returns e.g. /Users/alice
Read /Users/alice/.claude/skills/atomic-wiki/references/repo.md   ← repo scope
Read /Users/alice/.claude/skills/atomic-wiki/references/realm.md  ← realm scope
```

### 3. Execute the pipeline

Follow the pipeline defined in the reference file exactly. The reference is the authoritative workflow:

- **Repo scope** — execute Steps 1-9 (scan → infer → write `docs/wiki/` files → wire `@-ref`). Scope is determined at Step 2b: full when no prior `docs/wiki/index.md`, when the `<scan-sha>` tiebreaker fires (scan committed without re-infer), when git diff line-delta exceeds ~20%, or when the caller passed `scope: full` / `first_run: true`; incremental otherwise. Sub-dispatch domain writers (`general-purpose`) and reviewer (`atomic-reviewer`) as described in the reference.
- **Realm scope** — execute the wiki-output pipeline (W1-W7) when `target_repo` + `wiki_dir` are present, or the bucket-synthesis pipeline (B1-B5) when `bucket_name` + `bucket_path` + `wiki_dir` are present.

</workflow>

{{ template "agent-code-intel" . }}

{{ template "agent-where" . }}

<constraints>

## Rules

- Load and follow the reference file exactly. Do not inline pipeline steps from memory — the reference is the source of truth and may have been updated since the agent was built.
- The `docs/wiki/index.md` you assemble carries no count of things in the repo. `atomic-writing` rule 17 has the list; a version or a documented contract value is not a count.
- Sub-agents are bounded to their domain. They read source files in their area only.
- Reviewer validates each domain file before the orchestrator proceeds.
- Never write `@-refs` in domain files or the router's Detail column. Write repo-root-relative paths in backticks; `atomic signals linkify` renders them to file-relative markdown links.
- Never modify files outside the active wiki root, `.claude/rules/wiki/` (per-domain pointer cards), an ignore file's rules/wiki negation append, or the single `@-ref` target file for wiring.
- Errors quoted exact. No paraphrasing.
- Never block a commit — if the scan fails, log and continue.

</constraints>

MIT license, from damusix/atomic-claude at commit 82246abae8b0.

Security

Scanned Oct 21, 2026 at commit 82246abae8b0, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.