feature-wiki

feature-wiki

Turn any codebase's git history into a feature wiki, enriched with your Jira / Linear / GitHub tickets and published to Confluence, Notion, a GitHub wiki, or a local HTML site.

A Claude Code plugin that reconstructs the features an author shipped from git history, enriches them with project-management ticket context (Jira, Linear, GitHub, Shortcut, Asana, whatever MCP is connected), and publishes the result to Confluence, Linear, Notion, a GitHub wiki, or a self-contained local HTML wiki.

It turns the one-off job of "document what this repo does" into a repeatable pipeline you can re-run as the code changes.

Why / use cases

The story of why and how a feature was built already lives in your commits and tickets. It just is not written down anywhere readable. feature-wiki assembles it into clear, onboarding-grade docs and keeps them current as the code evolves. It helps whether you work solo or on a team:

• Solo builders. Collate what each of your side projects actually contains and why you built it the way you did, so coming back to one after months is painless.
• Teams. Give new starters accurate onboarding docs instead of weeks of reverse-engineering, and keep those docs in sync as the code changes.
• Shared docs spaces. When publishing to a shared Confluence, Notion, or Linear space, it first searches the space for an existing page for each ticket or epic and updates that page rather than creating a new one. Several teammates can run it against the same project and everyone lands on one page per feature instead of spawning copies.

Requirements

• Required: git and python3 (standard library only, no packages to install). This is enough to produce the local HTML wiki.
• Optional but recommended: an MCP connection for the parts that need external data:
  • a project-management MCP (Jira, Linear, GitHub, Shortcut, or Asana) for ticket enrichment,
  • a docs MCP (Confluence, Notion, or Linear) or the gh CLI for publishing to a shared space.

The plugin does not ship or require any MCP. It uses whatever you have connected and degrades to a local wiki when nothing is. See Connecting your tools.

Install

This repo is a Claude Code plugin marketplace. From GitHub:

/plugin marketplace add zaakirio/feature-wiki
/plugin install feature-wiki

Or from a local checkout:

/plugin marketplace add /path/to/feature-wiki
/plugin install feature-wiki

(Or copy skills/building-feature-wikis into a .claude/skills/ directory to use the skill alone, with no plugin install.)

Use

/feature-wiki-init                 # detect MCPs, set scope, write .featurewiki/config.json
/feature-wiki-build --since 2025-11-01   # mine, enrich, write docs, render local HTML wiki
/feature-wiki-publish confluence   # publish or update pages in a shared space

Or just ask in natural language ("build a wiki of the features I shipped in this repo") and the skill self-triggers.

How it works

Editable source: assets/how-it-works.excalidraw — open it at excalidraw.com (File > Open, or drag it onto the canvas). The same pipeline, as text:

discover repo + scope  ->  mine git history into features  ->  enrich from the PM tool
        ->  one subagent per feature reads code + writes a doc  ->  check what changed
        ->  create or update each feature on the target(s)

Stages are deterministic where it matters (git mining, bookkeeping, and HTML bundling are scripts) and high-freedom where judgement helps (grouping review, code reconstruction, provider binding).

Connecting your tools (MCP)

feature-wiki adapts to whatever MCP servers you have connected in Claude Code. Connect the ones you want, then run /feature-wiki-init to bind them.

What each connection unlocks:

• Read (Jira, Linear, GitHub, Shortcut, Asana): pulls real ticket titles, descriptions, status, and epic links into each doc. Without it, docs still link the ticket keys found in your commits.
• Write (Confluence, Notion, Linear, or gh for a GitHub wiki): publishes and updates pages in a shared space. Without it, output is the local HTML wiki.

How to connect, in short:

1. Add the server, e.g. claude mcp add --transport sse linear https://mcp.linear.app/sse (use the current URL from the provider's MCP docs; some servers use --transport http).
2. Run /mcp to authenticate and to verify what is connected.