- Add ESLint configuration (eslint.config.mjs) for TypeScript/JavaScript linting - Update executor prompts to include lint instruction before code submission - Add lint check to triage prompt validation workflow - Update agent prompts to emphasize lint compliance as quality requirement - Add lint tool to agent toolset with file-level rule disabling capability - Include lint in CI workflow with non-blocking status - Update tests to verify lint-inclusive prompt behavior - Add documentation for lint integration in contributing.md - Add changeset for @gsxdsm/fusion minor release
3.2 KiB
Contributing
Thanks for contributing to Fusion.
Development Setup
Prerequisites
- Node.js (current LTS recommended)
- pnpm (
packageManageris pnpm) - Git
piruntime/auth configured for AI features
Install dependencies
pnpm install
Build all packages
pnpm build
Workspace Package Overview
| Package | Purpose |
|---|---|
@fusion/core |
Shared domain types, stores, persistence, and core utilities |
@fusion/dashboard |
Express API + React UI |
@fusion/engine |
Scheduling, triage, execution, merge orchestration |
@fusion/tui |
Ink-based terminal UI components |
@gsxdsm/fusion |
Published CLI + pi extension |
Development Workflow
pnpm dev # build + run CLI entrypoint in dev mode
pnpm dev:ui # dashboard dev server only
pnpm lint # lint all packages
pnpm typecheck # workspace typechecks
pnpm test # workspace test suite
pnpm build # workspace builds
Quality Gate Checklist
Before submitting changes, verify:
pnpm lint— lint passes with no errorspnpm test— all tests passpnpm typecheck— type checking passespnpm build— builds successfully
Testing Requirements
Use real test runs (not manual verification substitutes):
pnpm test
pnpm test:coverage
pnpm test:coverage:core
pnpm test:coverage:engine
pnpm test:coverage:cli
pnpm test:coverage:dashboard
Build Standalone Executables
Fusion supports standalone binary builds through Bun compile scripts in the CLI package.
pnpm build:exe # build host-target executable
pnpm build:exe:all # build multi-target executables
Release Process
Fusion uses Changesets + version PR workflow.
- See RELEASING.md for release flow details.
- For published package behavior changes, include a changeset.
Code Signing
Release binary signing setup is documented here:
Git / Commit Conventions
Use task-ID-scoped conventional commits:
feat(FN-XXX): ...fix(FN-XXX): ...test(FN-XXX): ...docs(FN-XXX): ...(for documentation-only changes)
Project Memory
When enabled, agents can read/write durable project memory:
.fusion/memory.md
Use it for reusable patterns, constraints, and pitfalls that should persist across tasks.
Background Memory Summarization
Fusion can automatically extract insights from working memory and prune transient content. Enable via insightExtractionEnabled setting:
.fusion/memory.md— Working memory (automatically pruned to durable items).fusion/memory-insights.md— Long-term distilled insights.fusion/memory-audit.md— Audit report after each extraction (includes pruning outcome)
See Settings Reference for configuration details.
SQLite Test Runner Pitfall
When running engine tests with Vitest and node:sqlite, ensure the engine Vitest config uses thread pool mode:
- ✅
pool: "threads" - ❌
pool: "vmThreads"
node:sqlite fails under Vitest VM contexts; using threads avoids that failure mode.