asgard 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 1c25b1efcac0de2f525140327f64753c1cb7b0cf82904ea6c4e1be1114b619bf
+  data.tar.gz: 857e98381996d06968944ed6bafb6b35d86073523672ac6d987ce2fb85a8cc79
+SHA512:
+  metadata.gz: 383ececde0765e801b1e84dc239895ee0d2ffe491fc6d0c0c4d3a583f0a0912f64ca8dc4a4a6469f12efcae93358302ada9aeb648b6a95ada4fe866c205306b0
+  data.tar.gz: 3d2ecd3d0dcc3acdaa1ecd6dd6457ce02c23b086c36f178b9aa378ec620069ae99e9ecae3d824d26f0d22fb5906a4b34bc1831a2040abf24bab81833080b470e

data/.envrc

@@ -0,0 +1 @@
+export RR=`pwd`

data/.loki

@@ -0,0 +1,34 @@
+# default task filename for the asgard task runner
+
+class Tasks < Asgard::Base
+  var :gem_name, "asgard"
+  var :version,  -> { Asgard::VERSION }
+
+  desc "test", "Run the test suite"
+  def test
+    sh "bundle exec rake test"
+  end
+
+  depends_on :test
+  desc "quality", "Run tests then flog"
+  def quality
+    sh "flog lib/"
+  end
+
+  desc "build", "Build the gem package"
+  def build
+    sh "bundle exec rake build"
+  end
+
+  depends_on :test
+  desc "install", "Build and install gem locally"
+  def install
+    sh "bundle exec rake install"
+  end
+
+  depends_on :quality
+  desc "release", "Release to RubyGems"
+  def release
+    sh "bundle exec rake release"
+  end
+end

data/CHANGELOG.md

@@ -0,0 +1,29 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-05-28
+
+### Added
+
+- `Asgard::Base` — Thor subclass providing the task DSL
+- `depends_on` — declare recipe dependencies resolved via `SimpleFlow::DependencyGraph`; dependencies run at most once per invocation
+- `var` — declare static or lazy-evaluated variables available to all recipes
+- `import` — flat-merge a task module into the current class
+- `dotenv` — load a `.env` file into the environment
+- `sh` — run a shell command or multiline heredoc script; exits with the command's status on failure
+- `shebang` — write a script body to a tempfile and execute it with a given interpreter (`:python3`, `:node`, `:ruby`, `:perl`, `:bash`, `:sh`, or any custom interpreter)
+- `Asgard.find_task_files` — search current directory and ancestors for task files
+- Task file resolution: `.loki` takes priority; falls back to all `*.loki` files sorted alphabetically
+- `asgard` executable — finds task files, validates dependency graph, dispatches via Thor
+- Circular dependency detection via `SimpleFlow::DependencyGraph` at startup
+- 100% test coverage enforced via SimpleCov (95% minimum threshold)
+- Quality task in `.loki` runs flog after tests
+
+[Unreleased]: https://github.com/MadBomber/asgard/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/MadBomber/asgard/releases/tag/v0.1.0

data/COMMITS.md

@@ -0,0 +1,196 @@
+---
+url: https://www.conventionalcommits.org/en/v1.0.0/
+title: Conventional Commits
+description: A specification for adding human and machine readable meaning to commit messages
+access_date: 2025-07-31T20:51:29.000Z
+current_date: 2025-07-31T20:51:29.601Z
+---
+
+# Conventional Commits
+
+A specification for adding human and machine readable meaning to commit messages
+
+ Quick Summary Full Specification Contribute
+
+# Conventional Commits 1.0.0
+
+## Summary
+
+The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages.
+
+The commit message should be structured as follows:
+
+---
+
+```
+<type>[optional scope]: <description>
+
+[optional body]
+
+[optional footer(s)]
+
+```
+
+---
+
+The commit contains the following structural elements, to communicate intent to the consumers of your library:
+
+1. **fix:** a commit of the _type_ `fix` patches a bug in your codebase (this correlates with `PATCH` in Semantic Versioning).
+2. **feat:** a commit of the _type_ `feat` introduces a new feature to the codebase (this correlates with `MINOR` in Semantic Versioning).
+3. **BREAKING CHANGE:** a commit that has a footer `BREAKING CHANGE:`, or appends a `!` after the type/scope, introduces a breaking API change (correlating with `MAJOR` in Semantic Versioning). A BREAKING CHANGE can be part of commits of any _type_.
+4. _types_ other than `fix:` and `feat:` are allowed, for example @commitlint/config-conventional (based on the Angular convention) recommends `build:`, `chore:`,`ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, and others.
+5. _footers_ other than `BREAKING CHANGE: <description>` may be provided and follow a convention similar to git trailer format.
+
+Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic Versioning (unless they include a BREAKING CHANGE). A scope may be provided to a commit’s type, to provide additional contextual information and is contained within parenthesis, e.g., `feat(parser): add ability to parse arrays`.
+
+## Examples
+
+### Commit message with description and breaking change footer
+
+```
+feat: allow provided config object to extend other configs
+
+BREAKING CHANGE: `extends` key in config file is now used for extending other config files
+
+```
+
+### Commit message with `!` to draw attention to breaking change
+
+```
+feat!: send an email to the customer when a product is shipped
+
+```
+
+### Commit message with scope and `!` to draw attention to breaking change
+
+```
+feat(api)!: send an email to the customer when a product is shipped
+
+```
+
+### Commit message with both `!` and BREAKING CHANGE footer
+
+```
+chore!: drop support for Node 6
+
+BREAKING CHANGE: use JavaScript features not available in Node 6.
+
+```
+
+### Commit message with no body
+
+```
+docs: correct spelling of CHANGELOG
+
+```
+
+### Commit message with scope
+
+```
+feat(lang): add Polish language
+
+```
+
+### Commit message with multi-paragraph body and multiple footers
+
+```
+fix: prevent racing of requests
+
+Introduce a request id and a reference to latest request. Dismiss
+incoming responses other than from latest request.
+
+Remove timeouts which were used to mitigate the racing issue but are
+obsolete now.
+
+Reviewed-by: Z
+Refs: #123
+
+```
+
+## Specification
+
+The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
+
+1. Commits MUST be prefixed with a type, which consists of a noun, `feat`, `fix`, etc., followed by the OPTIONAL scope, OPTIONAL `!`, and REQUIRED terminal colon and space.
+2. The type `feat` MUST be used when a commit adds a new feature to your application or library.
+3. The type `fix` MUST be used when a commit represents a bug fix for your application.
+4. A scope MAY be provided after a type. A scope MUST consist of a noun describing a section of the codebase surrounded by parenthesis, e.g., `fix(parser):`
+5. A description MUST immediately follow the colon and space after the type/scope prefix. The description is a short summary of the code changes, e.g., _fix: array parsing issue when multiple spaces were contained in string_.
+6. A longer commit body MAY be provided after the short description, providing additional contextual information about the code changes. The body MUST begin one blank line after the description.
+7. A commit body is free-form and MAY consist of any number of newline separated paragraphs.
+8. One or more footers MAY be provided one blank line after the body. Each footer MUST consist of a word token, followed by either a `:<space>` or `<space>#` separator, followed by a string value (this is inspired by the git trailer convention).
+9. A footer’s token MUST use `-` in place of whitespace characters, e.g., `Acked-by` (this helps differentiate the footer section from a multi-paragraph body). An exception is made for `BREAKING CHANGE`, which MAY also be used as a token.
+10. A footer’s value MAY contain spaces and newlines, and parsing MUST terminate when the next valid footer token/separator pair is observed.
+11. Breaking changes MUST be indicated in the type/scope prefix of a commit, or as an entry in the footer.
+12. If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon, space, and description, e.g.,_BREAKING CHANGE: environment variables now take precedence over config files_.
+13. If included in the type/scope prefix, breaking changes MUST be indicated by a`!` immediately before the `:`. If `!` is used, `BREAKING CHANGE:` MAY be omitted from the footer section, and the commit description SHALL be used to describe the breaking change.
+14. Types other than `feat` and `fix` MAY be used in your commit messages, e.g., _docs: update ref docs._
+15. The units of information that make up Conventional Commits MUST NOT be treated as case sensitive by implementors, with the exception of BREAKING CHANGE which MUST be uppercase.
+16. BREAKING-CHANGE MUST be synonymous with BREAKING CHANGE, when used as a token in a footer.
+
+## Why Use Conventional Commits
+
+* Automatically generating CHANGELOGs.
+* Automatically determining a semantic version bump (based on the types of commits landed).
+* Communicating the nature of changes to teammates, the public, and other stakeholders.
+* Triggering build and publish processes.
+* Making it easier for people to contribute to your projects, by allowing them to explore a more structured commit history.
+
+## FAQ
+
+### How should I deal with commit messages in the initial development phase?
+
+We recommend that you proceed as if you’ve already released the product. Typically _somebody_, even if it’s your fellow software developers, is using your software. They’ll want to know what’s fixed, what breaks etc.
+
+### Are the types in the commit title uppercase or lowercase?
+
+Any casing may be used, but it’s best to be consistent.
+
+### What do I do if the commit conforms to more than one of the commit types?
+
+Go back and make multiple commits whenever possible. Part of the benefit of Conventional Commits is its ability to drive us to make more organized commits and PRs.
+
+### Doesn’t this discourage rapid development and fast iteration?
+
+It discourages moving fast in a disorganized way. It helps you be able to move fast long term across multiple projects with varied contributors.
+
+### Might Conventional Commits lead developers to limit the type of commits they make because they’ll be thinking in the types provided?
+
+Conventional Commits encourages us to make more of certain types of commits such as fixes. Other than that, the flexibility of Conventional Commits allows your team to come up with their own types and change those types over time.
+
+### How does this relate to SemVer?
+
+`fix` type commits should be translated to `PATCH` releases. `feat` type commits should be translated to `MINOR` releases. Commits with `BREAKING CHANGE` in the commits, regardless of type, should be translated to `MAJOR` releases.
+
+### How should I version my extensions to the Conventional Commits Specification, e.g. `@jameswomack/conventional-commit-spec`?
+
+We recommend using SemVer to release your own extensions to this specification (and encourage you to make these extensions!)
+
+### What do I do if I accidentally use the wrong commit type?
+
+#### When you used a type that’s of the spec but not the correct type, e.g. `fix` instead of `feat`
+
+Prior to merging or releasing the mistake, we recommend using `git rebase -i` to edit the commit history. After release, the cleanup will be different according to what tools and processes you use.
+
+#### When you used a type _not_ of the spec, e.g. `feet` instead of `feat`
+
+In a worst case scenario, it’s not the end of the world if a commit lands that does not meet the Conventional Commits specification. It simply means that commit will be missed by tools that are based on the spec.
+
+### Do all my contributors need to use the Conventional Commits specification?
+
+No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they’re merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
+
+### How does Conventional Commits handle revert commits?
+
+Reverting code can be complicated: are you reverting multiple commits? if you revert a feature, should the next release instead be a patch?
+
+Conventional Commits does not make an explicit effort to define revert behavior. Instead we leave it to tooling authors to use the flexibility of _types_ and _footers_ to develop their logic for handling reverts.
+
+One recommendation is to use the `revert` type, and a footer that references the commit SHAs that are being reverted:
+
+```
+revert: let us never again speak of the noodle incident
+
+Refs: 676104e, a215868
+
+```

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2026 Dewayne VanHoozer
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,260 @@
+# Asgard
+
+A [just](https://just.systems)-like task runner for Ruby. Define project recipes in a `.loki` file and run them with the `asgard` command. Built on [Thor](https://github.com/rails/thor) for argument handling and [SimpleFlow](https://github.com/madbomber/simple_flow) for dependency ordering.
+
+The name comes from Norse mythology: **Thor** is the CLI framework, **Asgard** is the realm where tasks live, and the task file is named **loki** — because Loki holds all the tricks.
+
+## Installation
+
+```bash
+gem install asgard
+```
+
+Or add to your Gemfile:
+
+```bash
+bundle add asgard
+```
+
+## Quick Start
+
+Create a `.loki` file at your project root. `sh` runs any shell command — a single line or a multiline heredoc:
+
+```ruby
+# filename: .loki
+
+class Tasks < Asgard::Base
+  desc "deps", "Install project dependencies"
+  def deps
+    sh <<~SHELL
+      brew install redis
+      npm install
+      bundle install
+    SHELL
+  end
+
+  depends_on :deps
+  desc "test", "Run the test suite"
+  def test
+    sh "bundle exec rake test"
+  end
+
+  depends_on :test
+  desc "release", "Tag and publish the gem"
+  def release
+    sh <<~SHELL
+      git tag v$(ruby -r./lib/my_gem/version -e 'puts MyGem::VERSION')
+      git push --tags
+      bundle exec rake release
+    SHELL
+  end
+end
+```
+
+Then run tasks from any directory in the project tree:
+
+```bash
+asgard test       # runs deps, then test
+asgard release    # runs deps, then test, then release
+asgard help       # list all available tasks
+```
+
+## Task Files
+
+Asgard searches the current directory and its ancestors for task files, in this order:
+
+1. **`.loki`** — the hidden default. Found alone, takes priority over everything.
+2. **`*.loki`** — all matching files loaded alphabetically when no `.loki` exists.
+
+This means you can split a large task set across multiple files:
+
+```
+deploy.loki
+test.loki
+build.loki        # loaded as: build.loki, deploy.loki, test.loki
+```
+
+Or use a single hidden default:
+
+```
+.loki             # takes priority, *.loki files are ignored
+```
+
+## Features
+
+### Task dependencies
+
+```ruby
+depends_on :build
+desc "test", "Run tests"
+def test
+  sh "bundle exec rake test"
+end
+```
+
+Dependencies run before the recipe, at most once per invocation regardless of how many recipes declare them. Circular dependencies are caught at startup via `SimpleFlow::DependencyGraph`.
+
+### Variables
+
+```ruby
+var :app,     "myapp"
+var :version, -> { `git describe --tags`.strip }   # lazy, evaluated on first use
+
+desc "tag", "Create a git tag"
+def tag
+  sh "git tag #{version}"
+end
+```
+
+### Multi-line shell scripts
+
+```ruby
+desc "setup", "Bootstrap the dev environment"
+def setup
+  sh <<~SHELL
+    brew install redis postgresql
+    brew services start redis
+    bundle install
+    rails db:setup
+  SHELL
+end
+```
+
+### Embedded scripts in other languages
+
+```ruby
+desc "analyze", "Run data analysis"
+def analyze
+  shebang :python3, <<~PYTHON
+    import json
+    data = json.load(open("results.json"))
+    print(f"Total: {sum(data.values())}")
+  PYTHON
+end
+
+desc "bundle", "Build frontend assets"
+def bundle_assets
+  shebang :node, <<~JS
+    const esbuild = require("esbuild")
+    esbuild.buildSync({ entryPoints: ["src/app.js"], bundle: true, outfile: "dist/app.js" })
+  JS
+end
+```
+
+Supported interpreters: `:python3`, `:python`, `:node`, `:ruby`, `:perl`, `:bash`, `:sh`. Any other symbol is passed directly to `system` with a `.tmp` extension.
+
+### Importing task modules
+
+Split tasks into reusable modules and include them flat (all tasks in the same namespace):
+
+```ruby
+# shared/deploy_tasks.rb
+module DeployTasks
+  def self.included(base)
+    base.desc "deploy", "Deploy to production"
+    base.define_method(:deploy) { sh "cap production deploy" }
+  end
+end
+
+# .loki
+require_relative "shared/deploy_tasks"
+
+class Tasks < Asgard::Base
+  import DeployTasks
+end
+```
+
+For namespaced subcommands, use Thor's `register`:
+
+```ruby
+register DeployTasks, "deploy", "deploy COMMAND", "Deployment tasks"
+# invoked as: asgard deploy production
+```
+
+### Dotenv
+
+```ruby
+class Tasks < Asgard::Base
+  dotenv          # loads .env from CWD
+  dotenv ".env.local"
+
+  desc "check", "Print the app name"
+  def check
+    sh "echo $APP_NAME"
+  end
+end
+```
+
+### Echo suppression
+
+Pass `silent: true` to suppress the command echo (equivalent to `just`'s `@` prefix):
+
+```ruby
+def build
+  sh "bundle exec rake build", silent: true   # runs quietly, output still shown
+end
+```
+
+## Shell helpers
+
+| Method | Description |
+|---|---|
+| `sh(script, silent: false)` | Run a shell command or multiline script |
+| `shebang(interpreter, script, silent: false)` | Write script to a tempfile and execute it |
+
+Both exit with the command's status code on failure.
+
+## Full example `.loki`
+
+```ruby
+require "asgard"
+
+class Tasks < Asgard::Base
+  dotenv
+
+  var :app,     "myapp"
+  var :version, -> { File.read("VERSION").strip }
+
+  desc "test", "Run the test suite"
+  def test
+    sh "bundle exec rake test"
+  end
+
+  depends_on :test
+  desc "quality", "Run tests then check complexity"
+  def quality
+    sh "flog lib/"
+  end
+
+  desc "build", "Build the gem"
+  def build
+    sh "bundle exec rake build"
+  end
+
+  depends_on :quality, :build
+  desc "release", "Release #{version} to RubyGems"
+  def release
+    sh "bundle exec rake release"
+  end
+end
+```
+
+## Development
+
+```bash
+git clone git@github.com:MadBomber/asgard.git
+cd asgard
+bundle install
+bundle exec rake test       # run tests with coverage
+bundle exec bin/asgard help # try the CLI against this gem's own .loki file
+```
+
+Coverage threshold is enforced at 95% via SimpleCov.
+
+## Contributing
+
+Bug reports and pull requests are welcome at https://github.com/MadBomber/asgard.
+
+## License
+
+MIT. See [LICENSE.txt](LICENSE.txt).

data/Rakefile

@@ -0,0 +1,22 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "minitest/test_task"
+
+SIMPLECOV_PRELUDE = <<~RUBY.freeze
+  require "simplecov"
+  SimpleCov.start do
+    add_filter "/test/"
+    minimum_coverage 95
+  end
+RUBY
+
+Minitest::TestTask.create do |t|
+  t.test_prelude = SIMPLECOV_PRELUDE
+end
+
+task quality: :test do
+  sh "flog lib/"
+end
+
+task default: :test

data/bin/asgard

@@ -0,0 +1,24 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require "asgard"
+
+task_files = Asgard.find_task_files
+
+unless task_files
+  warn "asgard: no .loki or *.loki task file found in #{Dir.pwd} or any parent directory"
+  exit 1
+end
+
+task_files.each { |f| load f }
+
+klass = Asgard::Base.subclasses.last
+
+unless klass
+  warn "asgard: no class inheriting Asgard::Base found in #{task_files.join(', ')}"
+  exit 1
+end
+
+klass.validate_deps!
+klass._reset_ran!
+klass.start(ARGV)

data/bin/console

@@ -0,0 +1,11 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require "bundler/setup"
+require "asgard"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/lib/asgard/base.rb

@@ -0,0 +1,156 @@
+# frozen_string_literal: true
+
+require "thor"
+require "set"
+require "simple_flow"
+
+module Asgard
+  class Base < Thor
+    include Asgard::Shell
+
+    class << self
+      def subclasses
+        @subclasses ||= []
+      end
+
+      def inherited(subclass)
+        super
+        Asgard::Base.subclasses << subclass
+        subclass.instance_variable_set(:@_deps,         {})
+        subclass.instance_variable_set(:@_vars,         {})
+        subclass.instance_variable_set(:@_pending_deps, [])
+        subclass.instance_variable_set(:@_ran_tasks,    Set.new)
+        subclass.instance_variable_set(:@_ran_mutex,    Mutex.new)
+      end
+
+      def _deps
+        @_deps ||= {}
+      end
+
+      def _vars
+        @_vars ||= {}
+      end
+
+      def _ran_tasks
+        @_ran_tasks ||= Set.new
+      end
+
+      def _ran_mutex
+        @_ran_mutex ||= Mutex.new
+      end
+
+      # Reset execution tracking for a fresh asgard invocation.
+      def _reset_ran!
+        _ran_mutex.synchronize { @_ran_tasks = Set.new }
+      end
+
+      # Translate stages into a DependencyGraph-compatible hash.
+      #
+      #   stages: [[:one], [:two, :three], [:four]]
+      #   → { one: [], two: [:one], three: [:one], four: [:two, :three] }
+      def _build_dep_graph(stages)
+        graph = {}
+        stages.each_with_index do |stage, i|
+          prev_stage = i > 0 ? stages[i - 1] : []
+          stage.each { |task| graph[task] = prev_stage.dup }
+        end
+        graph
+      end
+
+      # Declare dependencies for the next recipe.
+      # Bare symbols run sequentially; arrays within the splat run in parallel.
+      #
+      #   depends_on :build                          # sequential
+      #   depends_on :build, :lint                   # both sequential
+      #   depends_on [:build, :lint]                 # build and lint in parallel
+      #   depends_on :setup, [:build, :lint], :test  # setup, then build+lint, then test
+      def depends_on(*recipes)
+        @_pending_deps = recipes
+      end
+
+      def var(name, value = nil, &block)
+        value = block if block_given?
+        _vars[name.to_sym] = value
+        no_commands do
+          define_method(name) do
+            v = self.class._vars[name.to_sym]
+            v.respond_to?(:call) ? v.call : v
+          end
+        end
+      end
+
+      def import(mod)
+        include mod
+      end
+
+      def dotenv(path = ".env")
+        require "dotenv"
+        Dotenv.load(path) if File.exist?(path)
+      end
+
+      # Validate the full dep graph for cycles using SimpleFlow::DependencyGraph.
+      def validate_deps!
+        return if _deps.empty?
+
+        all_tasks  = all_commands.keys.map(&:to_sym)
+        full_graph = all_tasks.each_with_object({}) do |task, hash|
+          hash[task] = _deps.fetch(task, []).flatten
+        end
+
+        SimpleFlow::DependencyGraph.new(full_graph).order
+      rescue TSort::Cyclic => e
+        raise Asgard::CircularDependencyError, e.message
+      end
+
+      def method_added(method_name)
+        pending = Array(@_pending_deps).dup
+        @_pending_deps = []
+
+        return super if pending.empty?
+        return super if method_name.to_s.start_with?("_")
+
+        # Each element is a Symbol (sequential) or Array (parallel group).
+        _deps[method_name.to_sym] = pending.map { |d| Array(d).map(&:to_sym) }
+        super
+      end
+    end
+
+    no_commands do
+      # Dispatch hook: resolves and runs all deps (in parallel where declared)
+      # before executing the target command. Thread-safe deduplication via
+      # the class-level _ran_tasks set ensures each recipe runs at most once.
+      def invoke_command(command, *args)
+        target = command.name.to_sym
+
+        should_run = self.class._ran_mutex.synchronize do
+          next false if self.class._ran_tasks.include?(target)
+          self.class._ran_tasks.add(target)
+          true
+        end
+        return unless should_run
+
+        stages = self.class._deps[target]
+        if stages&.any?
+          graph  = self.class._build_dep_graph(stages)
+          groups = SimpleFlow::DependencyGraph.new(graph).parallel_order
+
+          groups.each do |group|
+            if group.size > 1
+              threads = group.map { |task| Thread.new { _run_dep(task) } }
+              threads.each(&:join)
+            else
+              _run_dep(group.first)
+            end
+          end
+        end
+
+        command.run(self, *args)
+      end
+
+      def _run_dep(task)
+        command = self.class.all_commands[task.to_s]
+        invoke_command(command) if command
+      end
+    end
+  end
+end

data/lib/asgard/shell.rb

@@ -0,0 +1,43 @@
+# frozen_string_literal: true
+
+require "tempfile"
+
+module Asgard
+  module Shell
+    # Run a shell script. Multiline strings are passed to bash -c; single-line
+    # strings are passed to system directly. Exits with the command's status
+    # code on failure.
+    def sh(script, silent: false)
+      script = script.strip
+      $stdout.puts script unless silent
+
+      success = if script.include?("\n")
+        system("bash", "-c", script)
+      else
+        system(script)
+      end
+
+      exit($?.exitstatus) unless success
+    end
+
+    # Write +script+ to a tempfile and execute it with +interpreter+.
+    # Useful for embedding Python, Node, Ruby, or any shebang-style body.
+    def shebang(interpreter, script, silent: false)
+      extensions = {
+        python3: ".py", python: ".py",
+        node:    ".js",
+        ruby:    ".rb",
+        perl:    ".pl",
+        bash:    ".sh", sh: ".sh"
+      }
+      ext = extensions.fetch(interpreter.to_sym, ".tmp")
+
+      Tempfile.create(["asgard_", ext]) do |f|
+        f.write(script)
+        f.flush
+        system(interpreter.to_s, f.path)
+        exit($?.exitstatus) unless $?.success?
+      end
+    end
+  end
+end

data/lib/asgard/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module Asgard
+  VERSION = "0.1.0"
+end

data/lib/asgard.rb

@@ -0,0 +1,32 @@
+# frozen_string_literal: true
+
+require_relative "asgard/version"
+require_relative "asgard/shell"
+require_relative "asgard/base"
+
+module Asgard
+  class Error < StandardError; end
+  class CircularDependencyError < Error; end
+
+  # Search the current directory and its ancestors for task files.
+  # Returns an array of paths, or nil if nothing is found.
+  #
+  # Priority:
+  #   1. A single .loki file in the directory (default/hidden task file)
+  #   2. All *.loki files in the directory, sorted alphabetically
+  def self.find_task_files
+    dir = Dir.pwd
+    loop do
+      dot_loki = File.join(dir, ".loki")
+      return [dot_loki] if File.exist?(dot_loki)
+
+      matches = Dir.glob(File.join(dir, "*.loki")).sort
+      return matches unless matches.empty?
+
+      parent = File.dirname(dir)
+      break if parent == dir
+      dir = parent
+    end
+    nil
+  end
+end

data/sig/asgard.rbs

@@ -0,0 +1,4 @@
+module Asgard
+  VERSION: String
+  # See the writing guide of rbs: https://github.com/ruby/rbs#guides
+end

metadata

@@ -0,0 +1,117 @@
+--- !ruby/object:Gem::Specification
+name: asgard
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Dewayne VanHoozer
+bindir: bin
+cert_chain: []
+date: 1980-01-02 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: logger
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: thor
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1.0'
+- !ruby/object:Gem::Dependency
+  name: simple_flow
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.4'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.4'
+- !ruby/object:Gem::Dependency
+  name: dotenv
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+description: 'Asgard brings just-style recipes to Ruby: Thor-powered CLI, dep ordering
+  via SimpleFlow::DependencyGraph, var declarations, dotenv, sh/shebang helpers, and
+  importable task modules.'
+email:
+- dewayne@vanhoozer.me
+executables:
+- asgard
+extensions: []
+extra_rdoc_files: []
+files:
+- ".envrc"
+- ".loki"
+- CHANGELOG.md
+- COMMITS.md
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/asgard
+- bin/console
+- bin/setup
+- lib/asgard.rb
+- lib/asgard/base.rb
+- lib/asgard/shell.rb
+- lib/asgard/version.rb
+- sig/asgard.rbs
+homepage: https://github.com/madbomber/asgard
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://github.com/madbomber/asgard
+  source_code_uri: https://github.com/madbomber/asgard
+  changelog_uri: https://github.com/madbomber/asgard/blob/master/CHANGELOG.md
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 3.2.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 4.0.12
+specification_version: 4
+summary: A just-like task runner built on Thor, with recipe dependencies via SimpleFlow.
+test_files: []