chatccc 0.2.136 → 0.2.137
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -1 +1,55 @@
|
|
|
1
|
+
# Claude-Specific Injection Prompt
|
|
2
|
+
|
|
3
|
+
Use this prompt as the Claude Agent SDK injection prompt for this project.
|
|
4
|
+
|
|
5
|
+
Project workspace:
|
|
6
|
+
|
|
7
|
+
```text
|
|
8
|
+
f:\users\weizhangjian\feishuclauderprivate
|
|
9
|
+
```
|
|
10
|
+
|
|
11
|
+
## Repeated Successful Command Guard
|
|
12
|
+
|
|
13
|
+
When working in this project through Claude Agent SDK, repeated successful shell commands are a completion signal, not a reason to keep using tools.
|
|
14
|
+
|
|
15
|
+
A shell command is considered the same command when all of these are true:
|
|
16
|
+
|
|
17
|
+
- The command text is effectively the same.
|
|
18
|
+
- The working directory is the same.
|
|
19
|
+
- The current task goal has not changed.
|
|
20
|
+
- There is no new user input that changes the task.
|
|
21
|
+
- There is no new error output that explains why the command must be run again.
|
|
22
|
+
|
|
23
|
+
If the same shell command succeeds more than once consecutively, do not call it again.
|
|
24
|
+
|
|
25
|
+
After the second consecutive successful execution of the same command, the next assistant action must be a final user-facing response. Do not call another tool unless the next command is materially different and has a clear reason based on the latest output.
|
|
26
|
+
|
|
27
|
+
This guard applies to all shell commands, including but not limited to:
|
|
28
|
+
|
|
29
|
+
- test commands
|
|
30
|
+
- build commands
|
|
31
|
+
- git commands
|
|
32
|
+
- install commands
|
|
33
|
+
- formatting commands
|
|
34
|
+
- project scripts
|
|
35
|
+
- status or inspection commands
|
|
36
|
+
|
|
37
|
+
Do not "verify one more time" by repeating the same successful command. If verification is needed, use a different command that checks a different fact, or explain the current result to the user.
|
|
38
|
+
|
|
39
|
+
If you notice that you are about to repeat a successful command with the same arguments, stop using tools and respond to the user with the current result.
|
|
40
|
+
|
|
41
|
+
If you produce or observe text like "I'm stuck in a loop", do not call any more tools. Immediately send the final user-facing response explaining:
|
|
42
|
+
|
|
43
|
+
- what has completed,
|
|
44
|
+
- what is still uncertain, if anything,
|
|
45
|
+
- and what the user can do next, if action is needed.
|
|
46
|
+
|
|
47
|
+
## Hard Stop Rule
|
|
48
|
+
|
|
49
|
+
Never execute the same successful shell command three times for the same task in this project.
|
|
50
|
+
|
|
51
|
+
If the same command has already succeeded twice in a row, the next assistant action must be a final response to the user, not another tool call.
|
|
52
|
+
|
|
53
|
+
Successful repeated command execution is a terminal condition. Prefer a concise final response over further tool calls.
|
|
54
|
+
|
|
1
55
|
如果计划写好了等待你的审阅，将计划文件通过当前聊天软件发给用户
|
package/config.sample.json
CHANGED