Programmatically define and detect the 'scope' of a tree-sitter node

AI Contexts, Commands, Plugins, Docs, Examples, Specs, Etc

My personal GitHub Actions

Helm charts registry accessible in artifacthub.io, https://charts.arusty.dev, and from the repo url

Dev Toolbx Container images for docker based development

git subcommand compatible tool for creating atomic commits & branches

My blog (testing)

My brand resources (Logo's, photos, Minified CSS/JS, etc) centralized into one repo

A hybrid n-gram + neural model for conventional commits and CHANGELOG generation

Centrally managed schemas (primarily json) that can be referenced remotely

Central Justfile repo

HTMX-enhanced alternative backend for mdBook with server-side rendering, authorization, and audience scopes

GitHub App for facilitating dynamic cross-repo authentication, with traceability

MDBook backend that outputs Wiki.js-compatible markdown with schema validation

MCP Server implementation for https://github.com/Cyberwatch/Pentest-Collaboration-Framework

Zed LSP Extension for Sieve

zed-extension for Tide language (my custom DSL)

AppleScript Language Extension for Zed

VS Code Extension for Tide language

My first attempt at creating a helm chart, hopefully this will eventually be reliable

https://code.visualstudio.com/api/get-started/your-first-extension

Tree-sitter grammar for Tide language (my custom DSL)