@link-assistant/hive-mind 0.47.0 → 0.47.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
CHANGED
|
@@ -1,5 +1,24 @@
|
|
|
1
1
|
# @link-assistant/hive-mind
|
|
2
2
|
|
|
3
|
+
## 0.47.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- a44ab88: Add system prompt guidance to prefer using existing code as examples
|
|
8
|
+
- Added guideline to encourage searching for similar existing implementations before implementing from scratch
|
|
9
|
+
- Applied consistently across all three prompt modules (claude, codex, opencode)
|
|
10
|
+
- Helps maintain consistency with existing patterns and reduces redundant work
|
|
11
|
+
|
|
12
|
+
## 0.47.1
|
|
13
|
+
|
|
14
|
+
### Patch Changes
|
|
15
|
+
|
|
16
|
+
- 68c0417: Fix Rocq installation verification by sourcing opam environment
|
|
17
|
+
- Source opam environment before verifying Rocq in installation summary
|
|
18
|
+
- Use `rocq -v` for verification as recommended by official documentation
|
|
19
|
+
- Update CI workflow to require Rocq to be accessible (not optional)
|
|
20
|
+
- Add case study documenting the issue and solution
|
|
21
|
+
|
|
3
22
|
## 0.47.0
|
|
4
23
|
|
|
5
24
|
### Minor Changes
|
package/package.json
CHANGED
|
@@ -135,6 +135,7 @@ Initial research.
|
|
|
135
135
|
|
|
136
136
|
Solution development and testing.
|
|
137
137
|
- When issue is solvable, implement code with tests.
|
|
138
|
+
- When implementing features, search for similar existing implementations in the codebase and use them as examples instead of implementing everything from scratch.
|
|
138
139
|
- When coding, each atomic step that can be useful by itself should be commited to the pull request's branch, meaning if work will be interrupted by any reason parts of solution will still be kept intact and safe in pull request.
|
|
139
140
|
- When you test:
|
|
140
141
|
start from testing of small functions using separate scripts;
|
|
@@ -127,6 +127,7 @@ Initial research.
|
|
|
127
127
|
|
|
128
128
|
Solution development and testing.
|
|
129
129
|
- When issue is solvable, implement code with tests.
|
|
130
|
+
- When implementing features, search for similar existing implementations in the codebase and use them as examples instead of implementing everything from scratch.
|
|
130
131
|
- When coding, each atomic step that can be useful by itself should be commited to the pull request's branch, meaning if work will be interrupted by any reason parts of solution will still be kept intact and safe in pull request.
|
|
131
132
|
- When you test:
|
|
132
133
|
start from testing of small functions using separate scripts;
|
|
@@ -119,6 +119,7 @@ Initial research.
|
|
|
119
119
|
|
|
120
120
|
Solution development and testing.
|
|
121
121
|
- When issue is solvable, implement code with tests.
|
|
122
|
+
- When implementing features, search for similar existing implementations in the codebase and use them as examples instead of implementing everything from scratch.
|
|
122
123
|
- When coding, each atomic step that can be useful by itself should be commited to the pull request's branch, meaning if work will be interrupted by any reason parts of solution will still be kept intact and safe in pull request.
|
|
123
124
|
- When you test:
|
|
124
125
|
start from testing of small functions using separate scripts;
|