@igorlau/dotagents 1.0.13 → 1.0.14

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.
@@ -2,12 +2,14 @@
2
2
 
3
3
  Apply these rules when you write, refactor, or review code:
4
4
 
5
- - Comment the why that the code can't show: a constraint, a workaround with its issue link, a non-obvious trade-off, an invariant, or the source of copied code. Keep it to one line when you can.
6
- - Let the code carry the what. When a comment would restate the code, improve a name or extract a function instead, and write no comment.
5
+ - Leave most code without comments. Comment the why the code can't show: a constraint, a workaround with its issue link, a non-obvious trade-off, an invariant, or the source of copied code. Keep it to one line when you can.
6
+ - Let names and types carry the what. When a comment would restate the code, improve a name or extract a function instead.
7
+ - Assume the reader knows the language, its libraries, and the platform. Comment only what is specific to this code.
7
8
  - Write comments for future readers of the code as it is. Change history, notes such as "added" or "now uses", and messages to the reviewer belong in the commit message or pull request.
8
9
  - Delete code instead of commenting it out. Git keeps the history.
9
- - Document public APIs in the language's doc-comment convention: purpose, contract, errors, and side effects, not the implementation.
10
+ - Write doc comments where the repository documents its APIs, or on an exported API whose name and types don't show its contract. Cover purpose, contract, errors, and side effects, not the implementation.
11
+ - Write comments above a function, class, property, or other declaration as doc comments in the language's convention, such as `/** */` JSDoc in TypeScript, so editors show them in hover tooltips, unless the surrounding code uses another style.
10
12
  - Explain regular expressions and complex algorithms with what they match or compute.
11
13
  - When you change code, update every comment that the change makes inaccurate, and delete comments that no longer apply.
12
14
  - When you review code, flag comments that restate the code, contradict it, or narrate changes, and ask for a why comment where intentional code looks wrong.
13
- - Match the comment density and style of the surrounding code.
15
+ - Match the comment density and style of the surrounding code. In a new file, match the repository's other files.
@@ -39,7 +39,7 @@ Done when every requirement of the task, plan, or request has code that meets it
39
39
 
40
40
  ## 4. Verify
41
41
 
42
- Run the task's "Verify" section, the plan's final check, or the repository's tests, type checker, and linter, and show the output. Check every acceptance criterion one by one.
42
+ Run the task's "Verify" section, the plan's final check, or the repository's tests, type checker, and linter, and show the output. Check every acceptance criterion one by one. Reread your diff against the code comments rule, and fix what it flags.
43
43
 
44
44
  When verification fails, or the task or plan turns out wrong (a fact contradicts it, or meeting it needs work outside its scope), stop. Report the failing check or the conflicting fact and propose a change to the task or plan. Keep the task file, the roadmap's decisions, and the plan as they are until the user agrees, and keep the change inside its scope.
45
45
 
@@ -1 +1 @@
1
- {"commit":"3187ce7"}
1
+ {"commit":"f6ee8bc"}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@igorlau/dotagents",
3
- "version": "1.0.13",
3
+ "version": "1.0.14",
4
4
  "description": "Install a curated set of agent skills and rules into Claude Code, Codex, and GitHub Copilot.",
5
5
  "license": "MIT",
6
6
  "repository": {