nitpick

Opinionated code organization linter for Go projects.

Dispatch panels of specialized subagents to review projects — expert audits, first-impression personas, task-completion flows, and pedantic nitpicks

Shared settings for linters, type checking tools and VSCode

Nitpick Programming Language — systems language built for safety, determinism, and AI-native applications. LLVM backend, 15+ packages, LSP, DAP debugger, GPU codegen.

Updated version of IKOS to support LLVM 20. Originally developed for use for verification for the Nitpick programming language.

Run flow & eslint with nitpicky config on project

A terminal user-interface library for Nitpick — zero dependencies, no libc, no terminfo. Deterministic byte-level rendering, deadline-bounded input, and terminal restoration guaranteed on the trap path.

Nitpick programming guide, language specification, tutorials, and API documentation

A set of code style tool settings to enforce them in other projects.

Registry for the Nitpick package management system

Asynchronous script that downloads the HEAD contents of the repository https://gitea.radium.group/radium/project-configuration in a temporary folder of 3 streams. After performing all asynchronous tasks, the script counts sha256 hashes from each downloaded file.

Workbench for the Nitpick library ecosystem — the playbook for setting up and planning a library, and the registry of what exists.

BSD sockets for Nitpick — AF_UNIX, TCP and UDP over IPv4/IPv6, straight to the

Systematic hunt for memory-safety defects in the Nitpick compiler: an exhaustive grid of owning types × places × operations, run at -O0 and -O2, with a recall gate that must re-find every known defect first.

⚠️ Aria has been renamed to Nitpick. This repo is a redirect pointer — see nitpick for the active project.

Obviously Turing-complete, but not for the reasons you expect

Workbench for programs written in Nitpick — the playbook for planning an application, and the registry of what exists. Sibling of nitpick-libs.

Multi-format parsing for Nitpick — one event stream, one document model, one set of scanning primitives, formats as plugins. JSON, TOML, CSV and YAML. A syntax error is a value, not an error: no input can stop your program.

The POSIX utility set in Nitpick — no libc, no C, no external dependency in any artifact. One repository, a directory per utility.

Dates, times and time zones for Nitpick — zero dependency, no libc, no system tzdb. The IANA database is compiled in from a pinned release, so the same program gives the same answer on every machine. Monotonic and wall clocks are different types.