rulesync 0.68.1 → 0.70.0

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 (4) hide show
  1. package/README.md +116 -9
  2. package/dist/index.cjs +916 -983
  3. package/dist/index.js +912 -979
  4. package/package.json +4 -4
package/README.md CHANGED
@@ -83,15 +83,7 @@ Team members can freely choose their preferred AI coding tools. Whether it's Git
83
83
  AI development tools evolve rapidly with new tools emerging frequently. With rulesync, switching between tools doesn't require redefining your rules from scratch.
84
84
 
85
85
  ### 🎯 **Multi-Tool Workflow**
86
- Enable hybrid development workflows combining multiple AI tools:
87
- - **GitHub Copilot** for code completion and inline suggestions
88
- - **Cursor** for intelligent refactoring and project-wide changes
89
- - **Claude Code** for architecture design and complex problem solving
90
- - **Cline** for autonomous debugging and file system operations
91
- - **Amazon Q Developer CLI** for comprehensive chat-based development with built-in commands and MCP integration
92
- - **OpenCode** for secure terminal-based development with granular permission controls
93
- - **Windsurf** for comprehensive AI-assisted editing with Cascade AI
94
- - **Gemini CLI** for Google AI integration and custom workflows
86
+ Enable hybrid development workflows combining multiple AI tools.
95
87
 
96
88
  ### 🔓 **No Lock-in**
97
89
  Avoid lock-in completely. If you decide to stop using rulesync, you can continue using the generated rule files as-is.
@@ -126,6 +118,8 @@ npx rulesync gitignore
126
118
 
127
119
  You can configure rulesync by creating a `rulesync.jsonc` file in the root of your project.
128
120
 
121
+ Example:
122
+
129
123
  ```jsonc
130
124
  // rulesync.jsonc
131
125
  {
@@ -146,6 +140,119 @@ You can configure rulesync by creating a `rulesync.jsonc` file in the root of yo
146
140
  }
147
141
  ```
148
142
 
143
+ ## Each File Format
144
+
145
+ ### `rulesync/rules/*.md`
146
+
147
+ Example:
148
+
149
+ ```md
150
+ ---
151
+ root: true # true that is less than or equal to one file for overview such as AGENTS.md, false for details such as .agents/memories/*.md
152
+ targets: ["*"] # * = all, or specific tools
153
+ description: "rulesync project overview and development guidelines for unified AI rules management CLI tool"
154
+ globs: ["**/*"] # file patterns to match (e.g., ["*.md", "*.txt"])
155
+ cursor: # for cursor-specific rules
156
+ alwaysApply: true
157
+ description: "rulesync project overview and development guidelines for unified AI rules management CLI tool"
158
+ globs: ["*"]
159
+ ---
160
+
161
+ # rulesync Project Overview
162
+
163
+ This is rulesync, a Node.js CLI tool that automatically generates configuration files for various AI development tools from unified AI rule files. The project enables teams to maintain consistent AI coding assistant rules across multiple tools.
164
+
165
+ ...
166
+ ```
167
+
168
+ ### `rulesync/commands/*.md`
169
+
170
+ Example:
171
+
172
+ ```md
173
+ ---
174
+ description: 'Review a pull request' # command description
175
+ targets: ["*"] # * = all, or specific tools
176
+ ---
177
+
178
+ target_pr = $ARGUMENTS
179
+
180
+ If target_pr is not provided, use the PR of the current branch.
181
+
182
+ Execute the following in parallel:
183
+
184
+ ...
185
+ ```
186
+
187
+ ### `rulesync/subagents/*.md`
188
+
189
+ Example:
190
+
191
+ ```md
192
+ ---
193
+ name: planner # subagent name
194
+ targets: ["*"] # * = all, or specific tools
195
+ description: >- # subagent description
196
+ This is the general-purpose planner. The user asks the agent to plan to
197
+ suggest a specification, implement a new feature, refactor the codebase, or
198
+ fix a bug. This agent can be called by the user explicitly only.
199
+ claudecode: # for claudecode-specific rules
200
+ model: opus # opus, sonnet, haiku or inherit
201
+ ---
202
+
203
+ You are the planner for any tasks.
204
+
205
+ Based on the user's instruction, create a plan while analyzing the related files. Then, report the plan in detail. You can output files to @tmp/ if needed.
206
+
207
+ Attention, again, you are just the planner, so though you can read any files and run any commands for analysis, please don't write any code.
208
+ ```
209
+
210
+ ### `.rulesync/.mcp.json`
211
+
212
+ Example:
213
+
214
+ ```json
215
+ {
216
+ "mcpServers": {
217
+ "serena": {
218
+ "type": "stdio",
219
+ "command": "uvx",
220
+ "args": [
221
+ "--from",
222
+ "git+https://github.com/oraios/serena",
223
+ "serena",
224
+ "start-mcp-server",
225
+ "--context",
226
+ "ide-assistant",
227
+ "--enable-web-dashboard",
228
+ "false",
229
+ "--project",
230
+ "."
231
+ ],
232
+ "env": {}
233
+ },
234
+ "context7": {
235
+ "type": "stdio",
236
+ "command": "npx",
237
+ "args": [
238
+ "-y",
239
+ "@upstash/context7-mcp"
240
+ ],
241
+ "env": {}
242
+ }
243
+ }
244
+ }
245
+ ```
246
+
247
+ ### `.rulesyncignore`
248
+
249
+ Example:
250
+
251
+ ```ignore
252
+ tmp/
253
+ credentials/
254
+ ```
255
+
149
256
  ## License
150
257
 
151
258
  MIT License