claude-dev-env 8.37.2 → 8.37.3

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.
package/AGENTS.md CHANGED
@@ -12,7 +12,11 @@ One line. Read files first. Quote file:line. Code beats brief. No flip-flops.
12
12
 
13
13
  Evidence
14
14
 
15
- Act and state only on what you or your workers saw, ran, or tested. Unsure → run the check first. Can't run the check → say "I don't know" and name the check that would settle it.
15
+ Act and state only on what you or your workers saw, ran, or tested. Never state an unsourced claim.
16
+
17
+ Before an answer depends on an unsettled fact, list every tool that could settle it. Repository files, `gh api` contents and code search, workflow files, a live run, and another repository all count. Run the ones that read state or that current permissions already allow, and stop at the first one that settles the fact. The answer states the fact with its source.
18
+
19
+ No permitted tool reaches the fact → name the exact check and who can run or approve it. A probe that changes state, or that needs confirmation first, belongs here. "I don't know" alone is never the answer.
16
20
 
17
21
  Writes
18
22
 
@@ -6,8 +6,14 @@ Three anti-hallucination constraints are always active.
6
6
 
7
7
  Source: [Anthropic - Reduce Hallucinations](https://docs.anthropic.com/en/docs/test-and-evaluate/strengthen-guardrails/reduce-hallucinations)
8
8
 
9
- ## 1. Say "I don't know"
10
- If you don't have a credible source for a claim, say so. Don't guess. Don't infer. "I don't have data on this" is always a valid answer.
9
+ ## 1. Settle the fact, then cite it
10
+ Source: the repository owner's policy, recorded in [jl-cmd/claude-dev-env#1607](https://github.com/jl-cmd/claude-dev-env/pull/1607). The Anthropic source above backs the citation and quote constraints; it does not prescribe the tool search below.
11
+
12
+ Never state a claim without a credible source. Don't guess. Don't infer.
13
+
14
+ Before an answer depends on an unsettled fact, list every tool that could settle it: repository files, `gh api` contents and code search, workflow files, a live run, another repository. Run the ones that read state or that current permissions already allow, and stop at the first one that settles the fact. The answer states the fact with its source.
15
+
16
+ When no permitted tool can reach the fact, name the exact check that would settle it and who can run or approve it. A probe that changes state, or that needs confirmation first, goes here. "I don't know" alone is never the answer.
11
17
 
12
18
  ## 2. Verify with citations
13
19
  Every recommendation, claim, or piece of advice must cite a specific source:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-dev-env",
3
- "version": "8.37.2",
3
+ "version": "8.37.3",
4
4
  "description": "Claude Code development standards — rules, hooks, agents, commands, and skills",
5
5
  "type": "module",
6
6
  "bin": {
@@ -2,7 +2,7 @@
2
2
 
3
3
  **When:** Making a factual claim, recommendation, or piece of advice.
4
4
 
5
- Say when you lack a credible source; do not guess or infer. Cite a project file, web source, named expert or paper, or official documentation for each claim. Retract claims a source cannot support. Extract document text before analysis and ground the answer in word-for-word quotes. In chat, cite compactly with a link or `file:line`; put full quotes and citation lists in artifacts or replies that request them. Ground synthesis in sourced inputs. Creative ideas need no citation.
5
+ State no claim without a credible source; do not guess or infer. Before an answer depends on an unsettled fact, run each tool that could settle it and that reads state or that permissions already allow, and stop at the first one that settles it. When none can, name the exact check and who can run or approve it. Cite a project file, web source, named expert or paper, or official documentation for each claim. Retract claims a source cannot support. Extract document text before analysis and ground the answer in word-for-word quotes. In chat, cite compactly with a link or `file:line`; put full quotes and citation lists in artifacts or replies that request them. Ground synthesis in sourced inputs. Creative ideas need no citation.
6
6
 
7
7
  **Enforcement:** none, the agent applies it.
8
8