This repo's contributor conventions and release flow live in CONTRIBUTING.md. Read it end-to-end before opening a PR. Everything an agent needs to know is in there — this file just makes sure you don't miss it.
The two failure modes most likely to bite an agent here are:
- Forgetting
yarn changeset. The PR will merge fine, but nothing publishes. CI does not block missing changesets — you must self-enforce. See Adding a changeset inCONTRIBUTING.md. - Hand-editing versions in
package.jsonorcodemod.yaml. Don't. The Changesets bot owns version bumps. See Release workflow inCONTRIBUTING.md.
Before declaring a task done, check CONTRIBUTING.md for the conventions in Adding a new codemod (directory layout, package scope, single-quoted YAML) and run the checks listed in Making changes.
Before implementing codemods for a new Backstage release, use the project skill .agents/skills/backstage-codemod-issue-research/SKILL.md to research breaking changes, classify codemod vs document-only items, produce an inventory table, and draft GitHub issue specs. Implementation starts only after issues are filed and approved — then hand off to the codemod skill (install via Codemod OSS quickstart; verify with npx codemod ai list --format json and use the returned path).