feat: configure prettier with pre-commit hook

[magyargergo]

Summary

• Configure Prettier as the code formatter for the monorepo with lint-staged + Husky pre-commit hook integration
• Format entire codebase (344 files, style-only — no logic changes)
• Pre-commit hook: lint-staged (prettier) → tsc (typecheck). Tests stay in CI only.

What's included

File	Change
package.json (root)	New — prettier, lint-staged, husky, prettier-plugin-tailwindcss
.prettierrc	New — singleQuote, trailingComma: "all", printWidth: 100, endOfLine: "lf", TW v4 tailwindStylesheet
.prettierignore	New — excludes fixtures, vendor, *.d.ts, *.snap, *.md
.gitattributes	New — * text=auto eol=lf for Windows line-ending consistency
.husky/pre-commit	Updated — lint-staged + tsc only (vitest removed, stays in CI)
gitnexus/package.json	Removed husky devDep (moved to root)
.git-blame-ignore-revs	New — hides bulk format commit from git blame

Key decisions

• lint-staged v15 (not v16) — v16 has Windows regressions with tinyexec
• endOfLine: "lf" + .gitattributes — prevents line-ending churn on Windows
• tailwindStylesheet (not tailwindConfig) — required for Tailwind CSS v4's CSS-based config
• No vitest in pre-commit — tests belong in CI, pre-commit should be fast (lint-staged + tsc)
• *.md excluded — markdown files have intentional formatting
• node_modules/.bin/ paths instead of npx — saves 2-7s on Windows per commit

Post-merge setup

Contributors run npm install at repo root to get prettier + activate Husky hooks. After merge, run:

git config blame.ignoreRevsFile .git-blame-ignore-revs

Test plan

• npx prettier --check . passes
• Test fixtures untouched (git diff gitnexus/test/fixtures/ is empty)
• Pre-commit hook runs lint-staged and tsc successfully
• npm install at root activates Husky hooks

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
gitnexus	Ready	Preview, Comment	Mar 28, 2026 2:46pm

[github-actions]

CI Report

✅ All checks passed

Pipeline Status

Stage	Status	Details
✅ Typecheck	success	tsc --noEmit
✅ Tests	success	unit tests, 3 platforms
✅ E2E	success	gitnexus-web changes only

Test Results

Tests	Passed	Failed	Skipped	Duration
4687	4641	0	46	165s

✅ All 4641 tests passed

46 test(s) skipped — expand for details

• buildTypeEnv > known limitations (documented skip tests) > Ruby block parameter: users.each { |user| } — closure param inference, different feature
• Swift constructor-inferred type resolution > detects User and Repo classes, both with save methods
• Swift constructor-inferred type resolution > resolves user.save() to Models/User.swift via constructor-inferred type
• Swift constructor-inferred type resolution > resolves repo.save() to Models/Repo.swift via constructor-inferred type
• Swift constructor-inferred type resolution > emits exactly 2 save() CALLS edges (one per receiver type)
• Swift self resolution > detects User and Repo classes, each with a save function
• Swift self resolution > resolves self.save() inside User.process to User.save, not Repo.save
• Swift parent resolution > detects BaseModel and User classes plus Serializable protocol
• Swift parent resolution > emits EXTENDS edge: User → BaseModel
• Swift parent resolution > emits IMPLEMENTS edge: User → Serializable (protocol conformance)
• Swift cross-file User.init() inference > resolves user.save() via User.init(name:) inference
• Swift cross-file User.init() inference > resolves user.greet() via User.init(name:) inference
• Swift return type inference > detects User class and getUser function
• Swift return type inference > detects save function on User (Swift class methods are Function nodes)
• Swift return type inference > resolves user.save() to User#save via return type of getUser() -> User
• Swift return-type inference via function return type > resolves user.save() to User#save via return type of getUser()
• Swift return-type inference via function return type > user.save() does NOT resolve to Repo#save
• Swift return-type inference via function return type > resolves repo.save() to Repo#save via return type of getRepo()
• Swift implicit imports (cross-file visibility) > detects UserService class in Models.swift
• Swift implicit imports (cross-file visibility) > resolves UserService() constructor call across files (no explicit import)
• Swift implicit imports (cross-file visibility) > resolves service.fetchUser() member call across files
• Swift implicit imports (cross-file visibility) > creates IMPORTS edges between files in the same module
• Swift extension deduplication > detects Product class
• Swift extension deduplication > resolves Product() constructor despite extension creating duplicate class node
• Swift extension deduplication > resolves product.save() to Product.swift (primary definition)
• Swift constructor call fallback (no new keyword) > resolves OCRService() as constructor call across files
• Swift constructor call fallback (no new keyword) > resolves ocr.recognize() member call via constructor-inferred type
• Swift export visibility (internal vs private) > resolves PublicService() constructor across files
• Swift export visibility (internal vs private) > resolves internalHelper() across files (internal = module-scoped)
• Swift if let / guard let binding resolution > detects User and Repo classes
• Swift if let / guard let binding resolution > resolves user.save() inside if-let to User#save
• Swift if let / guard let binding resolution > resolves repo.save() inside guard-let to Repo#save
• Swift if let / guard let binding resolution > user.save() in if-let does NOT resolve to Repo#save
• Swift await / try expression unwrapping > resolves user.save() via await fetchUser() return type
• Swift await / try expression unwrapping > resolves repo.save() via try parseRepo() return type
• Swift await / try expression unwrapping > detects fetchUser and parseRepo as functions
• Swift for-in loop element type inference > detects User and Repo classes
• Swift for-in loop element type inference > creates implicit import edges between files
• Swift field-type resolution > detects classes and their properties
• Swift field-type resolution > emits HAS_PROPERTY edges from class to field
• Swift field-type resolution > resolves field-chain call user.address.save() → Address#save
• Swift field-type resolution > emits ACCESSES edges for field reads in chains
• Swift field-type resolution > populates field metadata (visibility, declaredType) on Property nodes
• Swift call-result binding > resolves call-result-bound method call user.save() → User#save
• Swift call-result binding > getUser() is present as a defined function
• Swift call-result binding > emits processUser -> getUser CALLS edge for let-assigned free function call

Code Coverage

Tests

Metric	Coverage	Covered	Base	Delta	Status
Statements	70.58%	12500/17708	70.58%	＝ 0.0	🟢 ██████████████░░░░░░
Branches	60.03%	8236/13719	60.03%	＝ 0.0	🟢 ████████████░░░░░░░░
Functions	74.84%	1095/1463	74.84%	＝ 0.0	🟢 ██████████████░░░░░░
Lines	72.79%	11387/15643	73.07%	📉 -0.3	🔴 ██████████████░░░░░░

---

_{📋 View full run · Generated by CI}