Menu
Use when preparing Wendy repo commits, GitHub PRs, review-thread cleanup, or CI fixes, especially for wendy-agent Go changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | wendy-pr-workflow |
| description | Use when preparing Wendy repo commits, GitHub PRs, review-thread cleanup, or CI fixes, especially for wendy-agent Go changes. |
Use this for Wendy Labs PR, CI, and review cleanup work.
For wendy-agent Go changes:
cd /Users/maximilianalexander/wendylabsinc/wendy-agent/go
gofmt -w <changed-go-files>
go test ./internal/cli/commands ./internal/agent/services
git diff --check
Adjust packages to match touched files. When CI uses race-sensitive checks, match the workflow flags locally instead of relying on plain go test.
When resolving review conversations, use GraphQL reviewThreads so thread state is accurate. After patching and pushing, resolve only the addressed threads, then re-query to confirm isResolved.
Useful shape:
gh api graphql -f owner=wendylabsinc -f repo=wendy-agent -F number=<pr-number> -f query='
query($owner:String!, $repo:String!, $number:Int!) {
repository(owner:$owner, name:$repo) {
pullRequest(number:$number) {
reviewThreads(first:100) {
nodes {
id
isResolved
isOutdated
path
line
comments(first:10) { nodes { url body author { login } } }
}
}
}
}
}'
Resolve an addressed thread:
gh api graphql -f threadId=<thread-id> -f query='
mutation($threadId:ID!) {
resolveReviewThread(input:{threadId:$threadId}) {
thread { id isResolved }
}
}'
main, inspect divergence first so unrelated local commits are not bundled.Use when creating, validating, or repairing a Wendy project scaffold, adapting Wendy templates, `wendy.json`, JSON schema setup, or project entitlements with `wendy init`, `wendy json`, or `wendy project entitlements`.
Use when creating a Wendy app from an existing Wendy template or sample, especially when the user names an app archetype such as realsense-camera, camera-feed, camera-feed-yolo, voice-assistant, audio, fullstack, simple-api, or asks to create a Wendy app in a new directory.
Use when a developer needs to install, verify, or repair the Wendy CLI before using `wendy run`, `wendy discover`, or device workflows.
Use when a developer or coding agent needs Wendy CLI-native device operations: discover devices, set defaults, inspect device version/system/hardware/WiFi state, update the agent, or gather evidence before SSH/debugging.
Use when configuring, verifying, or explaining the Wendy CLI MCP server for AI assistants with `wendy mcp setup` or `wendy mcp serve`, especially Claude Code, Claude Desktop, Codex, or device-tool access.
Use when debugging WendyOS, Jetson, Raspberry Pi, USB-C host mode, containerd, GPU/audio/video entitlements, or a `wendy run` issue that only appears on a live device.