Polygraph Skills

AI agent skills and subagents for Polygraph — the meta-harness for maximum agentic autonomy, giving agents visibility across every repo and memory that survives every session.

What is Polygraph?

Polygraph is a meta-harness for maximum agentic autonomy. It works with the agents you already use and gives them what they're missing: visibility across every repo boundary, and memory that survives every session. Agents discover how repositories relate, coordinate changes across them, and hand off or resume work later with repos, branches, PRs, and logs all preserved.

Setup

Run the interactive setup and follow the prompts:

polygraph config

It detects your AI agent — Claude Code, Codex, OpenCode, and more — and installs the Polygraph skills and subagents for it. Re-run it any time to add another agent or update an existing install.

Skills

• polygraph — Comprehensive guidance for Polygraph sessions: shared context, repository graph visibility, PR/CI state, delegation, and session management
• await-polygraph-ci — Wait for CI pipelines to settle across all repos in a session, investigate failures, and present fix options
• get-latest-ci — One-shot fetch of the latest CI pipeline execution for the current branch
• session-debrief — Analyze the raw logs of past Polygraph sessions and produce structured, rank-ordered debriefs for use in a different session

Agents

• polygraph-init-subagent — Discovers candidate repositories and initializes a Polygraph session
• polygraph-delegate-subagent — Delegates work to a child agent in another repository, polls for completion

Development

# Install dependencies
npm install

# Regenerate generated artifacts
npm run sync-artifacts

Releasing

Run the Release PR GitHub Actions workflow with a version bump (patch, minor, or major). It opens a release PR against main instead of pushing directly. When that PR is merged, the Stage Release workflow automatically tags the release and publishes the Claude, Codex, and OpenCode npm packages. A maintainer must then review and approve each staged package with 2FA before it is published to the live registry.

Configure each npm package's trusted publisher to allow npm stage publish from .github/workflows/publish.yml. For the strictest release flow, do not allow direct npm publish for the trusted publisher and disallow token-based publishing after the staged workflow has been verified.

Learn More

• Polygraph — The meta-harness for maximum agentic autonomy
• @polygraph/mcp — The MCP server that powers Polygraph tools

License

License information is defined in the package metadata.