GitLane

Imported from Siomkin/GitLane (AGENTS.md). Install upstream with npx skills add Siomkin/GitLane. Copyright stays with the author.

AGENTS.md

Guidance for Codex (and any other coding agent) working in this repository.

This file is intentionally thin to avoid drift. The canonical guidance lives in two files — read them before making changes; they are the source of truth:

• CLAUDE.md — what GitLane is, the build/verify commands, and the full architecture (the Tauri IPC contract, the read/write split, the Rust gotchas, the Zustand store layout, and the frontend structure).
• docs/rules/architecture-rules.md — the enforceable checklist to follow when implementing new functionality (the cross-cutting IPC contract, read/write split, definition of done, anti-patterns), with side-specific rules in architecture-rules-rust.md and architecture-rules-react.md (the latter covers SOLID / module decomposition).

Keep this file thin: when guidance changes, edit CLAUDE.md / the docs/rules/architecture-rules*.md files, not this file.

The non-negotiables (full detail in the files above)

• OpenSpec lives in this repo (openspec/, store id gitlane). From GitLane/ the nearest root wins; from the GitLaneProject parent pass --store gitlane. Site specs are --store landing. See CLAUDE.md § Planning.
• Package manager is bun, never npm/yarn. Verify a change with the check suite in CLAUDE.md § Commands (tsc, cargo fmt/clippy, bun run test, sizes, cycles).
• Rust core (src-tauri/) + React/TS frontend (src/), bridged by Tauri IPC. An IPC change touches four layers in lockstep — see docs/rules/architecture-rules.md §1.
• Reads use libgit2; writes shell out to real git; forges shell out to gh / glab / origin. Don't reimplement writes with libgit2 — see docs/rules/architecture-rules.md §2.
• Frontend tests run on vitest + Testing Library (bun run test); the IPC boundary is mocked inline per test file with vi.hoisted + vi.mock (see src/test/README.md). Coverage is partial, so the typechecks are still the primary safety net.