neondeck-handoff
Skill8 starsChanged 2 months agoMITView on GitHub
Register completed local agent work with Neondeck so Neon can watch PRs, show notes, and queue bounded review assistance when allowed.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when you are an external local coding agent working in a repository that the user tracks with Neondeck.
- Distinctive: line 10
Before using it, check that the CLI exists:
- Very specific: line 16
If neondeck is missing, do nothing and do not tell the user to install it unless they asked about Neondeck.
- Very specific: line 20
When you push or update a pull request for a Neondeck-tracked repo, run:
- Very specific: line 26
Use a stable lowercase source name such as claude-code, codex, kilo, or ci:github-actions.
- Very specific: line 41
If ok is false, read message, requires, and errors.
- Very specific: line 43
Add --review only when the user or repo policy wants Neon to queue bounded PR review assistance.
- Distinctive: line 47
Leave a bounded note:
- Very specific: line 64
Do not use handoff commands for execution, approvals, pushes, provider changes, or remote ingest.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Neondeck Handoff
Use this skill when you are an external local coding agent working in a repository that the user tracks with Neondeck.
Before using it, check that the CLI exists:
command -v neondeck >/dev/null 2>&1If neondeck is missing, do nothing and do not tell the user to install it unless they asked about Neondeck.
After You Push A PR
When you push or update a pull request for a Neondeck-tracked repo, run:
neondeck register-pr <owner/repo#number> --from <agent-name> --note "<one-line summary>" --jsonUse a stable lowercase source name such as claude-code, codex, kilo, or ci:github-actions. The CLI stores it as attribution such as external:codex unless you already use a ci: or external: prefix.
The JSON contract is:
{
"ok": true,
"action": "handoff_pr_register",
"changed": true,
"id": "owner/repo#123",
"message": "Registered owner/repo#123 from codex.",
"deckUrl": "/"
}If ok is false, read message, requires, and errors. Do not retry in a loop. Duplicate PR registration is safe and returns success.
Add --review only when the user or repo policy wants Neon to queue bounded PR review assistance. It may start a model-backed Flue workflow that reads PR facts and creates local reports/draft comments, but it does not submit a GitHub review.
After Significant Work Without A PR
Leave a bounded note:
neondeck note "Finished local refactor; no PR was pushed." --from <agent-name> --repo <repo-id-or-owner/name> --level ready --jsonLevels are info, ready, and attention. Notes are capped to 4 KiB. Use attention only when the user needs to act.
Release Watching
To watch the default branch or a source PR through release checks:
neondeck watch-release <repo-id-or-owner/name> --from <agent-name> --json
neondeck watch-release <repo-id-or-owner/name> --source-pr <owner/repo#number> --from <agent-name> --jsonDo not use handoff commands for execution, approvals, pushes, provider changes, or remote ingest. They are only for attributed local registration into Neondeck.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

