> For the complete documentation index, see [llms.txt](https://sunzsh.gitbook.io/xiaoshan.bug/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sunzsh.gitbook.io/xiaoshan.bug/yi-hou-zang-huo-lei-huo-ye-ke-yi-diu-gei-chatgpt-liao.md).

# 以后脏活累活也可以丢给ChatGPT了

* 抖音：<https://v.douyin.com/AgvDxFv/>
* B站：<https://www.bilibili.com/video/BV13j411c7WU/>

我发现

我最近已经习惯把一些脏活累活

丢给chatGBT了

比方说这个我原来有张表

表里边有9个字段

是用来存储附件的URL的

然后呢现在有个需求

就是需要给每一个这个附件加一个

name和type

所以呢我就把这表结构丢给他

然后呢

我跟他说想给每一个附件加俩字段

一个是type

一个是name

然后呢告诉他数据类型答案

他就帮我生成了

修改表的circle语句了

我就直接执行就可以了

紧接着呢我又跟他说：那好

那Java的实体类也需要加字段对吧

然后呢

因为这个会话之前都跟他讲过了

用的是MyBatisPlus和lombok

所以呢

他帮我生成的都是符合我要求的

我直接把这些字段复制过去

直接覆盖一下就可以了

所以呢我发现其实

我们一个项目

最好对应的是一个ChatGBT的会话

这样的话呢因为我们的会话都被保留

所以在这个项目的开发过程中

只要有问题

我们就可以随时过来

请ChatGPT帮我们来做


---

# 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://sunzsh.gitbook.io/xiaoshan.bug/yi-hou-zang-huo-lei-huo-ye-ke-yi-diu-gei-chatgpt-liao.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.
