Skip to content

chore(agents): Improve perf-tuning command and exclude worktrees from biome #1284

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yamadashy merged 3 commits into from
Mar 21, 2026
Merged

chore(agents): Improve perf-tuning command and exclude worktrees from biome #1284

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a8dd43b
chore(agents): Improve perf-tuning command for better investigation c…
yamadashy Mar 21, 2026
fda6e73
chore(lint): Exclude .claude/worktrees from biome lint scope
yamadashy Mar 21, 2026
f8c060e
chore(agents): Add startup time reduction to perf-tuning targets
yamadashy Mar 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .agents/commands/code/perf-tuning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
# Goal
Improve performance or memory usage of `src`, `website/server`, and related code (tests, configs, dependencies) without causing regressions.
Improve performance or reduce memory consumption of `src`, `website/server`, and related code (tests, configs, dependencies) without causing regressions.

Think broadly — algorithm changes, architectural restructuring, parallelization, caching strategies, library replacements, dependency upgrades, and I/O reduction are all fair game. Small logic tweaks that only shave a few milliseconds on a 1000-file run are not worth pursuing. Aim for changes with meaningful, measurable impact.
Think broadly — algorithm changes, architectural restructuring, parallelization, caching strategies, library replacements, dependency upgrades, I/O reduction, peak memory reduction, memory leak fixes, and startup time reduction are all fair game. Small logic tweaks that only shave a few milliseconds on a 1000-file run are not worth pursuing. Aim for changes with meaningful, measurable impact.

# Steps

## Investigation & Planning

Spawn 10 agents in parallel to investigate efficiently and thoroughly, then form an improvement plan.
First, define 5 non-overlapping investigation scopes — partition by directory boundaries, cross-cutting concerns (I/O, memory, parallelism, algorithmic complexity, dependency weight), or pipeline stages. Then spawn 5 agents in parallel, assigning each agent exactly one scope with an explicit description of what it covers. After all agents report back, synthesize findings and form an improvement plan.
Even if multiple improvements are identified, scope the work to what fits in a single PR — focus on the highest-impact change only.

## Implementation
Expand Down
3 changes: 2 additions & 1 deletion biome.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,8 @@
"!**/website/client/.vitepress/cache",
"!**/website/server/dist",
"!**/browser/dist",
"!**/browser/packages"
"!**/browser/packages",
"!.claude/worktrees"
Comment thread
yamadashy marked this conversation as resolved.
]
},
"assist": { "actions": { "source": { "organizeImports": "on" } } },
Expand Down
Loading