ChecKMarK DevTools holds the shared wiring across both work and personal repos: org-wide workflows, reusable agents, conventions, and configuration that don’t belong to any single project but quietly keep everything else moving. This is infrastructure in the most literal sense — you shouldn’t have to think about it very often, and when you do, it should already be doing the right thing.
🦄 Yes. It's boring—but in the best way! Invisibility is the point.
These tools are intentionally opinionated. Flexibility is usually where the thread started to unravel the last time I looked at it, so the majority of projects here choose guardrails over options. Eliminating a choice eliminates an entire class of problems in my life, and that tradeoff is made consciously.
This org leans utilitarian by design. If something looks minimal, it’s trying not to get in your way. If it feels strict, it’s because the alternative already caused trouble once and didn’t need the sequel.
These are the projects that best represent what ChecKMarK DevTools is actually about: reducing friction, enforcing clarity, and making sure systems behave the way we think they do.
rai-lint The spine of this org. Dual-language linting for AI attribution commit footers across Node and Python. Same rules, same expectations, enforced automatically. This exists because standards don’t survive vibes-based enforcement.
eslint-config-echo Shared ESLint configs for v8 and v9 that stop teams from relitigating the same decisions forever. Built for real enterprise flows with Prettier, Sonar, Jest, and Jira in mind. Opinionated on purpose.
delegate-action A GitHub Action that lets agents do useful work without quietly taking control. Prompts become stacked PRs, humans stay in the review loop, and nothing merges itself behind your back.
devto-mirror (moving here) Static GitHub Pages mirrors for Dev.to blogs to improve crawlability, indexing, and AI consumption without breaking canonical ownership. Exists because “the content is public” doesn’t mean it’s discoverable.
checkmark-upkeep-docs-agentic-test A proving ground for agentic documentation workflows. This is where ideas get stress-tested, misbehave, and either mature into tools or get discarded without ceremony.
Everything here should be assumed licensed under the PolyForm Shield License 1.0.0 unless explicitly stated otherwise.
You’re free to use it, fork it, change it, adapt it, rewrite it, and run it inside your own workflows. That freedom is intentional. What isn’t optional is monetization: nobody is getting paid for my work before I am. If something here becomes part of a profit-making product or service, I expect to be first in line for that conversation.
Use anything that helps and ignore the rest. I don’t need fireworks, but stars are always appreciated.
GitHub Copilot, ChatGPT, Verdent, and number of friends were actively used throughout design, implementation, and documentation across this organization. All outputs were human-directed, mostly reviewed, and integrated with intent rather than automation for its own sake.