Skip to content

Pixel-CLI/pixel / .agents/skills/docker-setup-smoke

docker-setup-smoke

Verified

Replay Pixel's new-user setup in Docker without an LLM — install through a release archive, install.sh, the Homebrew tap, or sources from main, a PR head or a pinned commit; then personal Claude/Codex/pi settings kept, idempotent reinstall, first pixel audit, doctor and --fix, project install, disabled classify and uninstall; with --agents, Claude Code, Codex and pi sessions against a scripted fake model show whether each receives the Pixel prompt, runs pixel and routes grep. Use for Linux setup smoke checks, not macOS behavior or real model inference.

FileKindSize
SKILL.mdskill md10.7 KB
scripts/Dockerfileother1.8 KB
scripts/agents.shscript7.6 KB
scripts/bootstrap.shscript1.0 KB
scripts/brew.shscript2.6 KB
scripts/checks.shscript11.8 KB
scripts/fake-llm.pyscript8.8 KB
scripts/installer.shscript934 B
scripts/run.shscript5.6 KB
scripts/source.shscript1.0 KB
scripts/test-runner.pyscript11.1 KB

scripts/brew.sh

View on GitHub
#!/bin/sh
# SPDX-FileCopyrightText: The Pixel contributors
# SPDX-License-Identifier: MIT

set -eu
# Homebrew's prefix belongs to linuxbrew and is not readable by other users,
# so that user runs both the formula install and the checks, as on a Mac
# where the person who installed Homebrew runs pixel.
brew=/home/linuxbrew/.linuxbrew/bin/brew
chown linuxbrew:linuxbrew /evidence
su linuxbrew -c "$brew install LivioGama/tap/pixel" > /evidence/brew-install.log 2>&1 \
    || { cat /evidence/brew-install.log; exit 1; }
tail -3 /evidence/brew-install.log
su linuxbrew -c "$brew deps --installed LivioGama/tap/pixel" > /evidence/brew-deps.txt
su linuxbrew -c "$brew info --json=v2 LivioGama/tap/pixel" > /evidence/brew-info.json
# On a host whose glibc or libstdc++ is older than Homebrew's CI, Homebrew
# gives every formula, bottled or not, an implicit gcc and glibc: the
# formula cannot opt out. A control formula with no dependency measures what
# this host adds to any formula; only a dependency beyond it is pixel's.
su linuxbrew -c "$brew ruby -e 'puts \"system glibc: #{OS::Linux::Glibc.system_version}\",
    \"ci glibc: #{OS::LINUX_GLIBC_CI_VERSION}\",
    \"needs libc formula: #{DevelopmentTools.needs_libc_formula?}\",
    \"needs compiler formula: #{DevelopmentTools.needs_compiler_formula?}\"'" \
    2>/dev/null | grep -E '^(system|ci|needs) ' > /evidence/brew-host.txt
cat /evidence/brew-host.txt
su linuxbrew -c "$brew tap-new local/smoke --no-git" > /dev/null
cat > /tmp/control.rb <<'RB'
class Control < Formula
  desc "Formula without dependencies: what the host alone adds to any formula"
  homepage "https://example.com"
  url "https://example.com/control-1.tar.gz"
  sha256 "0000000000000000000000000000000000000000000000000000000000000000"
  def install; end
end
RB
su linuxbrew -c "cp /tmp/control.rb \"\$($brew --repository)/Library/Taps/local/homebrew-smoke/Formula/\""
su linuxbrew -c "$brew deps local/smoke/control" | sort -u > /evidence/brew-host-deps.txt
own=$(sort -u /evidence/brew-deps.txt | comm -23 - /evidence/brew-host-deps.txt)
if [ -n "$own" ]; then
    echo "FAIL the formula pulled dependencies of its own: $own" >&2
    exit 1
fi
if [ -s /evidence/brew-deps.txt ]; then
    echo "NOTE Homebrew gives this host's toolchain to every formula, pixel's $(wc -l < /evidence/brew-deps.txt) dependencies included (brew-host.txt, brew-host-deps.txt)"
fi
echo 'PASS the Homebrew formula pulls no dependency of its own'
dir=/home/linuxbrew/.linuxbrew/bin
"$dir/pixel" --version > /evidence/binary-version.txt
cat /evidence/binary-version.txt
printf 'PIXEL_BIN_DIR=%s\nPIXEL_OWNS_BINARY=0\n' "$dir" > /etc/pixel-smoke.env
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 466kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 192kUpdated Claude CodeCodexVerifiedInstall