Bzl on Alwaldend

Agents

Mon, 01 Jan 0001 00:00:00 +0000

Repository agent skills

This project owns the reusable cross-repository agent skills. Maintained improvement work lives in this project’s OpenSpec workspace. It does not centralize component facts or runtime state: each fact remains canonical at its natural owner.

Start here

Document	Purpose
OpenSpec changes	Maintained work, acceptance, and preserved goal history
Root agent guide	Current repository-wide operating policy

Dated audits remain in migrated history.

Ownership boundaries

openspec/ owns agent-system requirements, changes, and evidence; the migration map locates historical records.
Other components own their specifications and changes under their own openspec/ directory. infra/src/openspec/ describes repository evolution.
skills/ owns reusable cross-product, repository-wide agent procedures and their development-time evaluations. A product-specific procedure belongs with its product; a procedure that no narrower project genuinely owns lives here rather than in a contrived local home.
Product-specific skills remain with their project at projects/<project>/skills/<name>. Do not split one skill across owners.

Skill packaging and discovery

Every canonical skill is packaged as a skill_library in its owning directory.

Agents

Mon, 01 Jan 0001 00:00:00 +0000

This project owns the reusable, cross-project agent skills used across this repository. Each skill is a procedure with its own scope and ownership rules, so an agent loads the guidance it needs for the task at hand instead of one large document.

Features

One skill per procedure, with an explicit description and scope
Discovery written into the agent skills directory from declared sources
Product-specific skills stay with their product; only genuinely shared ones live here

Al

Mon, 01 Jan 0001 00:00:00 +0000

AL is a command runner that prepares credentials and environment variables through plugins, runs your command, and cleans up afterward. Its Bazel rules package commands with their configuration and required plugins.

al tool runs tools declared in AL configuration from a source-keyed executable cache. With no --config, it uses the repository-root al.lua; explicit --config paths replace that default. Cache misses build the tool’s configured Bazel label and publish the selected executable under $XDG_CACHE_HOME/al/tools. AL_TOOL_CACHE or tool --cache-root PATH selects an alternate cache root.

Al

Mon, 01 Jan 0001 00:00:00 +0000

AL is a command runner that prepares credentials and environment variables through plugins, runs your command, and cleans up afterward. Its Bazel rules package commands together with the configuration and plugins they need.

Features

Plugin-based credential and environment preparation around any command
Bazel rules that package a command with its configuration and plugins
A source-keyed executable cache for running declared tools

Ansible

Mon, 01 Jan 0001 00:00:00 +0000

ansible_lint runs ansible-lint from Bazel-managed Python dependencies. A Go test runner exposes the CLI binaries under their hyphenated names, configures writable Ansible paths, and invokes the linter against workspace-relative sources.

Molecule is not integrated yet. The likely path is to add Molecule to these Python requirements and invoke it through a Bazel-native Go runner, but practical scenarios require choosing and provisioning a Molecule driver before any scenarios can run.

Bazel shell worker

Mon, 01 Jan 0001 00:00:00 +0000

Blender

Mon, 01 Jan 0001 00:00:00 +0000

Bzl

Mon, 01 Jan 0001 00:00:00 +0000

Bzlenv

Mon, 01 Jan 0001 00:00:00 +0000

Rules to create a bazel environment which functions similar to venv

Features

Adds bazel-built tools to ${PATH}
Exports .env

Usage

Create env and activate:

. "$(bazel run //tools/bzlenv)"

Activate existing env:

. .bzlenv/bin/activate

Deactivate env:

bzlenv_deactivate

com_github_bazelbuild_bazel_protobuf

Mon, 01 Jan 0001 00:00:00 +0000

Dart Sass

Mon, 01 Jan 0001 00:00:00 +0000

Dart Sass binary toolchain, used by Hugo for toCSS "dartsass" builds.

Drawio

Mon, 01 Jan 0001 00:00:00 +0000

Reproducible SVGs

drawio_svg in defs.bzl renders named pages from a .drawio file with the pinned Drawio web exporter and the existing pinned Chrome-for-Testing browser. The extraction action unpacks the web application from the Drawio AppImage; rendering uses a small Puppeteer bridge for its export messages. Neither action uses a host display server or accesses the network. JavaScript keeps this adapter close to Drawio’s browser API and the existing Puppeteer dependency.

File installer

Mon, 01 Jan 0001 00:00:00 +0000

Git

Mon, 01 Jan 0001 00:00:00 +0000

Go

Mon, 01 Jan 0001 00:00:00 +0000

Gzip

Mon, 01 Jan 0001 00:00:00 +0000

Helm

Mon, 01 Jan 0001 00:00:00 +0000

Http server

Mon, 01 Jan 0001 00:00:00 +0000

Hugo

Mon, 01 Jan 0001 00:00:00 +0000

Hugo binary toolchain for the repository. Build rules live in rules_hugo.

Install file

Mon, 01 Jan 0001 00:00:00 +0000

Leetcode downloader

Mon, 01 Jan 0001 00:00:00 +0000

This project exports LeetCode submissions and generates documentation from submission files using a CLI and Bazel rules. A Tampermonkey script provides a browser-based download path; direct CLI downloads are currently blocked by LeetCode bot protection.

Features

CLI and bzl code to generate submission docs
Tampermonkey script to download submissions
CLI to download submissions (Doesn’t work because of bot protection)

Usage

Generate submission from a submission file

bazel run //projects/leetcode_downloader -- \
    --submissions-file "${PWD}/out/submissions.json" \
    --root-dir "${PWD}" \
    generate

Help

Usage of flags:
  -base_url string
    	 (default "https://leetcode.com")
  -cookie string

  -limit uint
    	 (default 20)
  -offset uint

  -root-dir string
    	 (default "${PWD}")
  -submissions-file string

Leetcode downloader

Mon, 01 Jan 0001 00:00:00 +0000

Tools for exporting your LeetCode submissions and turning them into documentation. This work is still in progress.

Status

In progress. The export and documentation tooling is not yet complete.

Lua

Mon, 01 Jan 0001 00:00:00 +0000

Make install

Mon, 01 Jan 0001 00:00:00 +0000

Md

Mon, 01 Jan 0001 00:00:00 +0000

Minisign

Mon, 01 Jan 0001 00:00:00 +0000

Oras

Mon, 01 Jan 0001 00:00:00 +0000

Patch

Mon, 01 Jan 0001 00:00:00 +0000

Pkg

Mon, 01 Jan 0001 00:00:00 +0000

Print deps

Mon, 01 Jan 0001 00:00:00 +0000

Proto

Mon, 01 Jan 0001 00:00:00 +0000

Py

Mon, 01 Jan 0001 00:00:00 +0000

The repository Python dependency lock remains in root requirements.txt, next to pyproject.toml. Update it with //tools/py:requirements.update and validate it with //tools/py:requirements.test; the root labels remain compatibility entry points. These upstream pip-tools workflows require network access to resolve and validate package versions and run outside the action sandbox.

Qt

Mon, 01 Jan 0001 00:00:00 +0000

Hermetic Qt

The module configuration downloads SHA-256-pinned Qt 6.8.3 distributions via rules_qt and registers its build tools. Bazel builds do not require Qt under /opt or another host installation.

Readme tree

Mon, 01 Jan 0001 00:00:00 +0000

Example

bazel run tools/readme_tree -- parse -g -C "${PWD}" .

Release

Mon, 01 Jan 0001 00:00:00 +0000

Replace section

Mon, 01 Jan 0001 00:00:00 +0000

Repo map

Mon, 01 Jan 0001 00:00:00 +0000

Resolved toolchain

Mon, 01 Jan 0001 00:00:00 +0000

Rfc

Mon, 01 Jan 0001 00:00:00 +0000

Rules binary toolchain

Mon, 01 Jan 0001 00:00:00 +0000

rules_binary_toolchain creates Bazel toolchains and runnable targets for packaged executable binaries. Archive entries can include runtime files, which the generated binary targets expose through Bazel runfiles.

Rules docs

Mon, 01 Jan 0001 00:00:00 +0000

rules_docs packages Markdown documentation under a common archive prefix.

Documentation rule

Add the module dependency:

bazel_dep(name = "rules_docs", version = "<VERSION>")

Then declare the package documentation. srcs defaults to glob(["*.md"]); visibility is optional.

load("@rules_docs//docs:defs.bzl", "docs_filegroup")

docs_filegroup(
    name = "docs",
    deps = ["child"],
)

Relative dependency names without a colon are normalized to the child package’s docs target. prefix defaults to the current package beneath content/docs/.

Files are packaged at their basename by default. When a package’s sources span subdirectories that hold identically named files, set preserve_paths = True so each source keeps its package-relative path and the destinations stay distinct.

Rules Hugo

Mon, 01 Jan 0001 00:00:00 +0000

rules_hugo builds Hugo sites with a registered Hugo toolchain. It keeps the site archive in the target configuration and the Hugo binary in the execution configuration so site sources are not rebuilt for the execution platform.

al_hugo_site wraps a site source archive and its PostCSS tooling. al_hugo_run_binary builds the site with the registered Hugo toolchain and al_hugo_binary exposes a runnable Hugo command for a site. The optional al_hugo_worker rule runs the build through a persistent worker.

Rules Promptfoo

Mon, 01 Jan 0001 00:00:00 +0000

rules_promptfoo runs repository skills through a pinned Promptfoo CLI. It keeps dependency resolution reproducible in Bazel while deliberately running model calls only at test runtime.

Setup

Add the module and its skill-provider dependency:

bazel_dep(name = "rules_promptfoo", version = "<VERSION>")
bazel_dep(name = "rules_skills", version = "<VERSION>")

The development checkout uses sibling local_path_override declarations. Published releases must replace those local overrides with registry versions.

Evaluate a skill

load("@rules_promptfoo//promptfoo:defs.bzl", "promptfoo_test")

promptfoo_test(
    name = "answer_question_eval",
    config = "promptfooconfig.yaml",
    skills = ["//projects/agents/skills/answer-question:skill"],
    env_inherit = [
        "CODEX_HOME",
        "CODEX_PATH_OVERRIDE",
    ],
    reuse_codex_login = True,
)

The runner physically copies each selected SkillInfo.files_by_path bundle to an isolated Bazel test-temporary workspace/.agents/skills/<name>/ tree. Point the Codex SDK provider at the exported workspace and, when using a compatible host Codex executable, at the exported executable path:

Rules skill

Mon, 01 Jan 0001 00:00:00 +0000

rules_skills packages all files belonging to a Codex skill and validates its instructions and optional OpenAI metadata with a hermetic Bazel aspect.

Getting started

Add the module and register the validation aspect:

bazel_dep(name = "rules_skills", version = "<VERSION>")

build --aspects @rules_skills//skill:defs.bzl%skill_validation_aspect
build --output_groups=+skill_validation

Declare one library in the skill’s named, non-root package:

load("@rules_skills//skill:defs.bzl", "skill_library")

skill_library(
    name = "skill",
    srcs = glob(
        ["**"],
        exclude = [
            "BUILD.bazel",
            "BUILD",
            "evals/**",
        ],
    ),
)

The package’s final path segment is the skill name, so a skill_library cannot be declared in a repository root package. Move a root-level skill into a named subpackage before declaring it.

Rules template

Mon, 01 Jan 0001 00:00:00 +0000

rules_template provides Bazel rules and a Go command for rendering template files. A registered toolchain supplies the templating executable to build actions.

Getting started

MODULE.bazel:

bazel_dep(name = "rules_template", version = "<VERSION>")
register_toolchains("@rules_template//main/bzl:all")

BUILD.bazel:

Run tool

Mon, 01 Jan 0001 00:00:00 +0000

Sh

Mon, 01 Jan 0001 00:00:00 +0000

Toml

Mon, 01 Jan 0001 00:00:00 +0000

Transitive sources

Mon, 01 Jan 0001 00:00:00 +0000

Trufflehog

Mon, 01 Jan 0001 00:00:00 +0000

The normal //tools/trufflehog:repo_test scans the history reachable from the checked-out HEAD and skips unrelated local refs. Run the manual //tools/trufflehog:repo_all_refs_test target explicitly when an audit must include every local Git ref, such as T3 checkpoint refs from other worktrees.

Txt

Mon, 01 Jan 0001 00:00:00 +0000

Vial

Mon, 01 Jan 0001 00:00:00 +0000

Bzl on Alwaldend

Agents

Repository agent skills

Start here

Ownership boundaries

Skill packaging and discovery

Agents

Features

Al

Al

Features

Ansible

Bazel shell worker

Blender

Links

Bzl

Bzlenv

Features

Usage

com_github_bazelbuild_bazel_protobuf

Dart Sass

Drawio

Links

Reproducible SVGs

File installer

Git

Go

Gzip

Helm

Links

Http server

Hugo

Install file

Leetcode downloader

Links

Features

Usage

Generate submission from a submission file

Help

Leetcode downloader

Status

Lua

Make install

Md

Minisign

Oras

Links

Patch

Pkg

Print deps

Proto

Py

Qt

Links

Hermetic Qt

Readme tree

Example

Release

Replace section

Repo map

Resolved toolchain

Links

Rfc

Links

Rules binary toolchain

Rules docs

Documentation rule

Rules Hugo

Rules Promptfoo

Setup

Evaluate a skill

Rules skill

Getting started

Rules template

Getting started

Run tool

Sh

Toml

Transitive sources

Trufflehog