From chronicler
Ambient .tech.md documentation generator with freshness tracking. Auto-generates technical documentation alongside source files and tracks staleness per file. Use when user says /chronicler, wants to set up documentation for a project, check doc freshness, regenerate stale docs, or configure chronicler settings. Supports init, status, regenerate, and configure subcommands.
npx claudepluginhub shihwesley/chronicler --plugin chroniclerThis skill uses the workspace's default tool permissions.
Chronicler generates `.tech.md` files that live alongside your source code in a `.chronicler/` directory. Each doc captures a file's purpose, key components, dependencies, and architectural context in structured frontmatter + markdown. A merkle tree tracks which source files have changed, so you always know which docs are fresh and which need updating.
Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.
Generates Angular code and provides architectural guidance for projects, components, services, reactivity with signals, forms, dependency injection, routing, SSR, ARIA accessibility, animations, Tailwind styling, testing, and CLI tooling.
Executes ctx7 CLI to fetch up-to-date library documentation, manage AI coding skills (install/search/generate/remove/suggest), and configure Context7 MCP. Useful for current API refs, skill handling, or agent setup.
Chronicler generates .tech.md files that live alongside your source code in a .chronicler/ directory. Each doc captures a file's purpose, key components, dependencies, and architectural context in structured frontmatter + markdown. A merkle tree tracks which source files have changed, so you always know which docs are fresh and which need updating.
/chronicler:initFirst-time project setup. Detects the project language, generates chronicler.yaml, builds a merkle tree, then generates .tech.md files for every tracked source file. Also builds .chronicler/INDEX.md with grouped component tables.
/chronicler:init
After init, hooks run automatically:
.tech.md backed by stale source/chronicler:statusShows a freshness report: how many files are fresh, stale, uncovered (source with no docs), or orphaned (docs with no source).
/chronicler:status
/chronicler:regenerateRegenerates .tech.md files whose source has changed since the last scan. Pass a specific file path to regenerate just that one, or run without arguments to regenerate all stale files. Rebuilds INDEX.md afterward.
/chronicler:regenerate
/chronicler:regenerate src/api/auth.ts
/chronicler:configureUpdates chronicler.yaml settings using dot-notation key=value pairs.
/chronicler:configure llm.provider=openai llm.model=gpt-4o
# 1. Set up chronicler in a new project
/chronicler:init
# 2. Work on code for a while...
# (hooks track which files you edit)
# 3. Check what's gone stale
/chronicler:status
# 4. Regenerate stale docs
/chronicler:regenerate
# 5. Tweak settings if needed
/chronicler:configure scan.exclude_patterns=["*.test.ts","dist/**"]
/chronicler:init first. The config file is required for all other subcommands./chronicler:status will flag these. Delete the old .tech.md and run /chronicler:regenerate for the renamed file.scan.exclude_patterns to skip generated or vendored code before running init./chronicler:regenerate <file> to clear it.This skill dispatches to the following command files:
commands/init.md — project setup and initial doc generationcommands/status.md — freshness reportingcommands/regenerate.md — stale doc regenerationcommands/configure.md — config updates