astkit-tooling

Original：🇺🇸 English

Translated

Use when a TypeScript/JavaScript task needs symbol navigation (`nav declarations|definition|references`), structural pattern search (`search`), structural rewrites (`patch`), or reference-based blast-radius estimation (`code-rank`). Prefer for compact, scoped repository analysis and migration work; do not use for runtime-path proofs, correctness guarantees, or replacing compiler/tests.

1installs

Sourceclaudiuceia/astkit

Added on2026-02-08

NPX Install

npx skill4agent add claudiuceia/astkit astkit-tooling

SKILL.md Content

View Translation Comparison →

astkit tooling

Use

astkit

for token-efficient repository exploration and structural edits in TS/JS projects. Keep scope narrow first, expand only when evidence is insufficient.

Quick Start

Confirm tool availability.

```
astkit --help
```
or
```
npx astkit --help
```
or
```
bunx astkit --help
```

Start with one focused operation.

```
astkit nav declarations <file>
```

astkit nav definition <file:line:character>

astkit nav references <file:line:character>

astkit search '<pattern>' <scope> --json

astkit patch --dry-run '<patch-document>' <scope>

astkit code-rank <scope> --limit 25 --json

Expand scope only if needed.

Working Workflow

Map contracts before implementation details.

Use
```
nav declarations
```
and
```
nav definition
```
first.
Treat signatures/docs as intended contracts until contradicted by evidence.

Clarify behavior from usage.

Use
```
nav references
```
to inspect representative callsites.
Prefer usage patterns over deep source reading for initial understanding.

Estimate blast radius before edits.

Use
```
code-rank
```
and references to identify high-impact symbols.
Prefer localized changes when task scope is localized.

Rewrite with structural tools.

Use
```
search
```
to find candidate shapes.
Use
```
patch --dry-run
```
before writing changes.
Use
```
patch --interactive
```
for high-risk or broad rewrites.

Re-check and validate.

Re-run focused
```
search
```
/
```
nav references
```
on touched symbols.
Validate with
```
tsc
```
and relevant tests when available.

Safe Rewrite Workflow

Find candidate sites.

astkit search '<pattern>' <scope> --json

Preview rewrite.

astkit patch --dry-run '<patch-document>' <scope>

Apply rewrite.

```
astkit patch '<patch-document>' <scope>
```
Use
```
--interactive
```
for high-risk or broad edits.

Re-check surfaced contracts.

Re-run focused
```
search
```
queries and
```
nav references
```
on touched symbols.

Validate with compiler and tests.

Run
```
tsc
```
diagnostics.
Run focused tests for touched behavior.

Reporting Contract

When reporting findings, include:

system boundaries and entry points
invariants/contracts with explicit status (
```
observed
```
vs
```
inferred
```
)
definition/reference flow summary
change hotspots/dependency hubs
suggested edits with blast-radius notes
validation status and remaining gaps

Keep output concise and include file paths/spans where possible.

Guardrails

Structural similarity does not imply behavioral equivalence.
Structural rewrites reduce accidental matches but do not guarantee correctness.
Reference ranking approximates impact, not runtime criticality.
No matches do not prove absence of behavior.
Do not use this skill as a substitute for compiler diagnostics or tests.

Common Failure Modes

Too many matches: narrow scope, add delimiters, add regex constraints.
No matches: verify pattern shape, scope, and
```
--no-isomorphisms
```
usage.
Rewrite too broad: switch to
```
--interactive
```
and re-run dry-run first.
Unclear impact: inspect
```
nav references
```
and
```
code-rank
```
before applying.

References

```
./references/cognitive-model.md
```
```
./references/non-goals.md
```