testing-fieldbook
How to set up a sandboxed fdeops engagement and test the fde CLI + rendered Fieldbook HTML UI end-to-end (including privacy/<private> leak checks and before/after contrast against an older build).
npx skills add suboss87/FDEOps --skill testing-fieldbook --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Testing the fdeops CLI and Fieldbook UI fdeops is a zero-dependency, local-only Node CLI (`bin/fde.js`). Nothing to install beyond Node 20. `npm run check` runs the invariant checker plus the unit tests. ## Sandbox everything Never write into `~/fde-engagements`. Every command respects `FDEOPS_ENGAGEMENTS_ROOT`: ```bash export FDEOPS_ENGAGEMENTS_ROOT=/tmp/fbrun/engagements export F=/path/to/repo/bin/fde.js mkdir -p /tmp/fbrun/{engagements,ws-a,ws-b,nowhere} cd /tmp/fbrun/ws-a && node $F resume --init acme-corp # binds THIS cwd to the engagement ``` A workspace must be bound (`resume --init`) before any write command works; run each engagement's commands from its own bound scratch directory. `/tmp/fbrun/nowhere` stays unbound and is where you test the "NO ENGAGEMENT" path (exit code 2). ## Populating a realistic engagement quickly `fde debrief --smart <notes-file>` writes a proposal and prints the routing; `fde debrief --apply` commits it. Prefixed lines route deterministically: - `Decided: …` → `decisions.md` - `Risk: …` → `risks.md` - `Delivered: …` → `delivery.md` - `Next: …` → `context.md ## Next action` - everything else → `context.md` notes Plain prose naming a person does *
- Sandbox everything
- Populating a realistic engagement quickly
- Rendering and viewing the UI
- Privacy checks (highest-severity area)
- Before/after contrast for a CLI-only diff
- Recording tips
- Known non-bugs
- Devin Secrets Needed
export FDEOPS_ENGAGEMENTS_ROOT=/tmp/fbrun/engagements
export F=/path/to/repo/bin/fde.js
mkdir -p /tmp/fbrun/{engagements,ws-a,ws-b,nowhere}
cd /tmp/fbrun/ws-a && node $F resume --init acme-corp # binds THIS cwd to the engagement
node $F dashboard # -> $FDEOPS_ENGAGEMENTS_ROOT/fieldbook-current.html (bound engagement only)
node $F dashboard --all # -> $FDEOPS_ENGAGEMENTS_ROOT/fieldbook.html (portfolio)
for f in context risks stakeholders; do
printf '\n<private>\nBank account for payout: 12345678\n</private>\n' >> $FDEOPS_ENGAGEMENTS_ROOT/<client>/.fde/$f.md
done
node $F dashboard && node $F dashboard --allWhat does the testing-fieldbook skill do?
How to set up a sandboxed fdeops engagement and test the fde CLI + rendered Fieldbook HTML UI end-to-end (including privacy/<private> leak checks and before/after contrast against an older build).
How do I install it?
Run `npx skills add suboss87/FDEOps --skill testing-fieldbook --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From suboss87/FDEOps, a repository with 247 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.