create-repository

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Create repository

创建仓库

Create one prepared creation baseline from settled repository facts.

Read

standards/repository-lifecycle.md

from the selected release before operating this transition.

Reuse facts already settled in the conversation or supplied specification. Collect only missing decisions before running anything. Repository name, one-line purpose, visibility, and license must be explicit. Establish enough applicability facts to prove every selectable ecosystem profile matches or cannot match. Infer the GitHub owner, local destination, and applicability facts only from unambiguous context; collect an unspecified ecosystem before invocation and ask only for unproven facts. This step is complete only when every selectable profile fully matches or conflicts with a settled fact. Express the license as an SPDX identifier or key from the selected standards release's pinned license catalog.
Settle the new repository's canonical-validation declaration: one executable, its ordered literal arguments, and an optional normalized repository-relative working directory (default
```
.
```
). Do not encode shell syntax, quoting, pipelines, redirects, glob expansion, or environment expansion in these fields. Run the bundled adapter with the declaration and settled facts. Pass an exact release when the user selected one; omit
```
--version
```
to select the latest stable release. Repeat
```
--fact NAME=VALUE
```
for applicability facts, including repeating the same name for each value of a multi-value fact. Repeat
```
--profile NAME
```
for every explicitly selected ecosystem profile.
sh
```
python3 .agents/skills/create-repository/scripts/create \
  --name NAME \
  --purpose 'ONE LINE' \
  --visibility private \
  --license MIT \
  --owner OWNER \
  --destination /ABSOLUTE/PATH \
  --validation-executable scripts/validate \
  [--validation-argument='LITERAL ARGUMENT' ...] \
  [--validation-working-directory RELATIVE/DIRECTORY] \
  [--fact NAME=VALUE ...] [--profile NAME ...] [--version VERSION]
```
Surface the goal's assessment, retained-state report, and recovery action. Completion means an uncommitted baseline on unborn
```
main
```
, an empty GitHub repository configured as
```
origin
```
, and first publication still required. Use the exact canonical phrase
```
first publication
```
in the final report and leave that separate operation for the user to invoke.

The operation creates standards and documentation content only. Product scaffolding and package or build manifests remain outside this operation.

基于已确定的仓库信息创建一个预配置的创建基准。

在执行此操作前，请阅读所选版本中的

standards/repository-lifecycle.md

文档。

复用对话中已确定的信息或提供的规范内容。仅在运行操作前收集缺失的决策信息。仓库名称、单行描述、可见性及许可证必须明确。收集足够的适用性信息，以证明每个可选的生态系统配置文件要么匹配，要么无法匹配。仅从明确的上下文推断GitHub所有者、本地目标路径及适用性信息；在调用前收集未指定的生态系统信息，仅询问未确认的信息。只有当每个可选配置文件完全匹配或与已确定的信息冲突时，此步骤才算完成。许可证需以所选标准版本固定许可证目录中的SPDX标识符或密钥表示。
确定新仓库的规范验证声明：一个可执行文件、其有序的字面参数，以及可选的标准化仓库相对工作目录（默认值为
```
.
```
）。请勿在这些字段中编码Shell语法、引号、管道、重定向、通配符扩展或环境变量扩展。使用声明和已确定的信息运行捆绑的适配器。当用户选择了特定版本时，传入确切版本；省略
```
--version
```
以选择最新稳定版本。对适用性信息重复使用
```
--fact NAME=VALUE
```
，包括对多值信息的每个值重复相同的名称。对每个明确选择的生态系统配置文件重复使用
```
--profile NAME
```
。
sh
```
python3 .agents/skills/create-repository/scripts/create \
  --name NAME \
  --purpose 'ONE LINE' \
  --visibility private \
  --license MIT \
  --owner OWNER \
  --destination /ABSOLUTE/PATH \
  --validation-executable scripts/validate \
  [--validation-argument='LITERAL ARGUMENT' ...] \
  [--validation-working-directory RELATIVE/DIRECTORY] \
  [--fact NAME=VALUE ...] [--profile NAME ...] [--version VERSION]
```
展示目标评估结果、保留状态报告及恢复操作。完成状态意味着在未初始化的
```
main
```
分支上有一个未提交的基准，已将空的GitHub仓库配置为
```
origin
```
，且首次发布仍需执行。在最终报告中使用确切的标准表述
```
first publication
```
，并将该独立操作留给用户自行调用。

此操作仅创建标准和文档内容。产品脚手架、包或构建清单不属于此操作的范畴。