Update React repo owner

.claude/skills/docs-writer-blog/SKILL.md

@@ -159,7 +159,7 @@ See [How to Upgrade to React X.Y](/blog/YYYY/MM/DD/react-xy-upgrade-guide) for s
 
 ### React {/*react*/}
 
-* Add `useNewHook` for [purpose]. ([#12345](https://github.com/facebook/react/pull/12345) by [@contributor](https://github.com/contributor))
+* Add `useNewHook` for [purpose]. ([#12345](https://github.com/react/react/pull/12345) by [@contributor](https://github.com/contributor))
 
 ---
 
@@ -603,7 +603,7 @@ npm install react@latest react-dom@latest
 
 | Type | Pattern |
 |------|---------|
-| GitHub PR | `[#12345](https://github.com/facebook/react/pull/12345)` |
+| GitHub PR | `[#12345](https://github.com/react/react/pull/12345)` |
 | GitHub user | `[@username](https://github.com/username)` |
 | Twitter/X | `[@username](https://x.com/username)` |
 | Bluesky | `[Name](https://bsky.app/profile/handle)` |
@@ -623,8 +623,8 @@ For more information, see the docs for [`useActionState`](/reference/react/useAc
 ### Bullet Pattern
 
 ```markdown
-* Add `useTransition` for concurrent rendering. ([#10426](https://github.com/facebook/react/pull/10426) by [@acdlite](https://github.com/acdlite))
-* Fix `useReducer` observing incorrect props. ([#22445](https://github.com/facebook/react/pull/22445) by [@josephsavona](https://github.com/josephsavona))
+* Add `useTransition` for concurrent rendering. ([#10426](https://github.com/react/react/pull/10426) by [@acdlite](https://github.com/acdlite))
+* Fix `useReducer` observing incorrect props. ([#22445](https://github.com/react/react/pull/22445) by [@josephsavona](https://github.com/josephsavona))
 ```
 
 **Structure:** `Verb` + backticked API + description + `([#PR](url) by [@user](url))`

.claude/skills/react-expert/SKILL.md

@@ -32,7 +32,7 @@ This skill produces exhaustive documentation research on any React API or concep
 2. **React Source Code** - Warnings, errors, implementation details
 3. **Git History** - Commit messages with context
 4. **GitHub PRs & Comments** - Design rationale (via `gh` CLI)
-5. **GitHub Issues** - Confusion/questions (facebook/react + reactjs/react.dev)
+5. **GitHub Issues** - Confusion/questions (react/react + reactjs/react.dev)
 6. **React Working Group** - Design discussions for newer APIs
 7. **Flow Types** - Source of truth for type signatures
 8. **TypeScript Types** - Note discrepancies with Flow
@@ -51,7 +51,7 @@ First, ensure the React repo is available locally:
 if [ -d ".claude/react" ]; then
   cd .claude/react && git pull origin main
 else
-  git clone --depth=100 https://github.com/facebook/react.git .claude/react
+  git clone --depth=100 https://github.com/react/react.git .claude/react
 fi
 ```
 
@@ -71,8 +71,8 @@ Spawn these agents IN PARALLEL using the Task tool. Each agent receives the skep
 | test-explorer | Explore | Test files for usage patterns | Search `.claude/react/packages/*/src/__tests__/` for test files mentioning the topic. Extract actual usage examples WITH file paths and line numbers. |
 | source-explorer | Explore | Warnings/errors in source | Search `.claude/react/packages/*/src/` for console.error, console.warn, and error messages mentioning the topic. Document trigger conditions. |
 | git-historian | Explore | Commit messages | Run `git log --all --grep="<topic>" --oneline -50` in `.claude/react`. Read full commit messages for context. |
-| pr-researcher | Explore | PRs introducing/modifying API | Run `gh pr list -R facebook/react --search "<topic>" --state all --limit 20`. Read key PR descriptions and comments. |
-| issue-hunter | Explore | Issues showing confusion | Search issues in both `facebook/react` and `reactjs/react.dev` repos. Look for common questions and misunderstandings. |
+| pr-researcher | Explore | PRs introducing/modifying API | Run `gh pr list -R react/react --search "<topic>" --state all --limit 20`. Read key PR descriptions and comments. |
+| issue-hunter | Explore | Issues showing confusion | Search issues in both `react/react` and `reactjs/react.dev` repos. Look for common questions and misunderstandings. |
 | types-inspector | Explore | Flow + TypeScript signatures | Find Flow types in `.claude/react/packages/*/src/*.js` (look for `@flow` annotations). Find TS types in `.claude/react/packages/*/index.d.ts`. Note discrepancies. |
 
 ### Step 3: Agent Prompts
@@ -164,8 +164,8 @@ CRITICAL: Do NOT rely on your prior knowledge. Only report what you find in PRs.
 
 Your task: Find PRs that introduced or modified <TOPIC>.
 
-1. Run: gh pr list -R facebook/react --search "<topic>" --state all --limit 20 --json number,title,url
-2. For promising PRs, read details: gh pr view <number> -R facebook/react
+1. Run: gh pr list -R react/react --search "<topic>" --state all --limit 20 --json number,title,url
+2. For promising PRs, read details: gh pr view <number> -R react/react
 3. Look for:
    - The original RFC/motivation
    - Design discussions in comments
@@ -189,7 +189,7 @@ CRITICAL: Do NOT rely on your prior knowledge. Only report what you find in issu
 
 Your task: Find issues that reveal common confusion about <TOPIC>.
 
-1. Search facebook/react: gh issue list -R facebook/react --search "<topic>" --state all --limit 20 --json number,title,url
+1. Search react/react: gh issue list -R react/react --search "<topic>" --state all --limit 20 --json number,title,url
 2. Search reactjs/react.dev: gh issue list -R reactjs/react.dev --search "<topic>" --state all --limit 20 --json number,title,url
 3. For each issue, identify:
    - What the user was confused about
@@ -199,7 +199,7 @@ Your task: Find issues that reveal common confusion about <TOPIC>.
 Format your output as:
 ## Common Confusion
 ### Issue #<number>: <title>
-**Repo:** <facebook/react or reactjs/react.dev>
+**Repo:** <react/react or reactjs/react.dev>
 **Confusion:** <what they misunderstood>
 **Resolution:** <correct understanding>
 **Gotcha:** <if applicable>

.github/ISSUE_TEMPLATE/config.yml

@@ -1,6 +1,6 @@
 contact_links:
   - name: 📃 Bugs in React
-    url: https://github.com/facebook/react/issues/new/choose
+    url: https://github.com/react/react/issues/new/choose
     about: This issue tracker is not for bugs in React. Please file React issues here.
   - name: 🤔 Questions and Help
     url: https://reactjs.org/community/support.html

.github/workflows/discord_notify.yml

@@ -8,7 +8,7 @@ permissions: {}
 
 jobs:
   check_maintainer:
-    uses: facebook/react/.github/workflows/shared_check_maintainer.yml@main
+    uses: react/react/.github/workflows/shared_check_maintainer.yml@main
     permissions:
       # Used by check_maintainer
       contents: read

.github/workflows/label_core_team_prs.yml

@@ -12,7 +12,7 @@ env:
 
 jobs:
   check_maintainer:
-    uses: facebook/react/.github/workflows/shared_check_maintainer.yml@main
+    uses: react/react/.github/workflows/shared_check_maintainer.yml@main
     permissions:
       # Used by check_maintainer
       contents: read

scripts/deadLinkChecker.js

@@ -311,7 +311,7 @@ async function buildContributorMap() {
 async function fetchErrorCodes() {
   try {
     const response = await fetch(
-      'https://raw.githubusercontent.com/facebook/react/main/scripts/error-codes/codes.json'
+      'https://raw.githubusercontent.com/react/react/main/scripts/error-codes/codes.json'
     );
     if (!response.ok) {
       throw new Error(`Failed to fetch error codes: ${response.status}`);

src/components/Layout/Footer.tsx

@@ -344,7 +344,7 @@ export function Footer() {
           <FooterLink href="/community" isHeader={true}>
             Community
           </FooterLink>
-          <FooterLink href="https://github.com/facebook/react/blob/main/CODE_OF_CONDUCT.md">
+          <FooterLink href="https://github.com/react/react/blob/main/CODE_OF_CONDUCT.md">
             Code of Conduct
           </FooterLink>
           <FooterLink href="/community/team">Meet the Team</FooterLink>
@@ -386,7 +386,7 @@ export function Footer() {
             </ExternalLink>
             <ExternalLink
               aria-label="React on Github"
-              href="https://github.com/facebook/react"
+              href="https://github.com/react/react"
               className={socialLinkClasses}>
               <IconGitHub />
             </ExternalLink>

src/components/Layout/TopNav/TopNav.tsx

@@ -386,7 +386,7 @@ export default function TopNav({
                 </div>
                 <div className="flex">
                   <Link
-                    href="https://github.com/facebook/react/releases"
+                    href="https://github.com/react/react/releases"
                     target="_blank"
                     rel="noreferrer noopener"
                     aria-label="Open on GitHub"

src/components/MDX/Sandpack/DownloadButton.tsx

@@ -19,7 +19,7 @@ let supportsImportMap = false;
 
 function subscribe(cb: () => void) {
   // This shouldn't actually need to update, but this works around
-  // https://github.com/facebook/react/issues/26095
+  // https://github.com/react/react/issues/26095
   let timeout = setTimeout(() => {
     supportsImportMap =
       (HTMLScriptElement as any).supports &&

src/content/blog/2021/06/08/the-plan-for-react-18.md

@@ -51,7 +51,7 @@ Everyone can read the discussions in the [React 18 Working Group repo](https://g
 
 Because we expect an initial surge of interest in the Working Group, only invited members will be allowed to create or comment on threads. However, the threads are fully visible to the public, so everyone has access to the same information. We believe this is a good compromise between creating a productive environment for working group members, while maintaining transparency with the wider community.
 
-As always, you can submit bug reports, questions, and general feedback to our [issue tracker](https://github.com/facebook/react/issues).
+As always, you can submit bug reports, questions, and general feedback to our [issue tracker](https://github.com/react/react/issues).
 
 ## How to try React 18 Alpha today {/*how-to-try-react-18-alpha-today*/}
 

src/content/blog/2022/03/08/react-18-upgrade-guide.md

@@ -13,7 +13,7 @@ March 08, 2022 by [Rick Hanlon](https://twitter.com/rickhanlonii)
 
 As we shared in the [release post](/blog/2022/03/29/react-v18), React 18 introduces features powered by our new concurrent renderer, with a gradual adoption strategy for existing applications. In this post, we will guide you through the steps for upgrading to React 18.
 
-Please [report any issues](https://github.com/facebook/react/issues/new/choose) you encounter while upgrading to React 18.
+Please [report any issues](https://github.com/react/react/issues/new/choose) you encounter while upgrading to React 18.
 
 </Intro>
 
@@ -317,8 +317,8 @@ If you need to support Internet Explorer we recommend you stay with React 17.
 
 * **Components can now render `undefined`:** React no longer warns if you return `undefined` from a component. This makes the allowed component return values consistent with values that are allowed in the middle of a component tree. We suggest to use a linter to prevent mistakes like forgetting a `return` statement before JSX.
 * **In tests, `act` warnings are now opt-in:** If you're running end-to-end tests, the `act` warnings are unnecessary. We've introduced an [opt-in](https://github.com/reactwg/react-18/discussions/102) mechanism so you can enable them only for unit tests where they are useful and beneficial.
-* **No warning about `setState` on unmounted components:** Previously, React warned about memory leaks when you call `setState` on an unmounted component. This warning was added for subscriptions, but people primarily run into it in scenarios where setting state is fine, and workarounds make the code worse. We've [removed](https://github.com/facebook/react/pull/22114) this warning.
-* **No suppression of console logs:** When you use Strict Mode, React renders each component twice to help you find unexpected side effects. In React 17, we've suppressed console logs for one of the two renders to make the logs easier to read. In response to [community feedback](https://github.com/facebook/react/issues/21783) about this being confusing, we've removed the suppression. Instead, if you have React DevTools installed, the second log's renders will be displayed in grey, and there will be an option (off by default) to suppress them completely.
+* **No warning about `setState` on unmounted components:** Previously, React warned about memory leaks when you call `setState` on an unmounted component. This warning was added for subscriptions, but people primarily run into it in scenarios where setting state is fine, and workarounds make the code worse. We've [removed](https://github.com/react/react/pull/22114) this warning.
+* **No suppression of console logs:** When you use Strict Mode, React renders each component twice to help you find unexpected side effects. In React 17, we've suppressed console logs for one of the two renders to make the logs easier to read. In response to [community feedback](https://github.com/react/react/issues/21783) about this being confusing, we've removed the suppression. Instead, if you have React DevTools installed, the second log's renders will be displayed in grey, and there will be an option (off by default) to suppress them completely.
 * **Improved memory usage:** React now cleans up more internal fields on unmount, making the impact from unfixed memory leaks that may exist in your application code less severe.
 
 ### React DOM Server {/*react-dom-server*/}
@@ -328,4 +328,4 @@ If you need to support Internet Explorer we recommend you stay with React 17.
 
 ## Changelog {/*changelog*/}
 
-You can view the [full changelog here](https://github.com/facebook/react/blob/main/CHANGELOG.md).
+You can view the [full changelog here](https://github.com/react/react/blob/main/CHANGELOG.md).