@igorlau/dotagents 1.0.21 → 1.0.22

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.
Files changed (108) hide show
  1. package/README.md +65 -65
  2. package/THIRD_PARTY_NOTICES.md +101 -6
  3. package/dist/build-info.json +1 -1
  4. package/dist/catalog.js +3 -3
  5. package/dist/cli.js +1 -1
  6. package/dist/commands.js +7 -5
  7. package/dist/manifest.js +8 -1
  8. package/dist/paths.js +0 -4
  9. package/dist/targets.js +3 -9
  10. package/dist/wizard.js +1 -1
  11. package/package.json +5 -3
  12. package/{plugin/rules → rules}/comments.upstream.json +1 -1
  13. package/{plugin/rules → rules}/ponytail.md +1 -1
  14. package/{plugin/rules → rules}/ponytail.upstream.json +1 -1
  15. package/{plugin/rules → rules}/writing.md +1 -2
  16. package/{plugin/rules → rules}/writing.upstream.json +1 -1
  17. package/{plugin/scaffold → scaffold}/AGENTS.md.tmpl +1 -1
  18. package/{plugin/skills → skills}/dot-code-review/SKILL.md +2 -0
  19. package/{plugin/skills → skills}/dot-code-review/UPSTREAM.json +1 -1
  20. package/skills/dot-code-review/references/finding-classes.md +33 -0
  21. package/{plugin/skills → skills}/dot-comments/UPSTREAM.json +1 -1
  22. package/{plugin/skills → skills}/dot-commit/SKILL.md +0 -2
  23. package/skills/dot-correct/UPSTREAM.json +8 -0
  24. package/{plugin/skills → skills}/dot-debug/UPSTREAM.json +1 -1
  25. package/{plugin/skills → skills}/dot-grilling/UPSTREAM.json +2 -2
  26. package/{plugin/skills → skills}/dot-handoff/UPSTREAM.json +1 -1
  27. package/{plugin/skills → skills}/dot-implement/SKILL.md +2 -2
  28. package/{plugin/skills → skills}/dot-plan/SKILL.md +3 -1
  29. package/{plugin/skills → skills}/dot-roadmap/SKILL.md +7 -4
  30. package/skills/dot-security-audit/SKILL.md +87 -0
  31. package/skills/dot-security-audit/UPSTREAM.json +8 -0
  32. package/skills/dot-security-audit/references/AI-AND-LLM.md +83 -0
  33. package/skills/dot-security-audit/references/ATTACK-CLASSES.md +130 -0
  34. package/skills/dot-security-audit/references/CLIENT-SIDE.md +83 -0
  35. package/skills/dot-security-audit/references/CLOUD-AND-DEPLOYMENT.md +86 -0
  36. package/skills/dot-security-audit/references/DATA-ISOLATION-AND-LIFECYCLE.md +84 -0
  37. package/skills/dot-security-audit/references/DESKTOP-MOBILE-AND-LOCAL-IPC.md +89 -0
  38. package/skills/dot-security-audit/references/MEMORY-SAFETY-AND-BINARY.md +101 -0
  39. package/skills/dot-security-audit/references/PROTOCOLS-RPC-AND-MESSAGING.md +81 -0
  40. package/skills/dot-security-audit/references/RESOURCE-EXHAUSTION-AND-AVAILABILITY.md +78 -0
  41. package/skills/dot-security-audit/references/SUPPLY-CHAIN-AND-RELEASE.md +73 -0
  42. package/skills/dot-security-audit/references/WEB-PROTOCOL-AND-AUTH.md +105 -0
  43. package/skills/dot-security-changes/SKILL.md +68 -0
  44. package/{plugin/skills → skills}/dot-testing/UPSTREAM.json +1 -1
  45. package/skills/dot-ui-review/SKILL.md +79 -0
  46. package/skills/dot-ui-review/UPSTREAM.json +8 -0
  47. package/skills/dot-ux-review/SKILL.md +50 -0
  48. package/skills/dot-ux-review/UPSTREAM.json +8 -0
  49. package/skills/dot-ux-review/references/web-interface-guidelines.md +191 -0
  50. package/{plugin/skills/dot-stack-review → skills/dot-walkthrough-branch}/SKILL.md +9 -30
  51. package/skills/dot-walkthrough-branch/references/layers.md +38 -0
  52. package/{plugin/skills/dot-stack-review → skills/dot-walkthrough-branch}/scripts/page.mjs +39 -10
  53. package/skills/dot-walkthrough-changes/SKILL.md +62 -0
  54. package/skills/dot-writing-for-agents/UPSTREAM.json +8 -0
  55. package/plugin/.claude-plugin/plugin.json +0 -10
  56. package/plugin/agents/dot-implementer.md +0 -27
  57. package/plugin/agents/dot-reviewer.md +0 -44
  58. package/plugin/agents/dot-tester.md +0 -25
  59. package/plugin/hooks/check.mjs +0 -118
  60. package/plugin/hooks/hooks.json +0 -54
  61. package/plugin/hooks/rules.mjs +0 -27
  62. package/plugin/skills/dot-correct/UPSTREAM.json +0 -8
  63. package/plugin/skills/dot-correct/agents/openai.yaml +0 -5
  64. package/plugin/skills/dot-debug/agents/openai.yaml +0 -3
  65. package/plugin/skills/dot-flow/SKILL.md +0 -105
  66. package/plugin/skills/dot-flow/agents/openai.yaml +0 -5
  67. package/plugin/skills/dot-flow/references/fix-round.md +0 -64
  68. package/plugin/skills/dot-flow/references/inline.md +0 -9
  69. package/plugin/skills/dot-grilling/agents/openai.yaml +0 -3
  70. package/plugin/skills/dot-handoff/agents/openai.yaml +0 -5
  71. package/plugin/skills/dot-roadmap/agents/openai.yaml +0 -5
  72. package/plugin/skills/dot-stack-review/agents/openai.yaml +0 -5
  73. package/plugin/skills/dot-writing-for-agents/UPSTREAM.json +0 -8
  74. package/plugin/skills/dot-writing-for-agents/agents/openai.yaml +0 -3
  75. /package/{plugin/rules → rules}/code-style.md +0 -0
  76. /package/{plugin/rules → rules}/comments.md +0 -0
  77. /package/{plugin/rules → rules}/core.md +0 -0
  78. /package/{plugin/scaffold → scaffold}/.claude/settings.json.tmpl +0 -0
  79. /package/{plugin/scaffold → scaffold}/.editorconfig.tmpl +0 -0
  80. /package/{plugin/scaffold → scaffold}/.gitattributes.tmpl +0 -0
  81. /package/{plugin/scaffold → scaffold}/CLAUDE.md.tmpl +0 -0
  82. /package/{plugin/skills → skills}/dot-code-review/references/maintainability.md +0 -0
  83. /package/{plugin/skills → skills}/dot-comments/SKILL.md +0 -0
  84. /package/{plugin/skills → skills}/dot-correct/SKILL.md +0 -0
  85. /package/{plugin/skills → skills}/dot-debug/SKILL.md +0 -0
  86. /package/{plugin/skills → skills}/dot-debug/references/loops.md +0 -0
  87. /package/{plugin/skills → skills}/dot-debug/scripts/hitl-loop.template.sh +0 -0
  88. /package/{plugin/skills → skills}/dot-docs-writing/SKILL.md +0 -0
  89. /package/{plugin/skills → skills}/dot-docs-writing/references/formatting.md +0 -0
  90. /package/{plugin/skills → skills}/dot-docs-writing/references/global-and-accessible.md +0 -0
  91. /package/{plugin/skills → skills}/dot-docs-writing/references/word-list.md +0 -0
  92. /package/{plugin/skills → skills}/dot-grilling/SKILL.md +0 -0
  93. /package/{plugin/skills → skills}/dot-handoff/SKILL.md +0 -0
  94. /package/{plugin/skills → skills}/dot-implement/UPSTREAM.json +0 -0
  95. /package/{plugin/skills → skills}/dot-implement/references/typescript.md +0 -0
  96. /package/{plugin/skills → skills}/dot-plan/UPSTREAM.json +0 -0
  97. /package/{plugin/skills → skills}/dot-plan/references/entity-schemas.md +0 -0
  98. /package/{plugin/skills → skills}/dot-roadmap/UPSTREAM.json +0 -0
  99. /package/{plugin/skills → skills}/dot-roadmap/references/wide-refactor.md +0 -0
  100. /package/{plugin/skills → skills}/dot-testing/SKILL.md +0 -0
  101. /package/{plugin/skills → skills}/dot-testing/references/after-implement.md +0 -0
  102. /package/{plugin/skills → skills}/dot-testing/references/http.md +0 -0
  103. /package/{plugin/skills → skills}/dot-testing/references/shared-state.md +0 -0
  104. /package/{plugin/skills → skills}/dot-testing/references/typescript.md +0 -0
  105. /package/{plugin/skills → skills}/dot-writing-for-agents/SKILL.md +0 -0
  106. /package/{plugin/skills → skills}/dot-writing-for-agents/references/pointers.md +0 -0
  107. /package/{plugin/skills → skills}/dot-writing-for-agents/references/skill-mechanics.md +0 -0
  108. /package/{plugin/skills → skills}/dot-writing-for-agents/references/steps.md +0 -0
package/README.md CHANGED
@@ -1,15 +1,18 @@
1
1
  # dotagents
2
2
 
3
- dotagents gives Claude Code, OpenAI Codex, and GitHub Copilot one AI workflow
4
- for every project. The workflow plans a change, writes code and tests in small
5
- steps, verifies each step, reviews the result, and asks for your decision.
3
+ dotagents gives Claude Code and GitHub Copilot the same skills and rules
4
+ for every project. The skills plan a change, write code and tests in small
5
+ steps, verify each step, review the result, and ask for your decision. In
6
+ Claude Code, `dot-factory` runs these steps for you, from one description to
7
+ a staged change.
6
8
 
7
9
  dotagents has two parts:
8
10
 
9
11
  - A plugin with skills, agents, and hooks. Claude Code, the
10
- Copilot CLI, and VS Code load the plugin.
11
- - A CLI that installs the always-on rules for all three coding agents, and the
12
- skills for Codex and Copilot.
12
+ Copilot CLI, and VS Code load the plugin. `dot-factory` and the agents
13
+ work only in Claude Code.
14
+ - A CLI that installs the always-on rules for both coding agents, and the
15
+ skills for Copilot.
13
16
 
14
17
  ## Install
15
18
 
@@ -79,62 +82,53 @@ Run `scaffold` before `init`. `init` adds a block to `AGENTS.md`, and
79
82
 
80
83
  ## The flow
81
84
 
82
- The following diagram shows the full flow, from an idea to the commits of one
83
- task. The agent stops for your decision at each "approve", "fix", or "accept":
85
+ In Claude Code, `dot-factory` takes a problem from one description to a
86
+ staged change. To start a run, give it the problem:
87
+
88
+ ```text
89
+ /dotagents:dot-factory Export the invoices as CSV, and do not write a row twice when a retry starts.
90
+ ```
91
+
92
+ The following diagram shows a run of the `feature` track. The main session
93
+ does all the work except the review, which runs in the `dot-reviewer` agent:
84
94
 
85
95
  ```mermaid
86
96
  sequenceDiagram
87
97
  actor User
88
98
  participant Main as Main session
89
- participant Agents as Step agents
90
- User->>Main: dot-grilling with an idea
91
- Main-->>User: Questions in rounds, with recommended answers
92
- User->>Main: Answers until the plan is clear
93
- User->>Main: dot-plan
94
- Main-->>User: Requirements
95
- User->>Main: Approve the requirements
96
- Main-->>User: Entity schemas
97
- User->>Main: Approve the schemas
98
- Main-->>User: Plan as small, verifiable steps
99
- User->>Main: Approve the plan
100
- User->>Main: dot-roadmap
101
- Main-->>User: Phases and task files with test cases
102
- User->>Main: Approve the roadmap
99
+ participant Reviewer as dot-reviewer
100
+ User->>Main: dot-factory with a problem
101
+ Main-->>User: Intake and track
102
+ Main->>Main: Research
103
+ Main-->>User: Questions about the open decisions
104
+ User->>Main: Answers
105
+ Main-->>User: Spec: phases, tasks, and test cases
106
+ User->>Main: Approve the spec
103
107
  loop Each task
104
- User->>Main: dot-flow with the task file
105
- Main->>Agents: 1. Production code (dot-implementer)
106
- Agents-->>Main: Reply
107
- Main->>Main: Run the checks of the reply
108
- Main->>Agents: 2. Tests (dot-tester)
109
- Agents-->>Main: Reply
110
- Main->>Main: Run the tests of the reply
111
- Main->>Agents: 3. Review (dot-reviewer)
112
- Agents-->>Main: Findings
113
- loop At most 2 automatic rounds, until a stop rule fires
114
- Main->>Agents: Steps 1 to 3 again for the high and medium findings
115
- Agents-->>Main: Status of each finding, and new findings
116
- end
117
- Main-->>User: Round history and findings
118
- break A blocker, or a check that differs from the reply
119
- Main-->>User: Stop. The files stay as they are.
120
- end
121
- opt Fix
122
- User->>Main: Fix these findings
123
- Main->>Agents: Steps 1 to 3 again, or only step 1 on the light path
124
- Main-->>User: Round history and findings
125
- end
126
- User->>Main: Accept
127
- User->>Main: dot-commit
128
- Main-->>User: Each commit for approval
129
- User->>Main: Approve
130
- Main-->>User: Commits, and a tick in the roadmap
108
+ Main->>Main: Code and tests
109
+ Main->>Main: Gate: check and tests, then tick the task
131
110
  end
111
+ Main->>Reviewer: Range, spec, and lenses
112
+ Reviewer-->>Main: Findings as JSON
113
+ loop Until the review script returns done
114
+ Main->>Main: Fix every finding, then run the Gate
115
+ Main->>Reviewer: Review the lines that the fix changed
116
+ Reviewer-->>Main: Findings as JSON
117
+ end
118
+ Main-->>User: Report, with all changes staged
119
+ User->>Main: dot-commit
132
120
  ```
133
121
 
134
- `dot-flow` never commits. In Codex and Copilot, `dot-flow` runs the three steps
135
- in the main session, with the same verification and stops.
122
+ The run stops for you at the spec approval, at the report, and at each
123
+ escalation: a question that the rules of the run cannot answer. It never
124
+ commits. Start Claude Code with `claude --effort medium` for a run. The main
125
+ session does most of the work, and `dot-reviewer` has its own model and
126
+ effort.
136
127
 
137
- To learn the workflow step by step, read the [guide](docs/guide/README.md).
128
+ Without `dot-factory`, and in Copilot, run each step yourself: `dot-grilling`,
129
+ `dot-plan`, and `dot-roadmap`, then `dot-implement`, `dot-testing`,
130
+ `dot-code-review`, and `dot-commit` for each task. To learn both ways, read
131
+ the [guide](docs/guide/README.md).
138
132
 
139
133
  ## Commands
140
134
 
@@ -158,24 +152,30 @@ write. To overwrite the file, add `--force`.
158
152
 
159
153
  ## What is included
160
154
 
161
- The always-on rules in [`plugin/rules/`](plugin/rules/) cover working
155
+ The always-on rules in [`rules/`](rules/) cover working
162
156
  agreements, the smallest complete change from
163
157
  [ponytail](https://github.com/DietrichGebert/ponytail), code comments, code
164
158
  style, and writing.
165
159
 
166
- The 15 skills in [`plugin/skills/`](plugin/skills/) load when a task needs
167
- them:
160
+ The 20 skills in [`skills/`](skills/) and
161
+ [`claude/skills/`](claude/skills/) load when a task needs them. You start
162
+ `dot-factory` yourself, and it works only in Claude Code:
168
163
 
169
164
  | Skill | Purpose |
170
165
  | ----- | ------- |
166
+ | `dot-factory` | Take a problem from one description to a staged change, with one spec approval and a Gate for each task. |
171
167
  | `dot-grilling` | Run an interview, in rounds of questions, that makes a plan clear. |
172
168
  | `dot-plan` | Plan a change as small, verifiable steps, with requirements and entity schemas. |
173
169
  | `dot-roadmap` | Split a plan into phases and tasks that each stand alone. |
174
- | `dot-flow` | Take a roadmap task through code, tests, and review, verify each step, fix the `high` and `medium` findings in automatic rounds, and stop for your decision. |
175
170
  | `dot-testing` | Write tests with a makeSut factory, alone or after `dot-implement`. |
176
171
  | `dot-implement` | Write the code of a change or roadmap task to the standards of the repository and the language. |
177
172
  | `dot-code-review` | Review a diff for correctness bugs and maintainability problems. |
178
- | `dot-stack-review` | Review the commits of a branch as an ordered stack of dependency layers. |
173
+ | `dot-walkthrough-branch` | Review the commits of a branch as an ordered stack of dependency layers. |
174
+ | `dot-walkthrough-changes` | Walk through the working-tree changes as an ordered stack of dependency layers. |
175
+ | `dot-security-audit` | Audit the whole codebase of a branch, or a path, for security vulnerabilities. |
176
+ | `dot-security-changes` | Check the working-tree changes for security problems. |
177
+ | `dot-ux-review` | Review UI code for UX and accessibility rules by reading the code, against the Vercel web interface guidelines. |
178
+ | `dot-ui-review` | Review UI changes visually in a browser against a live preview, or report why the review cannot run. |
179
179
  | `dot-comments` | Delete the comments in a diff that no exception protects. |
180
180
  | `dot-commit` | Commit changes as small, logical commits. |
181
181
  | `dot-debug` | Find the cause of a hard bug with a feedback loop. |
@@ -184,15 +184,15 @@ them:
184
184
  | `dot-docs-writing` | Give docs the structure and format of the Google developer documentation style. |
185
185
  | `dot-writing-for-agents` | Write skills, `AGENTS.md`, and `CLAUDE.md` files. |
186
186
 
187
- The plugin also has 3 agents in [`plugin/agents/`](plugin/agents/).
188
- `dot-flow` starts a new agent for each step, so each step starts with a clean
189
- context:
187
+ The plugin also has 3 agents in [`claude/agents/`](claude/agents/). Each
188
+ agent runs one step of a task in a clean context, with a fixed model and
189
+ effort. `dot-factory` starts only `dot-reviewer`:
190
190
 
191
- | Agent | Purpose |
192
- | ----- | ------- |
193
- | `dot-tester` | Write the tests of a task after the code exists. |
194
- | `dot-implementer` | Write the production code of a task. |
195
- | `dot-reviewer` | Review the changes of a task. |
191
+ | Agent | Purpose | Model | Effort |
192
+ | ----- | ------- | ----- | ------ |
193
+ | `dot-tester` | Write the tests of a task after the code exists. | `sonnet` | `medium` |
194
+ | `dot-implementer` | Write the production code of a task. | `sonnet` | `high` |
195
+ | `dot-reviewer` | Review a range of two trees, and write the findings as JSON. | `sonnet` | `high` |
196
196
 
197
197
  ## More information
198
198
 
@@ -35,9 +35,9 @@ SOFTWARE.
35
35
 
36
36
  ## DietrichGebert/ponytail
37
37
 
38
- The `ponytail` rules in `plugin/rules/ponytail.md` come from the `AGENTS.md`
38
+ The `ponytail` rules in `rules/ponytail.md` come from the `AGENTS.md`
39
39
  file in [DietrichGebert/ponytail](https://github.com/DietrichGebert/ponytail).
40
- `plugin/rules/ponytail.upstream.json` records the source commit and local
40
+ `rules/ponytail.upstream.json` records the source commit and local
41
41
  changes. The project is licensed under the MIT License:
42
42
 
43
43
  ```text
@@ -67,11 +67,11 @@ SOFTWARE.
67
67
  ## cursor/plugins pstack
68
68
 
69
69
  The `dot-comments` and `dot-correct` skills, the comment policy in
70
- `plugin/rules/comments.md`, and the word and format rules in
71
- `plugin/rules/writing.md` come from the
70
+ `rules/comments.md`, and the word and format rules in
71
+ `rules/writing.md` come from the
72
72
  `pstack` plugin in [cursor/plugins](https://github.com/cursor/plugins). The
73
- skills' `UPSTREAM.json` files, `plugin/rules/comments.upstream.json`, and
74
- `plugin/rules/writing.upstream.json` record the source commits and local
73
+ skills' `UPSTREAM.json` files, `rules/comments.upstream.json`, and
74
+ `rules/writing.upstream.json` record the source commits and local
75
75
  changes. The behavior test principle in the `dot-testing` skill, the rule to put
76
76
  removals first in the `dot-plan` and `dot-roadmap` skills, the domain model rules
77
77
  in `dot-plan`, the reader load, domain model, and scope rules in the
@@ -145,3 +145,98 @@ The `dot-docs-writing` skill is adapted from the
145
145
  by Google, licensed under the
146
146
  [Creative Commons Attribution 4.0 License](https://creativecommons.org/licenses/by/4.0/).
147
147
  The content was condensed, reorganized, and reworded for coding agents.
148
+
149
+ ## cloudflare/security-audit-skill
150
+
151
+ The `dot-security-audit` skill and its `references/` come from the
152
+ `security-audit` skill in
153
+ [cloudflare/security-audit-skill](https://github.com/cloudflare/security-audit-skill).
154
+ The skill's `UPSTREAM.json` file records the source commit and local changes.
155
+ The project is licensed under the MIT License:
156
+
157
+ ```text
158
+ MIT License
159
+
160
+ Copyright (c) 2025-2026 Cloudflare, Inc.
161
+
162
+ Permission is hereby granted, free of charge, to any person obtaining a copy
163
+ of this software and associated documentation files (the "Software"), to deal
164
+ in the Software without restriction, including without limitation the rights
165
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
166
+ copies of the Software, and to permit persons to whom the Software is
167
+ furnished to do so, subject to the following conditions:
168
+
169
+ The above copyright notice and this permission notice shall be included in all
170
+ copies or substantial portions of the Software.
171
+
172
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
173
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
174
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
175
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
176
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
177
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
178
+ SOFTWARE.
179
+ ```
180
+
181
+ ## vercel-labs/web-interface-guidelines
182
+
183
+ The `dot-ux-review` skill reads
184
+ `references/web-interface-guidelines.md`, a copy of `command.md` from
185
+ [vercel-labs/web-interface-guidelines](https://github.com/vercel-labs/web-interface-guidelines).
186
+ The skill's `UPSTREAM.json` file records the source commit and local changes.
187
+ The project is licensed under the MIT License:
188
+
189
+ ```text
190
+ MIT License
191
+
192
+ Copyright (c) 2025 Vercel Labs
193
+
194
+ Permission is hereby granted, free of charge, to any person obtaining a copy
195
+ of this software and associated documentation files (the "Software"), to deal
196
+ in the Software without restriction, including without limitation the rights
197
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
198
+ copies of the Software, and to permit persons to whom the Software is
199
+ furnished to do so, subject to the following conditions:
200
+
201
+ The above copyright notice and this permission notice shall be included in all
202
+ copies or substantial portions of the Software.
203
+
204
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
205
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
206
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
207
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
208
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
209
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
210
+ SOFTWARE.
211
+ ```
212
+
213
+ ## OneRedOak/claude-code-workflows
214
+
215
+ The `dot-ui-review` skill is a rewrite of the `design-review` workflow in
216
+ [OneRedOak/claude-code-workflows](https://github.com/OneRedOak/claude-code-workflows).
217
+ The skill's `UPSTREAM.json` file records the source commit and local changes.
218
+ The project is licensed under the MIT License:
219
+
220
+ ```text
221
+ MIT License
222
+
223
+ Copyright (c) 2025 Patrick Ellis
224
+
225
+ Permission is hereby granted, free of charge, to any person obtaining a copy
226
+ of this software and associated documentation files (the "Software"), to deal
227
+ in the Software without restriction, including without limitation the rights
228
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
229
+ copies of the Software, and to permit persons to whom the Software is
230
+ furnished to do so, subject to the following conditions:
231
+
232
+ The above copyright notice and this permission notice shall be included in all
233
+ copies or substantial portions of the Software.
234
+
235
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
236
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
237
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
238
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
239
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
240
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
241
+ SOFTWARE.
242
+ ```
@@ -1 +1 @@
1
- {"commit":"c4705cf"}
1
+ {"commit":"56d328e"}
package/dist/catalog.js CHANGED
@@ -1,10 +1,10 @@
1
1
  import fs from "node:fs";
2
2
  import path from "node:path";
3
- import { pluginRoot } from "./paths.js";
3
+ import { packageRoot } from "./paths.js";
4
4
  import { parseFrontmatter } from "./frontmatter.js";
5
5
  // Files that describe a skill's origin but aren't part of the skill itself.
6
6
  const META_FILES = new Set(["UPSTREAM.json"]);
7
- export function loadCatalog(root = pluginRoot) {
7
+ export function loadCatalog(root = packageRoot) {
8
8
  const rules = loadRules(path.join(root, "rules"));
9
9
  const skillsDir = path.join(root, "skills");
10
10
  const skills = fs
@@ -44,7 +44,7 @@ function loadSkill(dir) {
44
44
  }
45
45
  // Templates carry a .tmpl suffix, so agents and Git working in this repository
46
46
  // don't load them as its own AGENTS.md, CLAUDE.md, or .gitattributes.
47
- export function loadScaffold(root = pluginRoot) {
47
+ export function loadScaffold(root = packageRoot) {
48
48
  const dir = path.join(root, "scaffold");
49
49
  return listFiles(dir).map((rel) => ({ rel: rel.replace(/\.tmpl$/, ""), content: fs.readFileSync(path.join(dir, rel), "utf8") }));
50
50
  }
package/dist/cli.js CHANGED
@@ -18,7 +18,7 @@ Usage:
18
18
  dotagents check enable|disable Let the plugin's check hook run in the current repository, or stop it
19
19
 
20
20
  Options:
21
- --agents <list> Comma-separated: claude,codex,copilot (default: all)
21
+ --agents <list> Comma-separated: claude,copilot (default: all)
22
22
  --dry-run Print changes without writing them
23
23
  --force Overwrite files that were modified or not written by dotagents
24
24
  --source <spec> With install: where self-update fetches dotagents from
package/dist/commands.js CHANGED
@@ -6,7 +6,7 @@ import { readBlock } from "./blocks.js";
6
6
  import { loadCatalog, loadScaffold } from "./catalog.js";
7
7
  import { repoRoot } from "./git.js";
8
8
  import { fromStored, globalManifestPath, hash, projectManifestPath, readManifest, toStored, writeManifest, } from "./manifest.js";
9
- import { claudeHome, codexHome, configDir, packageRoot } from "./paths.js";
9
+ import { claudeHome, configDir, packageRoot } from "./paths.js";
10
10
  import { planInstall, planScaffold, projectClaudeRulesFile } from "./targets.js";
11
11
  export const DEFAULT_SOURCE = "@igorlau/dotagents@latest";
12
12
  export const UP_TO_DATE = "Already up to date.";
@@ -180,7 +180,12 @@ export function update(cwd, which, options) {
180
180
  ok = false;
181
181
  continue;
182
182
  }
183
- log(`Updating ${describe(scope)} to dotagents ${version()}:`);
183
+ if (manifest.agents.length === 0 && manifest.removedAgents.length > 0) {
184
+ log(`${manifest.removedAgents.join(", ")} is no longer supported. Removing ${describe(scope)}.`);
185
+ }
186
+ else {
187
+ log(`Updating ${describe(scope)} to dotagents ${version()}:`);
188
+ }
184
189
  ok = run(scope, manifest.agents, { ...options, agents: manifest.agents }) && ok;
185
190
  if (scope.mode === "global")
186
191
  logPluginHint(manifest.agents);
@@ -232,9 +237,6 @@ export function doctor(cwd) {
232
237
  else if (hash(entry.kind === "file" ? owned : owned.trim()) !== entry.hash)
233
238
  issues.push(`${entry.path}: modified since dotagents wrote it.`);
234
239
  }
235
- if (scope.mode === "global" && manifest.agents.includes("codex") && fs.existsSync(path.join(codexHome(), "AGENTS.override.md"))) {
236
- issues.push(`${path.join(codexHome(), "AGENTS.override.md")} exists, so Codex ignores the rules in AGENTS.md.`);
237
- }
238
240
  if (scope.mode === "global" && manifest.agents.includes("claude")) {
239
241
  issues.push(...(dotagentsPluginInstalled() ? duplicateClaudeSkills() : [PLUGIN_HINT]));
240
242
  }
package/dist/manifest.js CHANGED
@@ -1,6 +1,7 @@
1
1
  import crypto from "node:crypto";
2
2
  import fs from "node:fs";
3
3
  import path from "node:path";
4
+ import { AGENTS } from "./targets.js";
4
5
  import { configDir } from "./paths.js";
5
6
  export const PROJECT_MANIFEST = ".dotagents.json";
6
7
  export function hash(content) {
@@ -15,7 +16,13 @@ export function projectManifestPath(root) {
15
16
  export function readManifest(file) {
16
17
  if (!fs.existsSync(file))
17
18
  return undefined;
18
- return JSON.parse(fs.readFileSync(file, "utf8"));
19
+ const manifest = JSON.parse(fs.readFileSync(file, "utf8"));
20
+ const isSupported = (agent) => AGENTS.includes(agent);
21
+ return {
22
+ ...manifest,
23
+ agents: manifest.agents.filter(isSupported),
24
+ removedAgents: manifest.agents.filter((agent) => !isSupported(agent)),
25
+ };
19
26
  }
20
27
  export function writeManifest(file, manifest) {
21
28
  fs.mkdirSync(path.dirname(file), { recursive: true });
package/dist/paths.js CHANGED
@@ -7,9 +7,6 @@ export function homeDir() {
7
7
  export function claudeHome() {
8
8
  return process.env.CLAUDE_CONFIG_DIR ?? path.join(homeDir(), ".claude");
9
9
  }
10
- export function codexHome() {
11
- return process.env.CODEX_HOME ?? path.join(homeDir(), ".codex");
12
- }
13
10
  export function copilotHome() {
14
11
  return process.env.COPILOT_HOME ?? path.join(homeDir(), ".copilot");
15
12
  }
@@ -22,4 +19,3 @@ export function configDir() {
22
19
  }
23
20
  // Works from both src/ (tests, scripts) and dist/ (installed package).
24
21
  export const packageRoot = fileURLToPath(new URL("..", import.meta.url));
25
- export const pluginRoot = path.join(packageRoot, "plugin");
package/dist/targets.js CHANGED
@@ -1,7 +1,7 @@
1
1
  import fs from "node:fs";
2
2
  import path from "node:path";
3
- import { agentsHome, claudeHome, codexHome, copilotHome } from "./paths.js";
4
- export const AGENTS = ["claude", "codex", "copilot"];
3
+ import { agentsHome, claudeHome, copilotHome } from "./paths.js";
4
+ export const AGENTS = ["claude", "copilot"];
5
5
  const HEADER = "<!-- Managed by dotagents. Run `dotagents update` instead of editing this file. -->";
6
6
  const RULES_FILE = "dotagents.md";
7
7
  function layout(mode, root, pending) {
@@ -9,29 +9,25 @@ function layout(mode, root, pending) {
9
9
  return {
10
10
  skillDirs: {
11
11
  claude: path.join(claudeHome(), "skills"),
12
- codex: path.join(agentsHome(), "skills"),
13
12
  copilot: path.join(agentsHome(), "skills"),
14
13
  },
15
14
  claudeRules: path.join(claudeHome(), "rules", RULES_FILE),
16
15
  claudeRulesInAgentsMd: false,
17
- codexRules: path.join(codexHome(), "AGENTS.md"),
18
16
  // Copilot loads this file in every session; files in ~/.copilot/instructions/
19
17
  // load only when their applyTo pattern matches a file being edited.
20
18
  copilotRules: path.join(copilotHome(), "copilot-instructions.md"),
21
19
  };
22
20
  }
23
- // Copilot reads AGENTS.md too, so both agents share one block.
21
+ // Copilot reads AGENTS.md too, so Claude Code and Copilot share one block.
24
22
  const agentsMd = path.join(root, "AGENTS.md");
25
23
  const claudeRulesInAgentsMd = claudeReadsAgentsMd(root, pending);
26
24
  return {
27
25
  skillDirs: {
28
26
  claude: path.join(root, ".claude", "skills"),
29
- codex: path.join(root, ".agents", "skills"),
30
27
  copilot: path.join(root, ".agents", "skills"),
31
28
  },
32
29
  claudeRules: claudeRulesInAgentsMd ? agentsMd : projectClaudeRulesFile(root),
33
30
  claudeRulesInAgentsMd,
34
- codexRules: agentsMd,
35
31
  copilotRules: agentsMd,
36
32
  };
37
33
  }
@@ -61,8 +57,6 @@ export function planInstall(catalog, mode, agents, root = "", pending = []) {
61
57
  ? { kind: "block", path: target.claudeRules, content: rules }
62
58
  : { kind: "file", path: target.claudeRules, content: `${HEADER}\n\n${rules}\n` });
63
59
  }
64
- if (agents.includes("codex"))
65
- add({ kind: "block", path: target.codexRules, content: rules });
66
60
  if (agents.includes("copilot"))
67
61
  add({ kind: "block", path: target.copilotRules, content: rules });
68
62
  return [...ops.values()];
package/dist/wizard.js CHANGED
@@ -45,7 +45,7 @@ export function opensWizard({ command, interactive, values }) {
45
45
  return false;
46
46
  return !values["dry-run"] && !values.force && !values.global && !values.project && values.source === undefined;
47
47
  }
48
- const AGENT_LABELS = { claude: "Claude Code", codex: "Codex", copilot: "GitHub Copilot" };
48
+ const AGENT_LABELS = { claude: "Claude Code", copilot: "GitHub Copilot" };
49
49
  async function askAgents(prompts, agents) {
50
50
  return (agents ??
51
51
  prompts.multiselect({
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@igorlau/dotagents",
3
- "version": "1.0.21",
4
- "description": "Install a curated set of agent skills and rules into Claude Code, Codex, and GitHub Copilot.",
3
+ "version": "1.0.22",
4
+ "description": "Install a curated set of agent skills and rules into Claude Code and GitHub Copilot.",
5
5
  "license": "MIT",
6
6
  "repository": {
7
7
  "type": "git",
@@ -17,7 +17,9 @@
17
17
  },
18
18
  "files": [
19
19
  "dist",
20
- "plugin",
20
+ "skills",
21
+ "rules",
22
+ "scaffold",
21
23
  "THIRD_PARTY_NOTICES.md"
22
24
  ],
23
25
  "engines": {
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "repository": "https://github.com/cursor/plugins",
3
3
  "path": "pstack/agents/comment-sicko.md",
4
- "commit": "a5539b15a3d56e04992565aafee2b37051329ce3",
4
+ "commit": "e58dd043600587dbaf58ba315e7f2b38373eeb43",
5
5
  "license": "MIT",
6
6
  "modified": true,
7
7
  "notes": "Rewrote the agent's exception list as an always-on rule in neutral wording. Added the ponytail shortcut: exception, the rules to reshape surprises and encode constraints, and a pointer to the dot-comments skill. Dropped the suppression and report instructions, which live in dot-comments."
@@ -1,6 +1,6 @@
1
1
  # Ponytail, lazy senior dev mode
2
2
 
3
- You are a lazy senior developer. The best code is the code never written. You solve the whole problem with the least new code. Put what you skipped or did not check, and any risk the user must know, under the 🟡 heading. When a skill or an agent sets the format of the reply, put them in that format.
3
+ You are a lazy senior developer. The best code is the code never written. You solve the whole problem with the least new code. Put what you skipped or did not check, and any risk the user must know, at the end of the reply. When a skill or an agent sets the format of the reply, put them in that format.
4
4
 
5
5
  ## Before you write
6
6
 
@@ -4,5 +4,5 @@
4
4
  "commit": "2961b52fc1fe6a5a87c7a959a79512e5c2f3ffe5",
5
5
  "license": "MIT",
6
6
  "modified": true,
7
- "notes": "Removed the comment bullet (rules/comments.md owns comment guidance) and the closing note about the ponytail repository. Let a separate test step write the test that the check bullet asks for. Let the reply format of a skill or an agent hold the closing lines. Moved the closing lines under the 🟡 heading of rules/writing.md."
7
+ "notes": "Removed the comment bullet (rules/comments.md owns comment guidance) and the closing note about the ponytail repository. Let a separate test step write the test that the check bullet asks for. Let the reply format of a skill or an agent hold the closing lines. Moved the closing lines to the end of the reply."
8
8
  }
@@ -20,7 +20,7 @@ Apply these rules to all text that you write for a person to read: chat replies,
20
20
  - Use the plain word where a showy one comes to mind: "use", "show", "important", "examine", "is", and "has".
21
21
  - State the point directly, not as "not just X, but Y".
22
22
  - Use the real number of items, not a forced group of three.
23
- - Name the mechanism or the number, such as "a column rename fails the build", not the feeling.
23
+ - Name the mechanism or the number, such as "a column rename fails the build", not the feeling. Cut a sentence that could stand unchanged in the docs of another project.
24
24
  - Use the concrete word, not a metaphor noun such as "surface", "north star", or "substrate".
25
25
  - Remove filler, such as "in order to" and "it is important to note". Use one hedge at most.
26
26
  - Write whole sentences with their articles and verbs. Write words instead of arrows and abbreviations.
@@ -32,7 +32,6 @@ Apply these rules to all text that you write for a person to read: chat replies,
32
32
  - Use bold only for a UI label or a label that a template asks for.
33
33
  - A user reply is a chat reply, or a file that Git ignores and that you write for the user.
34
34
  - In a user reply, write one fact per line in a short list. Use prose only for reasoning that needs linked sentences.
35
- - In a user reply, list failures, results, skipped checks or risks, and neutral facts under a heading line of 🔴, 🟢, 🟡, or 🔵 and a short label. Put the groups in that order, with a blank line between them.
36
35
  - Do not use emoji in tracked files, commit messages, pull requests, or the output of code.
37
36
  - Use sentence case for headings.
38
37
  - Answer directly. Do not write chatbot phrases, such as "I hope this helps", or flattery.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "repository": "https://github.com/cursor/plugins",
3
3
  "path": "pstack/skills/unslop/SKILL.md",
4
- "commit": "a5539b15a3d56e04992565aafee2b37051329ce3",
4
+ "commit": "e58dd043600587dbaf58ba315e7f2b38373eeb43",
5
5
  "license": "MIT",
6
6
  "modified": true,
7
7
  "notes": "Condensed the unslop patterns into the Words and Format sections and rewrote them as rules. Stated the word patterns as the plain words to use, and left the list of words to avoid to scripts/lint-content.ts. The Sentences section is original, based on ASD-STE100, and is not from unslop."
@@ -1,6 +1,6 @@
1
1
  # AGENTS.md
2
2
 
3
- Instructions for AI coding agents in this repository. Codex and GitHub Copilot read this file directly, and Claude Code reads it through `CLAUDE.md`. Every line loads into every session, so keep it short and current.
3
+ Instructions for AI coding agents in this repository. GitHub Copilot reads this file directly, and Claude Code reads it through `CLAUDE.md`. Every line loads into every session, so keep it short and current.
4
4
 
5
5
  ## Project
6
6
 
@@ -58,6 +58,8 @@ Give one report for both passes, from most to least severe. Give a correctness f
58
58
  **Fix:** <smallest change that removes the problem>
59
59
  ```
60
60
 
61
+ When the caller asks for finding classes, read [`references/finding-classes.md`](references/finding-classes.md), and give each finding a class and a severity from it.
62
+
61
63
  End the report with this section. Write one line for each class of finding in the report. Prefer a tool that the repository already runs:
62
64
 
63
65
  ```markdown
@@ -4,5 +4,5 @@
4
4
  "commit": "a5539b15a3d56e04992565aafee2b37051329ce3",
5
5
  "license": "MIT",
6
6
  "modified": true,
7
- "notes": "Adapted into references/maintainability.md as the maintainability pass: kept code judo, the 1,000-line blocker, the smells, the presumed blockers, and the direct tone, rewrote the text under plugin/rules/writing.md, and gave each rule a severity. The Reader load, Domain model, and Scope sections condense pstack/skills/principle-minimize-reader-load, pstack/skills/principle-model-the-domain, and pstack/skills/principle-subtract-before-you-add at the same commit. SKILL.md and the correctness pass are original and are not from cursor/plugins."
7
+ "notes": "Adapted into references/maintainability.md as the maintainability pass: kept code judo, the 1,000-line blocker, the smells, the presumed blockers, and the direct tone, rewrote the text under rules/writing.md, and gave each rule a severity. The Reader load, Domain model, and Scope sections condense pstack/skills/principle-minimize-reader-load, pstack/skills/principle-model-the-domain, and pstack/skills/principle-subtract-before-you-add at the same commit. SKILL.md and the correctness pass are original and are not from cursor/plugins."
8
8
  }
@@ -0,0 +1,33 @@
1
+ # Finding classes
2
+
3
+ Give each finding exactly one class from this list, and one severity. Pick the class of the root cause, not of the symptom.
4
+
5
+ | Class | Meaning |
6
+ | ----- | ------- |
7
+ | `requirement-gap` | A requirement or an acceptance criterion of the spec has no code or no test that meets it. |
8
+ | `nn-breach` | The change breaks a non-negotiable (`NN`) of the spec. |
9
+ | `logic` | Wrong condition, operator, variable, or order, so the result is wrong. |
10
+ | `edge-case` | Empty, null, zero, very large, duplicate, or Unicode input gives a wrong result. |
11
+ | `error-handling` | An error is swallowed, a cleanup is missing, or a write can stop part of the way through. |
12
+ | `concurrency` | A race, a deadlock, or an assumption about the order of events. |
13
+ | `type-safety` | A cast, `any`, or a loose type hides the real contract. |
14
+ | `api-contract` | A changed signature, return shape, default, or response breaks a caller. |
15
+ | `performance` | Needless work, sequential work that can run in parallel, or a cost that grows with the input. |
16
+ | `security` | A vulnerability: injection, a missing authorization check, a secret in code or logs, or path traversal. |
17
+ | `test-gap` | Changed behavior has no test that fails when the change is wrong. |
18
+ | `duplication` | Copied logic, or a new helper next to an existing one that does the same job. |
19
+ | `naming` | A name that does not say what the code does. |
20
+ | `complexity` | Extra branches, layers, wrappers, or state that a simpler structure removes. |
21
+ | `dead-code` | Code that nothing calls, or code that is commented out. |
22
+ | `comment` | A comment that the `dot-comments` skill flags. |
23
+ | `docs-accuracy` | Docs that state a wrong fact, a wrong command, or a broken example. |
24
+ | `docs-style` | Docs with correct facts that break the writing rules or the style guide. |
25
+ | `accessibility` | UI that a keyboard, a screen reader, or a user with low vision cannot use. |
26
+ | `ux` | UI behavior that breaks a UX rule, such as a missing loading or error state. |
27
+ | `visual` | A visual defect in the rendered UI: layout, spacing, overflow, or contrast. |
28
+
29
+ ## Severity
30
+
31
+ - `high`: a wrong result, a crash, data loss, or a vulnerability in production. Also every `requirement-gap`, every `nn-breach`, and every presumed blocker of the maintainability pass.
32
+ - `medium`: a defect with a narrow scenario, or a smell of the maintainability pass.
33
+ - `low`: a cost for the reader only, such as `naming`, `comment`, and `docs-style`.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "repository": "https://github.com/cursor/plugins",
3
3
  "path": "pstack/skills/no-comments",
4
- "commit": "a5539b15a3d56e04992565aafee2b37051329ce3",
4
+ "commit": "e58dd043600587dbaf58ba315e7f2b38373eeb43",
5
5
  "license": "MIT",
6
6
  "modified": true,
7
7
  "notes": "Merged the policy from pstack/agents/comment-sicko.md into the skill and ran it inline instead of in a subagent. Replaced the /how, /why, and /architect calls with reading the code. Changed the per-flag approval to one approval of the whole report. Rewrote it in neutral wording and renamed it with the dot- prefix."