claude

ccinformer

A side pane in five areas: other sessions, live git and CI with the repo's rule checks and budgets, workflow runs, stats and plan checkpoints, and a debug log of tools, requests and context growth; approval gates that ask before the writes a pack names; plus planning skills whose plans the pane follows, a docs-audit skill, and a skill that writes your packs

2 on GitHubby EsonOscarv0.44.0MITupdated 3 days ago
/

Plugin ccinformer from marketplace ccinformer in EsonOscar/CCInformer. Commands read from the repo's manifest — 2 days ago.

What it installs

Skills (6)

  • write-builtin

    Write a new built-in CCInformer pack for a stack (hooks/packs/<id>.ts with its detect rules and its test) while working on the mod in a CCInformer clone. Generic values only, never a project's; asks once before writing, naming every path. Use when the maintainer asks for a new built-in pack, or runs

  • audit-docs

    Multi-agent docs audit in plan mode, then the fixes, for any kind of docs in any repo, git-tracked or local. Setup finds the docs, their kinds (current, instructions, ADRs and other records, changelogs, archives, history, generated, translations, copies, parsed, indexes, third-party, code comments)

  • plan-feature-small

    Fast planning for smaller tasks or a tighter token budget, then the build. In plan mode you scout the code yourself (at most two Explore helpers for ground too big to read), write down the requirements and draft the plan, then one critic agent (Opus at medium effort by default) reviews it against th

  • plan-feature

    Multi-agent planning in plan mode, then the build. Scope inline (requirements, the project's planning settings, prior findings), run the plan-fanout workflow (read-only scouts, 1 to 3 domain planners, adversarial critics with structured findings), check every finding against the code yourself and fo

  • plan-handoff

    Multi-agent planning for someone who isn't a developer, ending in a handoff doc instead of a build. Same fan-out as plan-feature (read-only scouts, 1 to 3 domain planners, adversarial critics, every finding checked against the code), with the user asked only product decisions in plain words, technic

  • write-pack

    Draft a CCInformer user pack for the repo you're in, from its files and its CI, checked by the mod's own validator, and write it to the person's packs folder once they approve the path. Reads manifests, lint and format configs, git hooks, CI workflows, deploy configs and tests that act as rules; nev

View source on GitHub

Maintain ccinformer?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted