agentleFS
BlackBeltTechnologyBlackBeltTechnology/pi-agent-dashboard/qa/AGENTS.md

pi-agent-dashboard / qa

AGENTS.md349 starsChanged 23 days agoMITView on GitHub

Files in this directory. One row per file. Non-source area (migrated from docs/file-index-skills-misc.md; source of truth now here). Subdir files owned by their own AGENTS.md (fixtures/, packer/, scripts/, tests/). See change: migrate-file-index-to-agents-tree. See change: fold-oversized-agents-directories.

  • Reads credentials

The file

Files
AGENTS.md

DOX — qa

Files in this directory. One row per file. Non-source area (migrated from docs/file-index-skills-misc.md; source of truth now here). Subdir files owned by their own AGENTS.md (fixtures/, packer/, scripts/, tests/). See change: migrate-file-index-to-agents-tree. See change: fold-oversized-agents-directories.

FilePurpose
.gitignoreIgnores VM build artifacts: output/ images, iso/ downloads, packer_cache/, clones/ working dirs, crash.log.
MakefileBuild/test/manual/clean targets for QA VMs. Targets: build-{linux-x86,linux-arm,windows,macos-x86,macos-arm,-all}, test-{linux-x86,linux-arm,windows,macos-x86,macos-arm,-all}, manual-<target>, clean, test-windows-remote-nsis SETUP=<Setup.exe>. Preflight check_placeholders / check_user_data reject unfilled REPLACE_WITH_ var files. Calls scripts/run-test.sh, scripts/vm-clone.sh, scripts/vm-destroy.sh. SSH user qa, key ~/.ssh/qa_vm_key, VMRUN path hard-coded to VMware Fusion.
README.mdFull QA setup + usage docs. Prereqs (Packer, VMware Fusion, ssh-keygen -t ed25519 -f ~/.ssh/qa_vm_key), ISO download table, hardware split (Intel Mac x86 builder, M1 Mac ARM builder), quick start (make build-/test-/manual-), manual macOS VM install steps (vmware-vmx builder, no unattended install), test coverage list (install, server start, WS, terminal, git ops, Electron zip V2 bootstrap Windows, NSIS Setup.exe smoke Windows, Electron real-launch Linux xvfb-run), directory structure map.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.