An author-directed editorial engine for your writing projects.
Bring your take — an idea or a rough draft. Pysar helps you shape it into a
piece you trust, without forcing pipeline jargon on you and without posting
on your behalf. It runs as a CLI plus an MCP server and a set of ps-*
skills for Claude Code, Cursor, and Codex.
User guide: start at docs/index.md (install → init → pipeline → MCP/skills → export → troubleshooting).
curl -fsSL https://getpysar.com/install.sh | bash
pysar init # Claude Code (default)
pysar init --cursor # Cursor (project scaffold; install the Pysar Cursor plugin for /ps skills)
pysar init --codex # Codex CLI / AppCursor plugin package (Marketplace / Install in Cursor / local dogfood):
plugins/pysar.
go build ./cmd/pysar # build
go install ./cmd/pysar # build + install to $(go env GOPATH)/bin
go test ./... # run testsPublic site (getpysar.com) lives under site/ — Next.js static
export, separate from the Go tool. See site/README.md.
Project governance, decision history, and contribution discipline live in
CLAUDE.md and the .haft/ directory (this project uses
haft for structured decision recording).
Releases are built and published by CI (.github/workflows/release.yml)
via GoReleaser whenever a v* tag is pushed. Tests
must pass before a build runs — see .goreleaser.yaml
for the build matrix.