agentleFS
Sign inStart free
rakaarwakyrakaarwaky/agents-arwaky/skills/code-quality/dogfood/SKILL.md

dogfood

Skill0 starsChanged 4 days agoMITView on GitHub

Exploratory QA for web, terminal/TUI, desktop GUI, and mobile (Android) apps — finds bugs, captures evidence, and produces a structured report across all four target types.

78 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dep-refs, feature-boundary-planner and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • betacatslingSkill

    dep-refs

    Use when needs to inspect TypeScript export references in the z-code workspace, list exports from a file, verify whether an export is unused before deletion, investigate who imports a symbol during refactors, or combine pnpm knip unused-export results with pnpm dep:refs symbol-level reference tracing.

    Also in 5 projects that use this

  • betacatslingSkill

    feature-boundary-planner

    Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation. Use for impact analysis, product-boundary planning, or an implementation handoff grounded in the checked-out source.

    Also in 5 projects that use this

  • lir-navcooSkill

    yuanbao

    Yuanbao (元宝) groups: @mention users, query info/members.

    Also in 18 projects that use this

  • Cartograf666Skill

    architecture-governance

    Bootstrap, document, enforce, and review a project's architecture through layer responsibilities, dependency direction, architecture manifests, legacy baselines, Change Envelopes, cross-layer approval policy, and deterministic architecture checks. Use when starting a project, auditing an existing codebase, planning cross-layer work, preventing architecture erosion, reviewing structural changes, or deciding whether implementation may expand into another layer.

    Also in 5 projects that use this

  • john-data-chenSkill

    touchdesigner-mcp

    Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.

    Also in 7 projects that use this

  • math-incSkill

    minecraft-modpack-server

    Set up a modded Minecraft server from a CurseForge/Modrinth server pack zip. Covers NeoForge/Forge install, Java version, JVM tuning, firewall, LAN config, backups, and launch scripts.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 78 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read only the winning lane's references.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 78 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dogfood — Exploratory QA

Runs one 5-phase pipeline — plan → explore → collect evidence → categorize → report — over any of four target types: web, terminal/tui, desktop, mobile. This file is the lane identification step only; the working method lives in references/hermes/ and references/grok/.

Global Rules

The lane is determined from a physical signal, not by self-identification. Each agent's launcher stamps a fixed attribution env var into every command it runs; the model cannot set these.

if [[ -n "${HERMES_AGENT:-}" ]]; then echo HERMES
elif [[ -n "${GROK_AGENT:-}" ]]; then echo GROK
else echo UNSET; fi
  • HERMES → Hermes lane. Read references/hermes/. Stop.
  • GROK → Grok lane. Read references/grok/. Stop.
  • UNSET → stop and report. Do not guess the lane.

Marker provenance:

  • Hermes re-exports AI_AGENT=hermes-agent and HERMES_AGENT=true on every command.
  • Grok Build runs with GROK_AGENT=1.

Read only the winning lane's references. Do not read the other lane's.

Routing

Hermes lane (Steps 0–3)

StepReferencePurpose
0references/hermes/step-0-plan-and-spawn.mdInfer target type; plan the brief (scope, output dir, acceptance criteria); create the Orca worktree (repo targets) or headless run (mobile); drop /dogfood <target>
1references/hermes/step-1-wait-grok.mdWait for Grok to finish the pipeline; read its report.md
2references/hermes/step-2-verify-and-ship.mdVerify evidence integrity and that the app tree is unmodified; triage summary; deliver the report
3references/hermes/step-3-final-report.mdFinal report to the user (issues by severity, top issues, patterns, report location, worktree teardown)

Grok lane (5-phase pipeline, run by Grok Build)

StepReferencePurpose
Step 0: planreferences/grok/step-0-plan.mdOutput directory layout and target-specific test-plan items for all four types.
Step 1: explore — webreferences/grok/step-1-web.mdbrowser_* toolset, web-specific tips, web issue taxonomy.
Step 1: explore — terminal/TUIreferences/grok/step-1-terminal.mdrun_terminal_command, screen/tmux capture, TUI sizing, signal handling, terminal issue taxonomy.
Step 1: explore — desktopreferences/grok/step-1-desktop.mdcomputer_use (cua-driver), AX-tree capture, drag-and-drop, desktop issue taxonomy.
Step 1: explore — mobilereferences/grok/step-1-mobile.mdadb shell (tap, swipe, type, screencap), logcat, rotation, permission dialogs, mobile issue taxonomy.
Shared QA rulesreferences/grok/shared.mdOutput directory layout, evidence protocol, categorize rules, report requirements, issue taxonomy (severity + universal categories), shared tips for all targets.
Report templatetemplates/dogfood-report-template.mdCopy-source shape of the final report; fill and save to {output_dir}/report.md.

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.

Check your setup, free