pi-agentsmd 0.1.1 → 0.1.2
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/CHANGELOG.md +10 -0
- package/package.json +3 -3
- package/prompts/init.md +1 -0
package/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,16 @@ This project follows the spirit of [Keep a Changelog](https://keepachangelog.com
|
|
|
6
6
|
|
|
7
7
|
## [Unreleased]
|
|
8
8
|
|
|
9
|
+
## [0.1.2] - 2026-07-01
|
|
10
|
+
|
|
11
|
+
### Changed
|
|
12
|
+
|
|
13
|
+
- Update Pi core development dependency for Pi 0.80 compatibility.
|
|
14
|
+
|
|
15
|
+
### Fixed
|
|
16
|
+
|
|
17
|
+
- Sync init prompt with upstream Codex to refuse overwriting an existing AGENTS.md (resolves #12)
|
|
18
|
+
|
|
9
19
|
## [0.1.1] - 2026-06-08
|
|
10
20
|
|
|
11
21
|
### Fixed
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pi-agentsmd",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2",
|
|
4
4
|
"description": "Generate AGENTS.md contributor guides for Pi repositories.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"license": "MIT",
|
|
@@ -52,8 +52,8 @@
|
|
|
52
52
|
"@earendil-works/pi-coding-agent": "*"
|
|
53
53
|
},
|
|
54
54
|
"devDependencies": {
|
|
55
|
-
"@earendil-works/pi-coding-agent": "^0.
|
|
56
|
-
"@types/node": "^25.
|
|
55
|
+
"@earendil-works/pi-coding-agent": "^0.80.0",
|
|
56
|
+
"@types/node": "^25.9.3",
|
|
57
57
|
"typescript": "^6.0.3"
|
|
58
58
|
},
|
|
59
59
|
"publishConfig": {
|
package/prompts/init.md
CHANGED
|
@@ -1,4 +1,5 @@
|
|
|
1
1
|
Generate a file named AGENTS.md that serves as a contributor guide for this repository.
|
|
2
|
+
Before writing, check whether AGENTS.md already exists in the current working directory. If it does, do not overwrite or modify it.
|
|
2
3
|
Your goal is to produce a clear, concise, and well-structured document with descriptive headings and actionable explanations for each section.
|
|
3
4
|
Follow the outline below, but adapt as needed — add sections if relevant, and omit those that do not apply to this project.
|
|
4
5
|
|