agentleFS
pandemicsynpandemicsyn/neondeck/skills/neondeck-handoff/SKILL.md

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.

  • In this repository2 other files it gives its agents.

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
  1. Very specific:

    Use this skill when you are an external local coding agent working in a repository that the user tracks with Neondeck.

    line 8
  2. Distinctive:

    Before using it, check that the CLI exists:

    line 10
  3. Very specific:

    If neondeck is missing, do nothing and do not tell the user to install it unless they asked about Neondeck.

    line 16
  4. Very specific:

    When you push or update a pull request for a Neondeck-tracked repo, run:

    line 20
  5. Very specific:

    Use a stable lowercase source name such as claude-code, codex, kilo, or ci:github-actions.

    line 26
  6. Very specific:

    If ok is false, read message, requires, and errors.

    line 41
  7. Very specific:

    Add --review only when the user or repo policy wants Neon to queue bounded PR review assistance.

    line 43
  8. Distinctive:

    Leave a bounded note:

    line 47
  9. Very specific:

    Do not use handoff commands for execution, approvals, pushes, provider changes, or remote ingest.

    line 64

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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>&1

If 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>" --json

Use 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 --json

Levels 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> --json

Do not use handoff commands for execution, approvals, pushes, provider changes, or remote ingest. They are only for attributed local registration into Neondeck.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.