Improve README and reorganize documentation

- Streamline README.md to focus on user-facing content
- Move AUTO_PUBLISH_SETUP.md to .github/ directory for better organization
- Add clear callout for framework maintainers with setup guide reference
- Remove verbose setup instructions from main README
- Maintain all essential information while improving readability

Author: alexbit-codemod

AUTO_PUBLISH_SETUP.md .github/AUTO_PUBLISH_SETUP.mdAUTO_PUBLISH_SETUP.md renamed to .github/AUTO_PUBLISH_SETUP.md

@@ -2,49 +2,11 @@
   <img src=".github/assets/migrations-template.png" alt="<ECOSYSTEM_NAME> Codemods" />
 </div>
 
-This repository serves as a template for open-source migrations, allowing contributors & framework maintainers to quickly whip up a repository for codemods that resolve breaking changes, refactors, and more.
-
-This template repository comes pre-configured with a GitHub workflow that automatically publishes the latest version of your codemods, keeping them up-to-date on [Codemod Registry](https://app.codemod.com/registry).
-
-> **Initial setup guide (remove once the repo is customized)**
-> 
-> 1. Search and replace placeholders:
->    - `<ECOSYSTEM_NAME>` (e.g., "React", "Node.js", "AcmeLib")
->    - `@<NAMESPACE>` (e.g., `acme`) 
->    - `<MAJOR_VERSION>` (e.g., `v5`)
-> 2. Scaffold new codemods under `recipes` and name them like `@<NAMESPACE>/<MAJOR_VERSION> (optional)/<codemod-name>`:
-> 
-> ```bash
-> npx codemod@latest init recipes/my-codemod
-> ```
-> 
-> 3. Build codemod manually or with **[Codemod Studio](https://app.codemod.com/studio) (recommended)** ([Read docs →](https://go.codemod.com/studio-docs)).
-> 4. Validate and test:
-> 
-> ```bash
-> npm run validate
-> npm run test
-> ```
-> 
-> 5. Commit hooks and CI run lint, validate, typecheck, and tests.
-> 
-> 6. Set up auto-publishing to [Codemod Registry](https://app.codemod.com/registry):
-> 
->     1. **Get API key**: [https://app.codemod.com/api-keys](https://app.codemod.com/api-keys)
->     2. **Create GitHub Environment**: Repository Settings → Environments → New environment (name it `production`)
->     3. **Add secret**: `CODEMOD_API_KEY` with your API key
->     4. **Optional variables**: `CODEMOD_REGISTRY_SCOPE`, `CODEMOD_REGISTRY_URL`
-> 
-> This automatically publishes codemods when you merge changes to `main`. See [AUTO_PUBLISH_SETUP.md](./AUTO_PUBLISH_SETUP.md) for details.
-
-
-## Overview
-
-This repository contains codemods (automated migrations) for <ECOSYSTEM_NAME>. These codemods facilitate adopting new features and upgrading across breaking changes.
-
-Codemods, public or private, are preferred to reside in repositories owned by the main organization of their respective projects. This repository serves as a template for codemod packages, allowing contributors to quickly create a repository for their published codemods.
-
-This template repository comes pre-configured with a GitHub workflow that automatically publishes the latest version of your codemod, eliminating the need to manually publish codemods after making updates.
+> **Remove this section once the repo is customized**
+> Framework/SDK maintainers: This template comes with setup guides, utilities, and a GitHub Action to help you and your community build and publish codemods with ease. Once you, the repo maintainers, approve codemod PRs, they’ll be automatically published as official codemods to the [Codemod Registry](https://app.codemod.com/registry) under your org scope. Check out the [Node.js codemods](https://codemod.link/nodejs-official) for an example. See [AUTO_PUBLISH_SETUP.md](.github/AUTO_PUBLISH_SETUP.md) for setup instructions.
+
+This repository contains codemods for <FRAMEWORK_OR_SDK_NAME>. These codemods facilitate adopting new features and upgrading across breaking changes.
+
 
 ## Running Codemods