@icebreakers/monorepo-templates 1.2.1 → 1.3.1

package/templates/vitepress/start/first-run.md

@@ -0,0 +1,39 @@
+# Your first run
+
+This is the smallest complete repoctl workflow. It makes one change, records evidence, and leaves you with a clear next action.
+
+## Install
+
+```bash
+pnpm add -D repoctl
+```
+
+## Initialize
+
+```bash
+pnpm exec repo init
+```
+
+Review the planned files before accepting writes. If the repository already has local conventions, use the adoption guide before allowing replacements.
+
+## Diagnose
+
+```bash
+pnpm exec repo doctor
+```
+
+The report checks the repository root, package manager, workspace layout, task runner, hooks, and release metadata. Fix the first reported blocker, then run the command again.
+
+## Plan checks
+
+```bash
+pnpm exec repo check --dry-run
+```
+
+This prints the commands that would run for lint, types, builds, tests, and package checks. Execute the plan only after it matches the checks your repository expects.
+
+## Next
+
+- New repository: [Create a package or app](/tasks/create-project).
+- Existing repository: [Adopt an existing workspace](/tasks/adopt-existing).
+- CI setup: [Add checks to CI](/tasks/ci).

package/templates/vitepress/start/index.md

@@ -0,0 +1,26 @@
+# Start here
+
+Use this section when repoctl is new to you. The shortest useful path is to install the CLI, run `repo init`, then run `repo doctor`.
+
+## Pick your first move
+
+- [Install and initialize](./install.md) if this is your first repoctl command.
+- [Run the first diagnosis](./diagnose.md) if repoctl is already installed.
+- [Choose the next task](./choose-next.md) after you have a diagnosis.
+
+## What repoctl does
+
+repoctl keeps common monorepo work in a small, predictable command set:
+
+| Need                            | Command                |
+| ------------------------------- | ---------------------- |
+| Add repository conventions      | `repo init`            |
+| Inspect repository health       | `repo doctor`          |
+| Create a package or app         | `repo new`             |
+| Plan checks before running them | `repo check --dry-run` |
+
+The CLI works with pnpm workspaces and understands Turborepo task graphs. It does not replace either tool.
+
+## Before you continue
+
+You need Node.js 22.12 or newer and pnpm available on your path. Run commands from the repository root so repoctl can read the workspace configuration.

package/templates/vitepress/{repoctl/getting-started.md → start/install.md}

@@ -1,4 +1,4 @@
-# Getting Started
+# Install and initialize
 
 This guide follows the order you would use when adding repoctl to a workspace.
 
@@ -110,7 +110,7 @@ pnpm exec repo upgrade --yes
 
 ## Next Steps
 
-- Adopt an existing repository: [Adopt Existing Repositories](./adopt-existing.md).
-- Set team defaults: [Configuration](./config.md).
-- Inspect template keys: [Templates](./templates.md).
-- Share diagnostic output: [Troubleshooting](./troubleshooting.md).
+- Adopt an existing repository: [Adopt an existing workspace](/tasks/adopt-existing).
+- Set team defaults: [Configuration](/reference/config).
+- Inspect template keys: [Templates](/reference/templates).
+- Share diagnostic output: [Troubleshoot](/tasks/troubleshooting).

package/templates/vitepress/{repoctl → tasks}/adopt-existing.md

@@ -1,4 +1,30 @@
-# Adopt Existing Repositories
+# Adopt an existing workspace
+
+## When To Use
+
+Use this task when a workspace already has scripts, hooks, or configuration that you need to keep while introducing repoctl.
+
+## Prerequisites
+
+- Run commands from the workspace root.
+- Commit or stash unrelated local changes.
+- Confirm that Node.js 22.12 or newer and pnpm are available.
+
+## Smallest Command
+
+```bash
+repo doctor --markdown --redact --out reports/baseline.md
+```
+
+## Expected Output
+
+The report records the detected package manager, workspace layout, task runner, tooling files, and release setup without exposing local paths.
+
+## Common Branches
+
+- Existing conventions are healthy: keep them and add only the missing managed assets.
+- A file is already managed locally: use `repo upgrade --no-overwrite` and review the diff.
+- Tooling is split across loaders: resolve the loader first, then rerun the diagnosis.
 
 repoctl is not only for newly generated repositories. It can be adopted gradually in existing pnpm workspaces by using diagnostics and conservative asset syncs.
 
@@ -128,6 +154,6 @@ or manually extend `pnpm-workspace.yaml`.
 
 ## Keep Reading
 
-- [Workflows and CI](./workflows.md)
-- [Troubleshooting](./troubleshooting.md)
-- [Configuration](./config.md)
+- [Add checks to CI](/tasks/ci)
+- [Troubleshoot](/tasks/troubleshooting)
+- [Configuration](/reference/config)

package/templates/vitepress/{repoctl → tasks}/checks.md

@@ -2,7 +2,33 @@
 outline: deep
 ---
 
-# repoctl Verification
+# Run checks
+
+## When To Use
+
+Use this task before a commit, before a pull request, or when you need to reproduce the repository's CI plan locally.
+
+## Prerequisites
+
+- Run `repo doctor` from the workspace root.
+- Install dependencies with the repository's pinned pnpm version.
+- Decide whether you need a fast check or the full delivery gate.
+
+## Smallest Command
+
+```bash
+repo check --dry-run
+```
+
+## Expected Output
+
+repoctl prints the selected tasks and the exact commands that would run. Remove `--dry-run` only after the plan matches the repository policy.
+
+## Common Branches
+
+- A staged file needs a focused check: use `repo check --staged`.
+- CI requires an artifact: add `--json --out reports/check-plan.json`.
+- You are preparing a release: use `repo check --full` after the fast check passes.
 
 `repo check` provides stable, task-oriented entrypoints for local and CI verification. It preserves the underlying workspace scripts and reports which commands will run before execution.
 

package/templates/vitepress/{repoctl/workflows.md → tasks/ci.md}

@@ -1,4 +1,30 @@
-# Workflows and CI
+# Add checks to CI
+
+## When To Use
+
+Use this task when local commands are ready and the same repository policy must run on every pull request or branch.
+
+## Prerequisites
+
+- A passing `repo check --dry-run` plan.
+- A CI runner with Node.js, pnpm, and the repository lockfile.
+- Non-interactive credentials for any publish or release job.
+
+## Smallest Command
+
+```bash
+repo check --full --json --out reports/check-plan.json
+```
+
+## Expected Output
+
+CI receives a stable plan and can upload the JSON or Markdown report as an artifact. The same command remains runnable locally.
+
+## Common Branches
+
+- Pull requests need a fast gate: use `repo check --staged` or the repository's pre-commit mode.
+- Main branch needs a delivery gate: use `repo check --full`.
+- A release job needs a version plan: run `repo release --dry-run` before publishing.
 
 repoctl commands have two audiences: humans using short daily commands, and automation consuming stable reports.
 
@@ -82,8 +108,43 @@ repo verify pre-push
 | Output for scripts                    | `--json --out <file>`                              |
 | Share a redacted report               | `--markdown --redact --out <file>`                 |
 
+## Documentation Worker
+
+The repoctl documentation is deployed as the `repoctl-docs` Cloudflare Worker. VitePress produces static assets, and Workers Static Assets serves them without an application handler or an `ASSETS` binding.
+
+### Workers Builds settings
+
+| Setting               | Value                                                   |
+| --------------------- | ------------------------------------------------------- |
+| Repository root       | Repository root                                         |
+| Production branch     | `main`                                                  |
+| Build command         | `pnpm --filter @icebreakers/website build`              |
+| Production deploy     | `pnpm --filter @icebreakers/website run deploy`         |
+| Non-production deploy | `pnpm --filter @icebreakers/website run deploy:preview` |
+
+The build command checks locale parity before VitePress generates `.vitepress/dist`. The Worker config serves the generated `404.html` for missing routes and keeps `public/_redirects` active for legacy `/en/*` links.
+
+### Preview, release, and rollback
+
+Run a local validation before changing production:
+
+```bash
+pnpm --filter @icebreakers/website build
+pnpm --filter @icebreakers/website run deploy:dry-run
+pnpm --filter @icebreakers/website exec wrangler dev
+```
+
+Non-production Workers Builds upload a preview version. Promote a validated build through the production deploy command. To roll back, inspect the version history and select the last known-good version:
+
+```bash
+pnpm --filter @icebreakers/website exec wrangler versions list
+pnpm --filter @icebreakers/website exec wrangler rollback <VERSION_ID>
+```
+
+`repoctl.icebreaker.top` is the canonical custom domain. Cloudflare Redirect Rules send `repo.icebreaker.top/*` and `monorepo.icebreaker.top/*` to the canonical host with a permanent redirect while preserving the path and query string.
+
 ## Keep Reading
 
-- [Command Reference](./commands.md)
-- [Troubleshooting](./troubleshooting.md)
-- [Command Aliases](./aliases.md)
+- [Command Reference](/reference/commands)
+- [Troubleshoot](/tasks/troubleshooting)
+- [Command Aliases](/reference/aliases)

package/templates/vitepress/tasks/create-project.md

@@ -0,0 +1,37 @@
+# Create a package or app
+
+Use this task when the workspace is ready and you need a new package, application, service, CLI, or documentation site.
+
+## Prerequisites
+
+- Run `repo doctor` from the workspace root.
+- Confirm the package name and destination directory.
+- Check the available template keys with `repo templates`.
+
+## Smallest command
+
+```bash
+repo new <name> --template <template>
+```
+
+For example:
+
+```bash
+repo new shared-config --template package
+```
+
+Use `--dry-run` when you want to inspect the file plan without writing anything.
+
+## Expected result
+
+repoctl prints the selected template, destination, and files it will create. After confirmation, the new project is added to the workspace and its package metadata is ready for the repository checks.
+
+## Common branches
+
+- Template key is unknown: run `repo templates` and choose an installed key.
+- Destination exists: choose a new name or inspect the existing project before using an overwrite option.
+- The project needs custom assets: create it first, then use [managed template assets](/reference/template-assets) for shared files.
+
+## Next
+
+Run [checks](/tasks/checks), then add the new project to the [CI workflow](/tasks/ci).

package/templates/vitepress/{repoctl/scenarios.md → tasks/index.md}

@@ -1,4 +1,4 @@
-# Choose By Scenario
+# Task index
 
 Start here when you know what you want to do, but not which repoctl command to use.
 
@@ -17,7 +17,7 @@ pnpm exec repo init --yes
 pnpm exec repo doctor
 ```
 
-Keep reading: [Getting Started](./getting-started.md).
+Continue with [Install and initialize](/start/install).
 
 ## I Want To Adopt repoctl In An Existing Repo
 
@@ -29,7 +29,7 @@ pnpm exec repo upgrade --no-overwrite
 pnpm exec repo doctor --markdown --redact --out reports/doctor-after.md
 ```
 
-Keep reading: [Adopt Existing Repositories](./adopt-existing.md).
+Continue with [Adopt an existing workspace](/tasks/adopt-existing).
 
 ## I Want To Create A Package Or App
 
@@ -45,7 +45,7 @@ For daily development, root scripts also work:
 pnpm run repo:new -- sdk --template tsdown
 ```
 
-Keep reading: [Templates](./templates.md).
+Keep reading: [Templates](/reference/templates).
 
 ## I Want To Check Before Committing
 
@@ -62,7 +62,7 @@ pnpm exec repo check --json --out reports/check-plan.json
 pnpm exec repo check --markdown --redact --out reports/check-plan.md
 ```
 
-Keep reading: [Workflows and CI](./workflows.md).
+Continue with [Add checks to CI](/tasks/ci).
 
 ## I Want To Debug CI Or Another Machine
 
@@ -72,7 +72,7 @@ pnpm exec repo env support --markdown --redact --out reports/support.md
 pnpm exec repo env snapshot --json --out reports/snapshot.json
 ```
 
-Keep reading: [Troubleshooting](./troubleshooting.md).
+Continue with [Troubleshoot](/tasks/troubleshooting).
 
 ## I Want To Sync Standard Assets
 
@@ -103,7 +103,7 @@ pnpm exec repo config inspect
 pnpm exec repo cfg i --json --out reports/config.json
 ```
 
-Keep reading: [Configuration](./config.md).
+Keep reading: [Configuration](/reference/config).
 
 ## I Want Shorter Commands
 
@@ -114,4 +114,4 @@ repo e support --markdown --redact
 repo cfg i
 ```
 
-Keep reading: [Command Aliases](./aliases.md).
+Keep reading: [Command Aliases](/reference/aliases).

package/templates/vitepress/tasks/release.md

@@ -0,0 +1,31 @@
+# Release packages
+
+Use this task when a change is ready to version and publish. Keep the release plan reviewable before any registry write.
+
+## Prerequisites
+
+- `repo doctor` reports a valid package manager and release configuration.
+- The working tree is clean except for the intended changes.
+- Every publishable change has a changeset or the repository's chosen intent file.
+
+## Smallest command
+
+```bash
+repo release --dry-run
+```
+
+Review the package groups, versions, changelog entries, and publish commands. Run the same command without `--dry-run` only after the plan is approved.
+
+## Expected result
+
+The release report names the packages that will change, the version decisions, and each subprocess that will run. A successful release also completes the configured post-publish hooks.
+
+## Common branches
+
+- Missing intent: add a changeset and rerun the plan.
+- Fixed group mismatch: inspect the package relationships before editing versions.
+- Registry authentication failure: refresh the local token and rerun the publish step; do not commit credentials.
+
+## Next
+
+Read [publishing and changelogs](/learn/monorepo/publish) for repository policy and [reports and output](/tasks/reports) for CI artifacts.

package/templates/vitepress/{repoctl → tasks}/reports.md

@@ -4,6 +4,31 @@ outline: deep
 
 # Reports and Automation Output
 
+## When To Use
+
+Use this task when a person, CI job, or support request needs a durable record of what repoctl found or planned.
+
+## Prerequisites
+
+- Choose a `reports/` directory that is ignored or uploaded as a CI artifact.
+- Use `--redact` before sharing environment details outside the repository.
+
+## Smallest Command
+
+```bash
+repo env support --markdown --redact --out reports/support.md
+```
+
+## Expected Output
+
+The output file contains stable headings and command results that can be attached to a pull request or issue.
+
+## Common Branches
+
+- Another tool consumes the result: use JSON with `--json`.
+- You only need to inspect a plan: combine `--dry-run` with the desired format.
+- A report contains a local path or token: regenerate it with `--redact`.
+
 repoctl commands expose human-readable text for terminals, Markdown for issues and pull requests, and stable JSON for automation.
 
 ## Common Options

package/templates/vitepress/{repoctl → tasks}/troubleshooting.md

@@ -1,4 +1,30 @@
-# Troubleshooting
+# Troubleshoot
+
+## When To Use
+
+Use this task when initialization, checks, templates, or automation stop with an unexpected result.
+
+## Prerequisites
+
+- Run the command from the repository root.
+- Keep the original error and the repository revision available.
+- Remove secrets before sharing command output.
+
+## Smallest Command
+
+```bash
+repo doctor --markdown --redact --out reports/doctor.md
+```
+
+## Expected Output
+
+The report identifies the repository root, package manager, workspace configuration, tooling, and the first failing check.
+
+## Common Branches
+
+- The command is run from a child directory: change to the workspace root.
+- A config file conflicts with a managed asset: inspect the plan before overwriting.
+- A template key is unknown: list templates with `repo templates`.
 
 repoctl focuses on reports that can be reproduced, saved, and shared.
 
@@ -91,6 +117,6 @@ repo check --json --out reports/check-plan.json
 
 ## Keep Reading
 
-- [Workflows and CI](./workflows.md)
-- [Command Reference](./commands.md)
-- [Command Aliases](./aliases.md)
+- [Add checks to CI](/tasks/ci)
+- [Command Reference](/reference/commands)
+- [Command Aliases](/reference/aliases)

package/templates/vitepress/tsconfig.json

@@ -9,6 +9,13 @@
     "skipLibCheck": true
   },
   "include": [
+    ".vitepress/home/**/*.ts",
+    ".vitepress/navigation/**/*.ts",
+    ".vitepress/seo.ts",
+    ".vitepress/theme/**/*.ts",
+    ".vitepress/theme/**/*.vue",
+    ".vitepress/env.d.ts",
+    "scripts/**/*.ts",
     "why/examples/2.npm-basic-package/src/**/*.ts",
     "why/examples/3.npm-basic-package/src/**/*.ts"
   ]

package/templates/vitepress/wrangler.jsonc

@@ -1,5 +1,22 @@
 {
-  "$schema": "https://unpkg.com/wrangler/config-schema.json",
-  "name": "monorepo-template",
-  "pages_build_output_dir": ".vitepress/dist"
+  "$schema": "./node_modules/wrangler/config-schema.json",
+  "name": "repoctl-docs",
+  "compatibility_date": "2026-08-16",
+  "compatibility_flags": ["nodejs_compat"],
+  "workers_dev": false,
+  "preview_urls": true,
+  "assets": {
+    "directory": ".vitepress/dist",
+    "not_found_handling": "404-page"
+  },
+  "routes": [
+    {
+      "pattern": "repoctl.icebreaker.top",
+      "custom_domain": true
+    }
+  ],
+  "observability": {
+    "enabled": true,
+    "head_sampling_rate": 1
+  }
 }

package/templates/vitepress/zh/ai/index.md

@@ -16,7 +16,7 @@ AI 文档入口用于给 Cursor、Claude Code、Codex 和其他 AI 编程工具
 
 ## 2. 在 AI 工具里怎么用
 
-优先把 `https://repo.icebreaker.top/llms.txt` 作为入口提供给 AI 工具。只有当工具不能继续抓取链接，或者你需要离线提供完整上下文时，再使用 `https://repo.icebreaker.top/llms-full.txt`。
+优先把 `https://repoctl.icebreaker.top/llms.txt` 作为入口提供给 AI 工具。只有当工具不能继续抓取链接，或者你需要离线提供完整上下文时，再使用 `https://repoctl.icebreaker.top/llms-full.txt`。
 
 ```txt
 先给 llms.txt

package/templates/vitepress/zh/ai/llms-txt.md

@@ -16,7 +16,7 @@ description: 使用 llms.txt 为大语言模型提供更易读取的 repoctl 文
 
 ## 1. 使用方式
 
-访问 `https://repo.icebreaker.top/llms.txt` 可以获取当前文档的 LLM 索引。如果需要一次性提供完整上下文，可以使用 `https://repo.icebreaker.top/llms-full.txt`。
+访问 `https://repoctl.icebreaker.top/llms.txt` 可以获取当前文档的 LLM 索引。如果需要一次性提供完整上下文，可以使用 `https://repoctl.icebreaker.top/llms-full.txt`。
 
 当你在 Cursor、Claude Code、Codex 或其他 AI 编程工具里引用 repoctl 文档时，优先提供 `llms.txt`，再按需要补充具体页面链接。
 
@@ -34,9 +34,9 @@ description: 说明这个页面解决的问题和适用场景。
 
 AI 入口应该保持显眼，但不要替代正常文档结构：
 
-| 页面类型                               | 推荐位置                             |
-| -------------------------------------- | ------------------------------------ |
-| repoctl 命令、校验、诊断、报告         | `/repoctl/`                          |
-| monorepo 和 npm 包基础知识             | `/knowledge/`、`/monorepo/`、`/why/` |
-| pnpm、Turborepo、versioning 等工具专题 | `/tools/`                            |
-| llms.txt 和 AI 工具读取约定            | `/ai/`                               |
+| 页面类型                               | 推荐位置                                          |
+| -------------------------------------- | ------------------------------------------------- |
+| repoctl 命令、校验、诊断、报告         | `/start/`                                         |
+| monorepo 和 npm 包基础知识             | `/learn/`、`/learn/monorepo/`、`/learn/packages/` |
+| pnpm、Turborepo、versioning 等工具专题 | `/learn/tools/`                                   |
+| llms.txt 和 AI 工具读取约定            | `/ai/`                                            |

package/templates/vitepress/zh/index.md

@@ -1,66 +1,9 @@
 ---
-layout: home
-
-hero:
-  name: repoctl
-  text: 让 pnpm monorepo 的日常操作更短、更稳
-  tagline: 用一套 CLI 管理初始化、诊断、创建模板、提交前校验和模板资产同步。
-  image:
-    src: /logo.jpg
-    alt: repoctl logo
-  actions:
-    - theme: brand
-      text: 快速开始
-      link: /zh/repoctl/getting-started
-    - theme: alt
-      text: 命令速查
-      link: /zh/repoctl/commands
-    - theme: alt
-      text: AI 文档入口
-      link: /zh/ai/
-
-features:
-  - title: 从已有仓库开始
-    details: 安装 repoctl 后运行 setup 和 doctor，先把 workspace、根脚本、配置冲突和提交链路检查清楚。
-  - title: 用模板创建包和应用
-    details: repo new 支持交互式创建、指定模板、dry-run、JSON 输出和创建计划落盘。
-  - title: 把质量门禁变成日常命令
-    details: repo check 统一预览和执行 lint、typecheck、build、test、tsd 等推荐校验。
-  - title: 给 AI 工具的文档入口
-    details: 构建时自动生成 llms.txt、llms-full.txt 和页面 Markdown，让 AI 编程工具更容易读取 repoctl 文档。
+layout: page
+aside: false
+pageClass: repoctl-home-page
+title: repoctl
+description: 面向 pnpm 与 Turborepo monorepo 的任务型 CLI。
 ---
 
-## 最短路径
-
-```bash
-pnpm add -D repoctl
-pnpm exec repo init
-pnpm exec repo doctor
-pnpm exec repo new
-pnpm exec repo check
-```
-
-在由 repoctl 创建或初始化的仓库里，同一套工作流会暴露成更短的根脚本：
-
-```bash
-pnpm run repo:init
-pnpm run repo:doctor
-pnpm run repo:new
-pnpm run repo:check
-```
-
-## 你可以继续阅读
-
-- [repoctl 概览](./repoctl/index.md)
-- [快速开始](./repoctl/getting-started.md)
-- [接入已有仓库](./repoctl/adopt-existing.md)
-- [按场景选命令](./repoctl/scenarios.md)
-- [执行模型](./repoctl/execution-model.md)
-- [命令速查](./repoctl/commands.md)
-- [校验链路](./repoctl/checks.md)
-- [doctor 诊断](./repoctl/doctor.md)
-- [配置文件](./repoctl/config.md)
-- [模板与创建](./repoctl/templates.md)
-- [模板资产治理](./repoctl/template-assets.md)
-- [工作流与 CI](./repoctl/workflows.md)
-- [报告与自动化输出](./repoctl/reports.md)
+<HomePage locale="zh" />

package/templates/vitepress/zh/learn/index.md

@@ -0,0 +1,18 @@
+# 理解这套系统
+
+第一次流程跑通后，再进入 Learn。这里解释 repoctl、monorepo、包、模板和底层工具之间的边界。
+
+## 核心概念
+
+- [repoctl 如何融入仓库](./repoctl-model)
+- [Monorepo 基础](./monorepo/)
+- [现代 npm 包](./packages/)
+- [模板体系](./monorepo/templates)
+
+## 工具
+
+[工具专题](/zh/learn/tools/)解释 pnpm、Turborepo、版本管理、hooks、暂存区校验和依赖自动化。
+
+## 建议阅读顺序
+
+先了解仓库模型，再按需要选择 monorepo 基础或包发布。需要可执行步骤时，回到[任务](/zh/tasks/)章节。

package/templates/vitepress/zh/{monorepo → learn/monorepo}/commands.md

@@ -2,9 +2,9 @@
 
 repoctl 现在是这套文档的主线。完整命令说明请阅读：
 
-- [repoctl 命令速查](../repoctl/commands.md)
-- [repoctl 模板与创建](../repoctl/templates.md)
-- [repoctl 排障与报告](../repoctl/troubleshooting.md)
+- [repoctl 命令速查](/zh/reference/commands)
+- [repoctl 模板与创建](/zh/reference/templates)
+- [repoctl 排障](/zh/tasks/troubleshooting)
 
 ## monorepo 知识点：为什么要统一命令入口
 

package/templates/vitepress/zh/{monorepo → learn/monorepo}/manage.md

@@ -2,7 +2,7 @@
 
 这一页是 repoctl 文档后面的知识库页面。它不再重新解释所有命令参数，而是解释：为什么这些命令能让 monorepo 日常管理变简单。
 
-如果你只想查命令，直接看 [repoctl 工作流与 CI](../repoctl/workflows.md) 或 [repoctl 命令速查](../repoctl/commands.md)。
+如果你只想查命令，直接看 [把校验加入 CI](/zh/tasks/ci) 或 [repoctl 命令速查](/zh/reference/commands)。
 
 ## 先记住默认工作流
 
@@ -237,7 +237,7 @@ pnpm test
 
 ## 继续阅读
 
-- [repoctl 工作流与 CI](../repoctl/workflows.md)
-- [repoctl 命令速查](../repoctl/commands.md)
-- [repoctl 排障与报告](../repoctl/troubleshooting.md)
+- [把校验加入 CI](/zh/tasks/ci)
+- [repoctl 命令速查](/zh/reference/commands)
+- [repoctl 排障](/zh/tasks/troubleshooting)
 - [发包与变更日志](./publish.md)

package/templates/vitepress/zh/{monorepo → learn/monorepo}/templates.md

@@ -2,8 +2,8 @@
 
 模板创建已经收敛到 repoctl 文档：
 
-- [repoctl 模板与创建](../repoctl/templates.md)
-- [repoctl 快速开始](../repoctl/getting-started.md)
+- [repoctl 模板与创建](/zh/reference/templates)
+- [repoctl 快速开始](/zh/start/install)
 
 ## monorepo 知识点：模板为什么重要