luthersystems

Create a new GitHub release with version tag and release notes. Determines the next version, verifies main, tags, and creates a GitHub release. Examples: 'create a release', 'release v0.15.0', 'cut a new version'.

Use when making any code change to this repo. Covers the full edit-lint-build-test loop with exact commands. Examples: 'implement this feature', 'fix this bug', 'add a new package'.

Pick up a GitHub issue and implement it end-to-end. Reads the issue, creates a branch, implements the fix/feature, verifies, and creates a PR. Examples: 'pickup issue #67', 'work on issue 55', 'grab that issue'.

Ship changes by creating a pull request. Runs verification first, then pushes and creates PR with repo conventions. Examples: 'create a PR', 'open a pull request', 'ship this'.

Local CI mirror. Run all checks that CI runs before pushing. Use before creating a PR or when you want to validate your changes match CI. Examples: 'verify my changes', 'run CI checks locally', 'check if this will pass CI'.

Core development loop for making code changes. Use when implementing features, fixing bugs, or refactoring. Triggers: 'implement', 'make a change', 'add feature', 'fix bug'.

Full lifecycle from GitHub issue to merged PR. Reads the issue, creates a branch, implements the fix/feature, verifies, and opens a PR. Triggers: 'pickup issue #N', 'work on issue', 'grab an issue'.

Ship changes via pull request. Runs verification, pushes, and creates a PR targeting main. Triggers: 'create PR', 'open PR', 'ship it', 'submit for review'.

Create a new release with a semver tag and GitHub release. Triggers: 'release', 'cut a release', 'tag a new version', 'create release'.

Local CI mirror. Run all checks that GitHub Actions runs before pushing. Use before creating PRs or to debug CI failures. Triggers: 'verify', 'check', 'run CI locally', 'pre-push check'.

Use when the user mentions infrastructure, cloud, AWS, GCP, Terraform, deployment, DevOps, containers, Kubernetes, serverless, VPC, networking, databases, load balancers, CDN, monitoring, or asks to "design infrastructure", "set up cloud", "deploy my app", "estimate cloud costs", "generate terraform", "inspect my deployment", "what would this cost on AWS/GCP", or discusses scaling, high availability, disaster recovery, or compliance requirements for cloud infrastructure.

Use when working with ELPS Lisp code, substrate phylum code, or .lisp files. Provides hover docs, go-to-definition, find-references, diagnostics, performance analysis, eval, test, and formatting for ELPS code with full substrate builtin awareness (cc:*, statedb:*, sidedb:*, crypto:*, router:*). Also provides the complete shirotester CLI for linting, debugging, REPL, and test execution.

Use the mars infrastructure tool for terraform, ansible, and packer operations

Use when the user mentions infrastructure, cloud, AWS, GCP, Terraform, deployment, DevOps, containers, Kubernetes, serverless, VPC, networking, databases, load balancers, CDN, monitoring, or asks to "design infrastructure", "set up cloud", "deploy my app", "estimate cloud costs", "generate terraform", "inspect my deployment", "what would this cost on AWS/GCP", or discusses scaling, high availability, disaster recovery, or compliance requirements for cloud infrastructure.