> For the complete documentation index, see [llms.txt](https://data-programs.gitbook.io/singularity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://data-programs.gitbook.io/singularity/zh/cli-reference/prep/add-piece.md).

# 添加片段

{% code fullWidth="true" %}

```
NAME:
   singularity prep add-piece - 手动向一个准备工作添加片段信息。这对于由外部工具准备的片段非常有用。

USAGE:
   singularity prep add-piece [command options] <preparation id|name>

CATEGORY:
   片段管理

OPTIONS:
   --piece-cid value   片段的CID
   --piece-size value  片段的大小（默认值："32GiB"）
   --file-path value   CAR文件路径，用于确定文件的大小和根CID
   --root-cid value    CAR文件的根CID
   --help, -h          显示帮助
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://data-programs.gitbook.io/singularity/zh/cli-reference/prep/add-piece.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.