Commands
Run pf list for the list that applies in the current directory, and pf help for options.
| Command | What it does |
|---|---|
pf | Menu: this repo’s own commands first (run, build, deploy, …), then pf’s tools including the agent; the fallback menu outside a repo |
pf list | The same list, static (for scripts and agents) |
pf dev, build, test, lint, install | Resolved per repo. --dry-run prints, --pick chooses when several exist, -- <args> passes args on. See Run, build and docs. pf install [local|<to>] (pf i, pf il) runs the repo’s install:local / install:<to> target, else installs dependencies |
pf doc (pf docs) | Run the docs site (Nextra, Docusaurus, VitePress, Starlight, mkdocs, Sphinx, mdBook, Hugo) |
pf ver [list|bump|init|sync] | Major.minor versioning with the bundled /ver CLI. See Versioning |
pf deploy (pf d) | Deploy: staging if configured, else production, else the repo’s own deploy, else the publish of a repo that only publishes. Optional commit message. See Deploy and publish |
pf deploy staging | Deploy to staging. --dry-run, --yes. See Deploy and publish |
pf deploy production | Only a deploy:production script or pulpfixer.json entry; always confirms |
pf publish staging | Run the repo’s publish:cellars script (else its staging deploy); always confirms |
pf tools [name] [args] | List and run the repo’s own ./a tools. See Tools and repo setup |
pf git [push | status | backup | primary] | Git helpers: a menu in a terminal, including adding a backup remote. pf git push (pf gp) pushes to the primary remote, then the backup remotes. See Tools and repo setup |
pf actions [--all] [--json] | The repo’s actions (run, deploy, publish, docs, custom commands) with an icon and a featured flag: the buttons of the Background Tone card. pf actions feature|unfeature <id...> chooses them. See Tools and repo setup |
pf init | Write pulpfixer.json for this repo from what was detected |
pf repo | Hook pf’s tools into this repo (link, pnpm commands, versioning, background tone logo and extension, .pf/ in .gitignore, deploy), or update them |
pf agent [prompt] | Open the coding agent (Claude Code, Codex or Cursor). See Agent |
pf troubleshoot [prompt] (pf t) | Find out what is wrong with this repo’s deployment on AWS: pf reads how it deploys, links the AWS profile, then starts the agent with scoped AWS access. See Troubleshoot |
pf profile [...] | Project profiles: which AWS account a repo uses and what the agent may read there |
pf aws [grants|revoke] | AWS access the agent was granted: list it, end it |
pf mcp | Serve pf’s tools to any MCP client over stdio |
pf skill [name] | Pick and run an agent skill. available, install, update, remove manage registry skills |
pf plugin [...] | Administer plugins from the registry. See Plugins |
pf s3 <file...>, pf dl [name] | AWS plugin: upload to and download from a shared exchange bucket |
pf sys [list|diff|apply|capture] | System plugin: apply the standard Cursor setup (extensions and settings) from a preset. See System plugin |
pf otp, pf yk | YubiKey plugin: OATH codes and a security audit |
pf host ... | pf on EC2 instances. See Host mode |
pf art [list|show <name>] | List the pictures pf prints and which commands show them |
pf setup, update, uninstall, doctor | Machine tooling |
pf about, pf help, pf --version | Info |
Commands that run something support --dry-run. Short names such as pf r and pf ds are listed under Shortcuts.
Machine tooling
| Command | Notes |
|---|---|
pf setup | Registry, completions and legacy cleanup. --dry-run, --yes, --no-completions |
pf update (pf u) | Update pf, installed plugins, the suite extensions installed in Cursor (Background Tone), the ver and pnpm skills and registry skills, then this repo’s copies of their helpers. --check, --yes, --dry-run |
pf uninstall | Remove pf. --purge, --no-package, --no-shell, --yes, --dry-run |
pf doctor | Check this machine and repo for problems. --offline |
pf versions (pf vs) | List the versions of everything pulpfixer-related installed here: pf, the bundled kit and plugins, registry plugins, skills, presets and the suite extensions in Cursor. --json. No network. See Versions |
Versions
pf versions (short: pf vs) reads what is on this machine and prints it in sections:
| Section | What it lists |
|---|---|
| pf | The running version, where it is installed, and the Node version |
| pf on PATH | Every pf on PATH, in order. A legacy (1.x) one or a shadowed one is flagged |
| Bundled with pf | @pulpfixer/kit and the built-in plugins, at the versions this pf ships |
| Plugins | Plugins installed from the registry (~/.pf/plugins), and whether each loaded |
| Skills | Registry skills in ~/.pf/skills and the agent folders (~/.cursor, ~/.claude, ~/.agents), what else sits in ~/.pf/skills, and the skills bundled with pf, with the version from the package or from metadata.version in SKILL.md |
| Presets | The presets pf sys apply fetched into ~/.pf/sys/presets |
| Cursor extensions | The suite extensions (Background Tone), at the version Cursor has installed, with a hint when a newer one was fetched |
Warnings are yellow and problems red (a plugin that failed to load, an unusable preset). pf versions --json prints the same data for scripts. It never uses the network; pf update --check compares with the registry. For the versions of a repo’s own modules, use pf ver.
Last updated on