Understand-Anything

Merge pull request #364 from smjeong84/feat/add-kiro-platform-support

feat: add Kiro CLI/IDE platform support

Yuxiang Lin · 2026-06-16 15:51:27 +08:00

ba9ba1f73c

docs(readme): add Kiro platform support to translated READMEs

Mirror the English README's Kiro additions across all 7 translations
(es-ES, ja-JP, ko-KR, ru-RU, tr-TR, zh-CN, zh-TW): the one-line install
heading, supported <platform> values, a dedicated Kiro CLI / IDE
section, and the Platform Compatibility table row.

Lum1104 · 2026-06-16 15:50:37 +08:00

bfb51a5ee0

fix(install): address PR #364 review feedback for Kiro support

Addresses the maintainer (@Lum1104) change requests and the Codex
review on PR #364.

install.sh
- Build the Kiro agent's "resources" list dynamically by iterating over
  understand-anything-plugin/agents/*.md instead of hard-coding each path
  (review: "do not hard code the agents, instead use loop of the repo
  dir"). Deterministic order via LC_ALL=C sort; pure bash, no jq
  dependency. This also fixes pre-existing drift: the hard-coded list had
  7 entries and was missing article-analyzer.md and
  knowledge-graph-guide.md, while 9 agent files actually exist.
- Drop the unsupported "Kiro IDE auto-discovers .kiro-plugin/plugin.json"
  install tip; keep the usage hint.

install.ps1 (Windows)
- Add the `kiro` platform entry (~/.kiro/skills, per-skill) so
  `install.ps1 kiro` no longer fails with "Unknown platform: kiro".
- Generate ~/.kiro/agents/understand.json in Cmd-Install using the same
  dynamic agent discovery; emit forward-slashed file:// URIs and write
  UTF-8 without a BOM via [System.IO.File]::WriteAllText.
- Remove the agent JSON in Cmd-Uninstall.

README.md
- Point the Kiro install command at the canonical Egonex-AI repo instead
  of Lum1104 (Codex P2: a lagging fork would error "Unknown platform:
  kiro" before cloning the canonical repo).
- Replace the unverified ".kiro-plugin auto-discovery" claim with the
  actual behavior (skills symlinked into ~/.kiro/skills, agent written to
  ~/.kiro/agents/understand.json).

Remove .kiro-plugin/plugin.json
- Kiro's documented discovery locations are ~/.kiro/agents, .kiro/skills
  and .kiro/prompts only; .kiro-plugin/plugin.json is never read, so the
  file and the claims that referenced it are removed (maintainer: "use
  install.sh only is fine").

Verification
- install.sh: `bash -n` clean; executed the real agent-JSON generation
  block -> valid JSON with 9 resources; `kiro-cli agent validate` exit 0.
- install.ps1: parsed with 0 syntax errors (PowerShell 7.6.2 AST parser);
  ConvertTo-FileUri yields file:///C:/... for Windows paths; the real
  Cmd-Install "kiro" path runs without error and produces JSON that
  passes `kiro-cli agent validate` (exit 0).

smjeong84 · 2026-06-16 14:18:56 +09:00

af435ed251

Merge pull request #435 from thejesh23/feat/dart-language-support

feat(core): add Dart language support via workspace-vendored WASM

Yuxiang Lin · 2026-06-16 11:06:53 +08:00

6a11656185

fix(core): DartExtractor — call graph coverage for codex P2 findings

Two gaps in the call-graph walker, both flagged by codex on #435:

1. `const Foo(...)` / `new Foo(...)` constructor calls were silently
   dropped. The grammar emits these as `const_object_expression` /
   `new_expression` containing `arguments` directly — they bypass the
   `selector > argument_part` shape the walker relied on. Added a
   dedicated branch that records the inner `type_identifier` as the
   callee. Critical for Flutter widget trees where
   `runApp(const MyApp())` would otherwise lose the MyApp construction
   edge.

2. When a getter / setter / constructor / factory_constructor has a
   body, its `method_signature` wraps `getter_signature` /
   `setter_signature` / `constructor_signature` /
   `factory_constructor_signature` instead of `function_signature`. The
   walker only looked for `function_signature`, so `pendingName`
   stayed null and the sibling `function_body` was walked with an
   empty stack — calls inside ctor/factory/getter/setter bodies were
   silently dropped even though those members were already extracted
   as functions. Now dispatch across all five signature variants,
   using `constructorName` for the (factory) constructor pair to
   match what `collectClassBody` pushes.

Tests: 41 → 47 dart cases (+6); full core 733 → 739; no regressions.

thejesh · 2026-06-15 02:50:06 -07:00

a555f4dd2a

chore: sync root pnpm-lock.yaml with new workspace dep

CI runs `pnpm install` from the repo root using the root lockfile with
the default frozen-lockfile behaviour. The previous commits ran install
only inside understand-anything-plugin/ so the new
@understand-anything/tree-sitter-dart-wasm workspace dependency was
recorded in understand-anything-plugin/pnpm-lock.yaml but missed at
the repo root — CI would have stopped at install.

Flagged by @chatgpt-codex-connector on #435.

thejesh · 2026-06-15 02:49:55 -07:00

f2d6b997c3

Merge branch 'main' into feat/add-kiro-platform-support

정수민/아이엔소프트 · 2026-06-15 11:34:39 +09:00

ede10b9f12

feat(core): DartExtractor — broaden coverage per review (#436 )

Incorporates stronger pieces from the prior Dart attempts (#348, #415)
that @Lum1104 called out:

- `extractParams` now walks `optional_formal_parameters` (covers both
  optional positional `[...]` AND named `{...}` parameters — the Dart
  grammar uses one wrapper for both).
- New `extractParamName` helper extracts the user-visible field name
  from `this.field` and `super.field` initializer parameters by
  unwrapping `constructor_param` / `super_formal_parameter`.
- `collectClassBody` now routes `getter_signature` and `setter_signature`
  in both shapes:
    - concrete: `method_signature > getter_signature` + sibling function_body
    - abstract: `declaration > getter_signature`
  Setters use the same path. The previous limitation assertion
  (`methods).not.toContain("value")`) flipped to a positive
  `.toContain("value")`.
- Added import/export edge-case tests: `dart:` SDK URIs, multi-import
  declaration-order preservation, and `export ... show` clauses.
- Added a comma-list field test (`int a, b, c;`).

Underscore-prefix visibility carries through naturally to all new code
paths via the existing `isExported` gate inside `pushMethod`; explicit
test added for an underscore-prefixed getter.

Test counts: 28 → 41 dart cases; full core suite 720 → 733; no
regressions.

thejesh · 2026-06-13 07:49:48 -07:00

68777feb1d

chore: trim process docs from docs/superpowers/

Per maintainer feedback on #436 — these are personal brainstorm/plan
artifacts produced via the superpowers skill flow, not repo
documentation. The BUILD.md provenance note in
packages/tree-sitter-dart-wasm/ stays since that's repo-level docs
about the vendored wasm.

thejesh · 2026-06-13 07:49:34 -07:00

e4301aea0c

chore: bump version 2.7.7 → 2.8.0 for Dart language support

thejesh · 2026-06-13 05:57:24 -07:00

6be6ad057c

feat(core): DartExtractor — call graph extraction

Implements extractCallGraph with a sibling-aware walk that pairs each
function_signature with its subsequent function_body sibling (Dart's
AST differs from Kotlin's: signature and body are siblings, not
parent/child). Detects call sites via selector nodes containing
argument_part; uses startIndex for sibling lookup (web-tree-sitter
returns new wrapper objects per child() call, making === unreliable).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

thejesh · 2026-06-13 05:41:43 -07:00

a1ee028c35

test(core): DartExtractor — visibility rule (underscore prefix)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

thejesh · 2026-06-13 05:36:23 -07:00

23d6b1a39c

feat(core): DartExtractor — import directives (package/relative/show/as) + export directives

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

thejesh · 2026-06-13 05:35:00 -07:00

798c1747b9

feat(core): DartExtractor — enum declarations

Adds enum_declaration handling to DartExtractor: enum constants are surfaced
as properties[] so the structural graph captures Color.red / Color.green etc.
Implements Task 9 of the Dart language support plan (TDD, 16/16 dart tests
pass, full suite 708/708).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

thejesh · 2026-06-13 05:26:12 -07:00

fd1d1c6450

feat(core): DartExtractor — extension declarations (named + anonymous)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

thejesh · 2026-06-13 05:24:30 -07:00

306ee2c070

feat(core): DartExtractor — mixin declarations

Add mixin_declaration handling to extractStructure, folding mixins into
classes[] (same convention as class_definition). The `on` constraint
sibling is intentionally ignored for graph purposes.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

thejesh · 2026-06-13 05:19:11 -07:00

05ce514db5

feat(core): DartExtractor — constructor naming (default/named/factory)

Add constructorName() helper and extend collectClassBody() to surface
unnamed constructors as "ClassName", named constructors as "Class.named",
and factory named constructors as "Class.named" in methods[]/functions[].
Probe confirmed plan's AST shapes match exactly; extractReturnType returns
undefined for all constructor forms (factory keyword is an unnamed node).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

thejesh · 2026-06-13 05:12:41 -07:00

893208efb3

feat(core): DartExtractor — class extraction with fields + methods

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

thejesh · 2026-06-13 05:08:47 -07:00

f4fc802743

feat(core): DartExtractor — top-level function extraction

Add TDD tests and implement extractTopLevelFunction with helpers for
extracting function name, params, and return type (including generics
where the grammar emits type_identifier + type_arguments as siblings).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

thejesh · 2026-06-13 04:58:56 -07:00

136f85c1c8

feat(core): scaffold DartExtractor + register in builtinExtractors

Empty extractor that satisfies the LanguageExtractor interface so the
plugin pipeline can load it. Real extraction logic lands in subsequent
TDD commits.

thejesh · 2026-06-13 04:50:00 -07:00

072bab798c

feat(core): register dart LanguageConfig

Adds the Dart language config and wires it into builtinLanguageConfigs
so .dart files are recognized by the language registry. References the
vendored @understand-anything/tree-sitter-dart-wasm package for grammar
loading.

No extractor yet — structural extraction lands in the next commit.

thejesh · 2026-06-13 04:46:13 -07:00

62932684c6

feat(tree-sitter-dart-wasm): vendor freshly-built dart WASM grammar

The upstream tree-sitter-dart@1.0.0 ships a pre-`dylink.0` wasm that
fails to load in web-tree-sitter@0.26.x. The grammar source itself is
sound — rebuilding with the current tree-sitter-cli + wasi-sdk produces
a working dylink.0 wasm. Vendor that artifact as a workspace-internal
package so @understand-anything/core can depend on it via workspace:*.

BUILD.md documents the provenance and rebuild instructions.

thejesh · 2026-06-13 04:42:58 -07:00

3587ffa7a3

docs: implementation plan for Dart language support

Thirteen-task TDD plan walking from vendoring the workspace wasm package
through scaffolding the extractor and adding extraction logic in
test-first slices: functions, classes, constructors, mixins, extensions,
enums, imports, exports, visibility, and call graph.

Every code block reflects AST shapes confirmed via a live probe against
a freshly-built tree-sitter-dart wasm in the project's own
web-tree-sitter at 0.26.x. No placeholder code, no "fill in later"
references.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

thejesh · 2026-06-13 04:35:07 -07:00

5459ac0e6d

docs: revise Dart spec for workspace-vendored wasm

Live verification during planning surfaced two facts that change the
shipping strategy:

1. tree-sitter-dart@1.0.0's prebuilt wasm uses the pre-`dylink.0` format
   and fails to load in web-tree-sitter@0.26.x (the version this project
   uses). Verified by directly loading the upstream wasm and catching
   the failure in getDylinkMetadata.

2. The grammar source itself is sound — rebuilding with the current
   tree-sitter-cli@0.26.x + wasi-sdk-29 toolchain produces a working
   dylink.0-format wasm that parses every construct the extractor needs.

Revised packaging: ship the freshly-built wasm as a workspace-internal
package (@understand-anything/tree-sitter-dart-wasm) rather than
depending on the broken upstream npm artifact. No loader changes
required; existing TreeSitterPlugin resolves it the same way it
resolves other tree-sitter packages.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

thejesh · 2026-06-13 04:30:09 -07:00

c447b69faf

docs: design spec for Dart language support

Adds the brainstormed design for landing deep Dart support at parity with
the recent Kotlin add (PR #347): LanguageConfig + tree-sitter WASM grammar
(tree-sitter-dart@1.0.0, verified ships a prebuilt .wasm in its tarball) +
DartExtractor + ~22 vitest cases. Six file changes, no edits to shared
schemas/registries.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

thejesh · 2026-06-13 04:19:22 -07:00

2bb5233517

Merge pull request #419 from chengyongru/feat/nanobot-support

feat(install): add Nanobot platform support

Yuxiang Lin · 2026-06-11 16:28:17 +08:00

09ede1917f

remove homepage starter community copy

chienvon · 2026-06-09 14:42:00 -07:00

fb1356ae32

sync egonex organization metadata

chienvon · 2026-06-09 14:26:48 -07:00

7254852f4a

feat(install): add Nanobot platform support

chengyongru · 2026-06-09 16:52:35 +08:00

8de0b3b11d

Merge pull request #347 from tirth8205/feat/kotlin-extractor

feat(core): add Kotlin structural analysis via tree-sitter

Yuxiang Lin · 2026-06-09 13:25:10 +08:00

ef7adac58e

Merge pull request #359 from tirth8205/fix/import-resolver-nodenext-rewrite

fix(extract-import-map): apply NodeNext .js→.ts rewrite (#294)

Yuxiang Lin · 2026-06-09 13:23:21 +08:00

13a39c01cb

Merge pull request #387 from tirth8205/fix/phase7-cleanup-mv-trash

fix(skill): use mv-to-trash + delayed purge for Phase 7 cleanup (#301)

ZebangCheng · 2026-06-06 18:47:00 +08:00

5c1e35f90b

Merge pull request #346 from tirth8205/perf/understand-pipeline

perf(understand): parallelise file I/O in compute-batches + extract-import-map (#76)

ZebangCheng · 2026-06-06 16:25:49 +08:00

3281fd15e0

fix(skill): use mv-to-trash + delayed purge for Phase 7 cleanup (#301 )

Phase 7's `rm -rf` of the just-created `intermediate/` and `tmp/` dirs
trips destructive-action gates on hardened hosts (e.g. freshness-window
checks that flag deleting paths created moments earlier). Move them into
a timestamped `.trash-<epoch>/` instead; Phase 0 reclaims the space once
the trash is older than 7 days, well past any freshness window. Behavior
on normal hosts is unchanged — disk usage is identical after the next
run's purge.

Closes #301

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Tirth Kanani · 2026-06-05 16:56:42 +01:00

b3da919223

fix(extract-import-map): preserve deterministic stderr order across concurrent loaders

Addresses the regression flagged by ZebangCheng on #346: under the
parallelised `buildResolutionContext`, `loadTsConfigs` /
`loadGoModules` / `loadPhpAutoloads` ran concurrently but each wrote
warnings to stderr inline as it iterated read results, so a fixture
with both a malformed `tsconfig.json` and a malformed `composer.json`
could emit `composer, tsconfig` instead of the pre-PR `tsconfig,
composer` depending on I/O timing.

Each loader now buffers its warnings into a returned array and the
caller drains them in canonical order (tsconfig → go → php) after
`Promise.all`, restoring byte-identical stderr output. Added a
regression test that fixtures both malformed configs and asserts the
tsconfig warning precedes the composer warning in stderr.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Tirth Kanani · 2026-06-05 16:19:31 +01:00

1f8d165f86

Merge pull request #378 from BozhengLong/feat/understand-language-auto-detection

feat(understand): auto-detect conversation language on first run

Yuxiang Lin · 2026-06-04 13:46:14 +08:00

7a3b7511b2

docs: design + implementation plan for language auto-detection

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Bozheng Long · 2026-06-03 21:19:52 +08:00

55d0ab2336

feat(understand): auto-detect conversation language on first run

When /understand runs with no --language flag and no stored outputLanguage,
step 3.6 now infers the conversation language and — only when it is non-English
— confirms once before generating, then persists the choice to config.json.
English conversations keep the exact same silent `en` path; --language flag and
stored config still take priority. README documents the behavior; version
bumped 2.7.5 -> 2.7.6 across all five manifests (user-visible behavior change).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Bozheng Long · 2026-06-03 21:19:52 +08:00

92e76190aa

Merge pull request #350 from tirth8205/chore/repo-hygiene

chore(repo): community templates, CoC, SECURITY, package metadata, CI on main (#248, #249, #251, #252).

ZebangCheng · 2026-06-02 17:49:02 +08:00

025b884935

Merge pull request #343 from xiazl1993/chore/cleanup-gitignore-patterns

chore: clean up duplicate gitignore patterns

ZebangCheng · 2026-06-02 17:47:24 +08:00

f65013e689

feat: add Kiro CLI/IDE platform support

- Add kiro to install.sh platforms_table (per-skill symlinks to ~/.kiro/skills/)
- Generate ~/.kiro/agents/understand.json on install for full pipeline support
- Clean up agent JSON on uninstall
- Add .kiro-plugin/plugin.json for IDE auto-discovery
- Update README with Kiro in platform table, one-line install list, and dedicated section

smjeong84 · 2026-06-02 13:46:55 +09:00

aa3a220e75

Merge pull request #332 from ZebangCheng/fix/phase7-preserve-scan-result

fix(skill): preserve scan-result.json across Phase 7 cleanup for incremental runs (#293)

Yuxiang Lin · 2026-06-01 17:53:12 +08:00

e5dded6215

Merge branch 'main' into fix/import-resolver-nodenext-rewrite

Resolve conflict in tests/skill/understand/test_extract_import_map.test.mjs
by keeping both new test groups — they cover independent fixes that should
coexist:
  - upstream #214: tsconfig path-alias targets with leading "./"
  - this PR  #294: NodeNext .js → .ts rewrite for ESM TypeScript imports

The extract-import-map.mjs script auto-merged cleanly; both fixes are
already present in the merged source.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Tirth Kanani · 2026-06-01 10:25:37 +01:00

143b4e492f

fix(extract-import-map): apply NodeNext .js→.ts rewrite (#294 )

Fixes the silent near-edgeless-graph regression on any modern ESM
TypeScript project. Reported in #294 with full repro + root-cause
analysis.

### Why this matters

Under `moduleResolution: NodeNext` (or `Node16` / `Bundler` with
explicit extensions — the default for new TS-ESM projects since 2023),
TypeScript does NOT rewrite import specifiers during compilation:

  // src/index.ts — real, idiomatic NodeNext source
  import { x } from './config.js';   // on disk: config.ts

Before this fix, `probeWithExtensions` only tried APPENDING extensions
to the import specifier:

  './config.js' → not in fileSet
  './config.js.ts', './config.js.tsx', './config.js.js', ... → all miss
  → returns null → edge dropped at merge as dangling

Net result on the reporter's repro: a knowledge graph with hundreds of
file nodes and almost no `imports` edges between them — silently
removing exactly the dependency structure the graph is meant to show.

### Fix

New `NODENEXT_REWRITES` table maps each compiled-output extension to
the TypeScript source extensions that could have produced it:

  .js   → [.ts, .tsx, .js, .jsx]
  .jsx  → [.tsx, .jsx]
  .mjs  → [.mts, .mjs, .ts]
  .cjs  → [.cts, .cjs, .ts]

`probeWithExtensions` now applies the rewrite when the import already
ends with one of these extensions and no such file exists on disk. The
rewrite runs BEFORE the legacy append-extensions loop — otherwise
`./foo.js` would generate the nonsense candidate `foo.js.ts` and the
append loop would never reach the actual `foo.ts`.

### Disambiguation

If both `config.ts` and `config.js` exist on disk (rare, but possible
during a partial migration), `import './config.js'` still resolves to
the .js — that's an exact-disk match and what NodeNext compilation
actually does. The rewrite only kicks in when the .js doesn't exist.

### Tests

6 new tests in `test_extract_import_map.test.mjs`:
- The main #294 case (`.js → .ts`)
- `.jsx → .tsx` and `.mjs → .mts` rewrites
- Disambiguation when both `.ts` and `.js` exist on disk
- Pure-JS projects still work (real `.js → .js` imports)
- Historical no-extension probes unaffected
- Missing files still return null (rewrite can't invent targets)

Total: 202 tests passing (was 196).

Closes #294

Tirth Kanani · 2026-05-31 22:31:23 +01:00

a6c653e36b

chore(repo): add issue/PR templates, SECURITY.md, CoC, package metadata; widen CI triggers

Closes a cluster of community-profile gaps (#248, #249, #251, #252) in one
PR rather than four micro-PRs that all touch the same surface area.

### Templates (#251, #252)

- .github/ISSUE_TEMPLATE/bug_report.yml — required fields for repro
  (plugin version, platform, OS, project language, file count); the four
  pieces of context that are missing from ~every current bug report.
- .github/ISSUE_TEMPLATE/feature_request.yml — leads with the *problem*
  rather than the proposed solution, which keeps maintainer review focused
  on whether to solve, not just how.
- .github/ISSUE_TEMPLATE/question.yml — separate from bug to keep the
  bug queue triagable.
- .github/ISSUE_TEMPLATE/config.yml — disables blank issues and routes
  general discussion to README + Discussions.
- .github/PULL_REQUEST_TEMPLATE.md — includes the version-bump checklist
  that CLAUDE.md says must stay in sync across 5 manifests; otherwise
  every contributor learns this rule by getting their PR bounced.

### Community files

- CODE_OF_CONDUCT.md — short, project-specific document that names the
  expectations and reporting path. Not a verbatim Contributor Covenant
  to keep it readable.
- SECURITY.md — describes the project's local-only threat model
  explicitly so reporters know what's in / out of scope before they
  spend time on a writeup. Points at GitHub private vulnerability
  reporting as the primary channel.

### CI (#249)

- ci.yml now also runs on pushes to main, not only PRs. Without this,
  a direct push to main (which happens when maintainers merge a PR
  branch locally) doesn't trigger CI, so a regression can land green-
  looking and stay broken for days.
- Added a concurrency group that cancels stale runs for the same ref.
  Saves runner minutes and keeps the per-ref status meaningful.
- Used `github.ref` (a controlled value), not user-controlled input,
  so no script-injection surface.

### package.json (#248)

- Added description, license, repository, bugs, homepage, keywords —
  the standard set for npm package discoverability and so GitHub's
  community-profile check shows the project at 100%.

Tirth Kanani · 2026-05-31 21:29:13 +01:00

aef940fcde

feat(core): add Kotlin structural analysis via tree-sitter

Wires Kotlin into the existing tree-sitter pipeline so .kt and .kts
files now produce functions, classes, data classes, sealed classes,
interfaces, objects, imports, exports, and call-graph edges — matching
the behavior of the other language extractors.

## Why @tree-sitter-grammars/tree-sitter-kotlin

The standard `tree-sitter-kotlin` (v0.3.8) ships only native bindings.
The new `@tree-sitter-grammars/tree-sitter-kotlin@1.1.0` ships a
prebuilt `.wasm` (loads cleanly with `web-tree-sitter@^0.26.6`,
nodeTypeCount=289, parses class_declaration / function_declaration as
expected). Same shape that PR1 used for Swift, just a different
publisher because the repomix WASM bundle does not include Kotlin.

`@tree-sitter-grammars` is the official tree-sitter org's GitHub
account, so this is the canonical upstream WASM source for Kotlin.

## Notes for reviewers

- `kotlinConfig` already existed as a stub (no `treeSitter` field), so
  Android / JVM / Gradle codebases currently produce no structural
  edges between `.kt` files. This PR adds the `treeSitter` field; the
  existing plugin loader picks it up unchanged.
- **Visibility rule differs from Swift**: Kotlin's default visibility
  is `public`, so the extractor treats *every* declaration with no
  modifier as exported. Only an explicit `private` opts out. `internal`
  and `protected` remain exported in the project-graph sense because
  they are still resolvable from other files (within the module / via
  inheritance).
- `class_declaration` in tree-sitter-kotlin is overloaded for class,
  data class, sealed class, and interface (distinguished by the keyword
  child and `modifiers > class_modifier`). The extractor handles all
  four uniformly.
- `object_declaration` is a separate node type (Kotlin singletons) —
  treated as a class-like entry with its own `name` and members.
- Primary-constructor parameters marked `val` / `var` are surfaced as
  class properties; plain `parameter`s without `val/var` are
  constructor-only and are NOT counted as properties (matching Kotlin
  semantics).
- Import handling distinguishes the three forms: plain dotted
  (`import a.b.C`), wildcard (`import a.b.*` → specifier `"*"`), and
  aliased (`import a.b.C as Foo` → specifier `"Foo"`).

## Verification

- `pnpm lint` clean
- `pnpm --filter @understand-anything/core build` clean
- `pnpm --filter @understand-anything/skill build` clean
- `pnpm --filter @understand-anything/core test`: **692/692** (+22 new
  Kotlin tests, matching the bar set by go-extractor.test.ts /
  swift-extractor.test.ts)
- `pnpm test`: 196/196 (no regressions)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Tirth Kanani · 2026-05-31 20:42:12 +01:00

235f2fafc8

perf(understand): parallelise file I/O in compute-batches + extract-import-map (#76 )

The /understand pipeline reads every code file twice during analysis:
once in compute-batches (`extractExports` for the cross-batch neighbour
map) and once again in extract-import-map (per-language config loaders).
Both sites used sequential `readFileSync` loops, so on the iOS repo in
issue #226 (~15k files) the disk-read time was effectively serialised
behind a single libuv thread while the rest of the pool sat idle.

## Changes

- `extractExports` now batches files into `IO_PARALLELISM = 64` slices
  and issues all `readFile` calls in each slice through `Promise.all`,
  letting libuv's worker-thread pool overlap disk reads. The
  tree-sitter parse stays on the main thread because `web-tree-sitter`
  is single-threaded WASM — pipelining the I/O while parses run is
  where the wall-time savings come from.
- `loadTsConfigs`, `loadGoModules`, `loadPhpAutoloads` and
  `buildResolutionContext` switch to async / `Promise.all` for the
  same reason. `buildResolutionContext` also runs the three loader
  passes concurrently (`Promise.all([...])`) since they're independent.
- A small `readFilesParallel(paths)` helper is added at the top of
  `extract-import-map.mjs` so the three loaders share the same
  error-preserving shape.

## Why behavior stays identical

- Each loader collects its candidate paths in `files[]` order *before*
  issuing reads, then iterates `reads` in the same order to emit
  warnings + populate output maps. So stderr order and the final map
  contents are byte-identical to the previous sequential loops.
- `extractExports` collects per-file errors in-place in the
  `Promise.all` callbacks and emits warnings during the post-read
  serial loop, again in chunk order — so warning text and order match
  the previous implementation.
- Tree-sitter parsing is unchanged: parses still run serially on the
  main thread, just with reads pipelined alongside.

## What's NOT in this PR

- `buildFingerprintStore` and `analyzeChanges` in `core/fingerprint.ts`
  have the same sequential pattern. They're left alone here because
  they're part of the public `@understand-anything/core` API; making
  them async would be a breaking change worth its own discussion.
  Internal-only `.mjs` scripts are safe to refactor without API churn.
- No change to scan-project: most of its sync I/O is `statSync`
  (metadata, not content) plus a handful of small `.gitignore` /
  `.understandignore` reads. The parallelism win is marginal there.

## Verification

- `pnpm lint` clean
- `pnpm --filter @understand-anything/core build` clean
- `pnpm --filter @understand-anything/skill build` clean
- `pnpm test`: 196/196 — including
  `test_compute_batches.test.mjs` (19 tests) and
  `test_extract_import_map.test.mjs` (40 tests), which exercise both
  changed pipelines end-to-end with fixture projects. No output
  diff vs main.

Refs #76

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Tirth Kanani · 2026-05-31 20:25:39 +01:00

eea73b656d

chore: clean up duplicate gitignore patterns

summer · 2026-05-31 23:14:38 +08:00

d2d4d23156

fix(skill): preserve scan-result.json across Phase 7 cleanup for incremental runs (#293 )

Zebang Cheng · 2026-05-29 15:33:31 +00:00

928b997c57

Merge pull request #235 from ZebangCheng/feat/add-trae-platform

feat(install): add Trae (ByteDance AI IDE) platform support (#229)

ZebangCheng · 2026-05-26 13:09:57 +08:00

26edf61856

596 Commits