# aspens — Scoped Skills from Your Import Graph

> aspens splits bloated CLAUDE.md into ~35-line scoped skills from your import graph; verified 81★ with `doc init/impact/sync` + post-commit auto-sync.

## Install

Save the content below to `.claude/skills/` or append to your `CLAUDE.md`:

## Quick Use

```bash
npm install -g aspens
cd /path/to/your/repo
aspens doc init --recommended
aspens doc impact
# Optional: keep docs fresh after each commit
aspens doc sync --install-hook
```

## Intro

aspens splits bloated CLAUDE.md into ~35-line scoped skills from your import graph; verified 81★ with `doc init/impact/sync` + post-commit auto-sync.

**Best for:** Teams whose single CLAUDE.md got too long and stale as the codebase evolved

**Works with:** Claude Code and Codex (targets: `claude`, `codex`, or `all`), git repos with stable import graph signals

**Setup time:** 8-15 minutes

### Key facts (verified)

- GitHub: 81 stars · 3 forks · pushed 2026-05-13.
- License: MIT · owner avatar + repo URL verified via GitHub API.
- README-backed entrypoint: `npm install -g aspens`.

## Main

- Replace the monolith: generate multiple small skill files so the agent reads the right context only when it touches that domain.

- Use `doc impact` as a freshness/coverage gate before trusting your context in CI or during high-risk refactors.

- Keep drift low by running `doc sync` after changes (or install the post-commit hook) so skills match current imports and domains.

### Source-backed notes

- README describes skills as ~35-line markdown files that activate when the agent edits matching domains.
- README documents `aspens doc init --recommended` and `aspens doc impact` as the first verification loop.
- README includes `aspens doc sync` and an `--install-hook` option for post-commit auto-sync.

### FAQ

- **Do I need to install it globally?**: No — README shows `npx aspens doc init --recommended` as a no-install path.
- **What triggers a skill?**: README explains skills activate when the agent touches matching domains/files, instead of loading one huge CLAUDE.md.
- **How do I keep it up to date?**: Run `aspens doc sync` after changes or install the post-commit hook via `--install-hook`.

## Source & Thanks

> Source: https://github.com/aspenkit/aspens
> License: MIT
> GitHub stars: 81 · forks: 3

---

<!-- ZH -->

## Quick Use

```bash
npm install -g aspens
cd /path/to/your/repo
aspens doc init --recommended
aspens doc impact
# Optional: keep docs fresh after each commit
aspens doc sync --install-hook
```

## Intro

aspens 把臃肿的 CLAUDE.md 拆成约 35 行的 scoped skills，并基于 import graph 自动生成/同步；已验证 81★，核心命令为 `doc init/impact/sync`。

**Best for:** 单一 CLAUDE.md 越写越长、随代码演进变得过时的团队

**Works with:** Claude Code 与 Codex（支持 `claude`/`codex`/`all` 输出目标），以及可分析 import graph 的 git 仓库

**Setup time:** 8-15 minutes

### Key facts (verified)

- GitHub：81 stars · 3 forks；最近更新 2026-05-13。
- 许可证：MIT；作者头像与仓库链接均已通过 GitHub API 复核。
- README 中可对照的入口命令：`npm install -g aspens`。

## Main

- 用多个小 skill 替代单个大文件：让 agent 只在触达对应领域时加载所需上下文。

- 把 `doc impact` 当作“上下文新鲜度/覆盖率”的门禁，在 CI 或大改动前先验证再依赖。

- 用 `doc sync`（或安装 post-commit hook）降低漂移，让 skills 与当前代码/依赖关系保持一致。

### Source-backed notes

- README 将 skills 描述为约 35 行的 markdown 文件，并在编辑对应领域文件时触发加载。
- README 给出 `aspens doc init --recommended` 与 `aspens doc impact` 作为首要验证闭环。
- README 提供 `aspens doc sync`，并支持 `--install-hook` 安装 post-commit 自动同步。

### FAQ

- **必须全局安装吗？**：不必。README 也提供 `npx aspens doc init --recommended` 的免安装用法。
- **skill 什么时候触发？**：README 说明：当 agent 触达匹配的领域/文件时再加载对应 skill，而不是一次性读完整 CLAUDE.md。
- **如何保持同步？**：改动后运行 `aspens doc sync`，或用 `--install-hook` 安装 post-commit 自动同步。

## Source & Thanks

> Source: https://github.com/aspenkit/aspens
> License: MIT
> GitHub stars: 81 · forks: 3


---
Source: https://tokrepo.com/en/workflows/aspens-scoped-skills-from-your-import-graph
Author: Script Depot