agentleFS
IvanWng97IvanWng97/pixtuoid/.claude/skills/add-source/SKILL.md

add-source

Skill551 starsChanged 31 days agoMITView on GitHub

Wires a new agent CLI into pixtuoid so its sessions become office sprites, from the upstream facts through a reviewed PR. Use when adding support for a CLI, adding a source for a tool, or integrating a coding agent, in a maintainer's session or a contributor's fork. Covers the cross-crate checklist, including what a diff-scoped edit silently misses: the site manifest, the per-source badge hue, the home-dir fn and the integration goldens a `--lib` run never builds.

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

add-source

Copy this list into your plan and work it in order, fixing and rerunning each check until it passes.

  • Upstream facts. Answer the checklist's step 1 before any code, from the latest release's source. Its questions have no test, so a wrong answer ships green.
  • The rest of that checklist, with the test steps in tests/AGENTS.md.
  • just test, never --lib alone. The sources --json golden (cli_json) and the wire_to_pixels matrix are integration binaries a --lib run skips: kimi's PR (#692) passed --lib and a multi-lens review with both red.
  • just gen-contract, only if the --json/SourceStatus/OutcomeRow shape changed; adding a row doesn't change it.
  • The must-run: just hermetic <source>, or a live run for a NOT_HERMETIC source. Either way the real CLI, never a capture rig's flags.
  • local-review, always: a fork's PR gets no CI review, so this is its only one. Fold what it finds into one commit.
  • The PR body holds step 1's answers and what the merge gate asks of it. CI runs the tests.

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.