Terminal
Terminal/Skill
Plans how to move an existing GitHub App onto Cursor Origin and writes a porting brief, without changing any code.
By Cursor
Works with
npx skills add cursor/plugins --skill port-github-app-to-originRun this inside the app's codebase. The output is a porting brief for the
team plus a Feedback for Cursor section they can send as is
(references/brief.md). This skill plans. It does not write or change code
unless the user asks for that after reading the brief. Follow the
origin-api skill for the docs and the rules to check first. Two more rules:
file:line. Feedback for Cursor says only what the app
needs to do and what Origin lacks for it, in Origin terms, with no file
paths, module names, framework details, or repository names.Record file:line for each item, and note what you looked for but did not
find.
App's installation and repository
listing; app-auth libraries. Read the dependency's docs and list these
calls marked "from <dependency>".A brief needs the whole spec, but openapi.yaml and llms-full.txt are
each several hundred kilobytes, too large to read into context whole. Save
them locally if you can, in a temporary location outside the app's
repository so nothing in the working tree is overwritten or left behind,
then search them and read only the matching part:
x-origin-scopes: in openapi.yaml marks every operation with its
scopes; the operationId sits a line above.x-origin-webhook-events: in openapi.yaml marks every webhook payload
schema with the event slugs that deliver it.### <Endpoint name> and ### <Payload type> headings in llms-full.txt
start the section that spells out that endpoint's or payload's fields as
dotted paths; read from the heading to the next ###.For a single question later, start at llms.txt and fetch just that
section.
/issues/{n}/… (comments,
labels) live under the pull request endpoints on Origin. If the code uses
them on real issues, see "Where GitHub features live on Origin" in
references/brief.md.x-origin-scopes.scopes over the
operations you named. Do not translate the GitHub manifest.event.type carries
the action), needs an extra read (say which operation and how many calls
per event), can be computed from other fields, or is missing. Payloads are
snapshots. A field the REST resource has but the payload lacks needs an
extra read.Every claim about Origin points at something in the saved docs. Every gap has a feedback entry that names its cost. The feedback reveals nothing about the team's internals. The summary names the native-or-mirror question.