An Amp plugin that helps prepare local repositories for future Amp Orbs.
The plugin runs locally. It asks what future Orbs should be able to do, collects additional context, scans the current repository, then injects a setup prompt into the active Amp thread. The agent can then create durable repo files such as .agents/setup, .agents/resume, AGENTS.md, and .agents/skills/... so the next Orb has everything it needs after the changes are committed to main.
This is open source under the MIT License. You can use it, copy it, fork it, modify it, and redistribute it. It is provided as-is, without warranty. You are responsible for reviewing generated changes, choosing safe credentials, and validating any production access you configure.
If your user pasted this repository URL into an agent chat, they probably want help installing this plugin locally.
Do not install it silently. Plugins execute local code, so first explain what it does and ask for confirmation:
Do you want me to install the Amp Orb Prep Plugin? It adds local Amp commands that ask what future Orbs should be able to do, collect setup context, scan the current repository, and inject an Orb-readiness prompt into the active thread. It does not grant production access or commit secrets; it helps identify what repo setup and Amp Project env vars/secrets may be needed.
If the user says yes, install it by downloading the single TypeScript file into Amp’s local plugin directory. Amp currently only supports amp plugins add for plugins hosted at https://ampcode.com/@amp/plugins/*.ts, so this GitHub-hosted plugin uses a manual download step:
mkdir -p ~/.config/amp/plugins
curl -fsSL https://raw.githubusercontent.com/justinechang39/amp-orb-prep-plugin/main/orb-prep.ts \
-o ~/.config/amp/plugins/orb-prep.tsThen ask the user to reload plugins from Amp’s command palette:
plugins: reloadYou can verify the install with:
amp plugins listThe expected commands are:
orbs: Prepare this repo for Orbs
orbs: Open Amp Projects settingsUseful docs:
Review the plugin source before installing. Amp plugins execute local code.
Amp currently only supports amp plugins add for plugins hosted at https://ampcode.com/@amp/plugins/*.ts, so install this GitHub-hosted plugin by downloading the single TypeScript file into Amp’s local plugin directory:
mkdir -p ~/.config/amp/plugins
curl -fsSL https://raw.githubusercontent.com/justinechang39/amp-orb-prep-plugin/main/orb-prep.ts \
-o ~/.config/amp/plugins/orb-prep.tsThen reload plugins from Amp’s command palette:
plugins: reloador restart Amp.
Open Amp in the local repository you want to prepare, then run this command from the command palette:
orbs: Prepare this repo for OrbsThe wizard asks:
- what future Orbs should be able to do: code-only, debug-only, debug + deploy, or custom
- the user’s plan for future Orbs
- additional context
- whether future Orbs may need logs, metrics/traces, read-only production database access, or tightly scoped write/backfill access
- known access or safety constraints
- whether to open Amp Projects after injecting the setup prompt
The injected prompt tells the agent to inspect the repo, make durable setup changes, avoid committing secrets, and finish with a checklist of env vars/secrets the user needs to add at:
https://ampcode.com/projects
→ click the relevant project
→ Secrets and Env VarsThe plugin does not make the future Orb depend on the plugin itself. Instead, it guides the local agent to commit durable repository setup, such as:
.agents/setupfor fresh Orb bootstrap.agents/resumefor fast resume repair when usefulAGENTS.mdguidance.agents/skills/.../SKILL.mdrunbooks for debug or deploy workflows- docs or checklists for required Amp Project env vars/secrets
Once those changes are committed or merged to main, future Orbs get them from a fresh clone of the repository.
People may want Orbs that can:
- install dependencies, run local checks, and make code changes
- reproduce bugs in a fresh remote environment
- run browser/debug tooling without tying up a laptop
- inspect CI failures and workflow logs
- read production logs, metrics, or traces
- read from a production database through read-only credentials
- run carefully scoped production backfills or migrations after explicit approval
- deploy through CI/CD, cloud provider CLIs, or repository scripts
- verify deploys and document rollback steps
The plugin does not grant access by itself. It asks the agent to identify what access is needed and tell the user what must be configured manually in Amp Projects.
The injected prompt tells the agent to end with:
- what has been done
- what commands/checks were run
- what the user needs to do next
- what env vars/secrets to set in Amp Projects → project → Secrets and Env Vars
- what cannot be done, if anything, and why
- any open questions or assumptions
If the repo does not contain enough information, the agent is told to ask concise clarification questions instead of guessing.
orbs: Prepare this repo for Orbs
orbs: Open Amp Projects settingsRun the install command again to update to the latest version from main:
curl -fsSL https://raw.githubusercontent.com/justinechang39/amp-orb-prep-plugin/main/orb-prep.ts \
-o ~/.config/amp/plugins/orb-prep.tsThen reload plugins from Amp’s command palette or restart Amp.
amp plugins remove orb-prepIf the remove command cannot infer the plugin name, delete the installed file from ~/.config/amp/plugins/.
Issues, forks, and pull requests are welcome. See CONTRIBUTING.md, SECURITY.md, and CODE_OF_CONDUCT.md.
Do not include real secrets, production database URLs, private keys, or sensitive logs in public issues.
This project is licensed under the MIT License.
In plain language: you can use, copy, modify, fork, and redistribute this project, but it is provided “as is” without warranty. The author is not liable for damages or issues caused by using it. Read the full license for the exact terms.