paperclip dev

Other Community

Skill notes

Quick Command Reference

These are the most common commands. For full option tables and details, see doc/DEVELOPING.md. Task · Command Start server (first time or normal) · npx paperclipai run Dev mode with hot reload · pnpm dev Stop dev server · pnpm dev:stop

Pulling from Master

If schema changes landed, also run pnpm db:generate && pnpm db:migrate.

Worktrees

Paperclip worktrees combine git worktrees with isolated Paperclip instances — each gets its own database, server port, and environment seeded from the primary instance. MANDATORY: Before creating or managing worktrees, you MUST read the "Worktree-local Instances" and "Worktree CLI Reference" sections in doc/DEVELOPING.md. That is the canonical reference for all worktree commands, their options, seed modes, and environment variables.

When to Use Worktrees

Starting a feature branch that needs its own Paperclip environment Running parallel agent work without cross-contaminating the primary instance Testing Paperclip changes in isolation before merging

Command Overview

The CLI has two tiers (see doc/DEVELOPING.md for full option tables): Command · Purpose worktree:make <name> · Create worktree + isolated instance in one step worktree:list · List worktrees and their Paperclip status worktree:merge-history · Preview/import issue history between worktrees

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@paperclipai · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Read the canonical files

You MUST read all three of these files before creating a PR: `.github/PULL_REQUEST_TEMPLATE.md` — the required PR body structure `CONTRIBUTING.md` — contribution conventions, PR requirements, and thinking-path examples `.github/workflows/pr.yml` — CI checks that gate merge

02
Step 2 — Validate your PR body against this checklist

After reading the template, verify your `--body` includes every one of these sections (names must match exactly): [ ] `## Thinking Path` — blockquote style, 5-8 reasoning steps [ ] `## What Changed` — bullet list of concrete changes [ ] `## Verification` — how a reviewer confirms this works [ ] `## Risks` — what could go wrong

03
Step 3 — Create the PR

Only after completing Steps 1 and 2, run `gh pr create`. Use the template contents as the structure for `--body` — do not write a freeform summary.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.