Bugs & Requests
CLI reference
Every `shipeasy feedback` command for triaging bugs and feature requests.
npm install -g @shipeasy/cli
shipeasy loginfeedback bugs
shipeasy feedback bugs <subcommand>| Subcommand | What it does |
|---|---|
list | List bug reports |
get <id> | Show a bug by id (or id prefix) |
create <title> | File a bug report |
update <id> | Update status / priority / fields |
delete <id> | Delete a bug |
link-pr <id> <pr-number> | Cross-link a GitHub PR onto the bug card |
shipeasy feedback bugs list --json | jq '.[] | select(.status=="open")'
# create requires --steps, --actual, --expected (the bug-report contract)
shipeasy feedback bugs create "Checkout button overlaps footer" \
--steps "1. Add item to cart. 2. Resize browser below 1024px." \
--actual "Button is hidden behind sticky footer" \
--expected "Button remains visible above the footer" \
--page-url https://example.com/checkout
shipeasy feedback bugs delete a1b2c3dfeedback features
shipeasy feedback features <subcommand>| Subcommand | What it does |
|---|---|
list | List feature requests |
get <id> | Show a feature request |
create <title> | File a feature request |
update <id> | Update status / importance / fields |
delete <id> | Delete a feature request |
link-pr <id> <pr-number> | Cross-link a GitHub PR onto the request card |
shipeasy feedback features list --json
# create requires --description and --use-case
shipeasy feedback features create "Dark mode dashboard" \
--description "Add a system-prefers dark theme to the dashboard chrome" \
--use-case "I'm reviewing experiments at night and the white bleeds light" \
--importance importantSee also
- API reference — same surface over HTTP
- MCP reference — same surface as MCP tools for AI agents