rulesync 4.3.1 → 5.0.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.
package/README.md CHANGED
@@ -135,11 +135,10 @@ Rulesync supports both **generation** and **import** for All of the major AI cod
135
135
  | GitHub Copilot | ✅ | | ✅ | ✅ | ✅ | ✅ |
136
136
  | Cursor | ✅ | ✅ | ✅ | ✅ 🌏 | 🎮 | ✅ |
137
137
  | OpenCode | ✅ | | ✅ | ✅ 🌏 | ✅ 🌏 | ✅ 🌏 |
138
- | Cline | ✅ | ✅ | ✅ | | | |
139
- | Roo Code | ✅ | ✅ | ✅ | ✅ | 🎮 | |
138
+ | Cline | ✅ | ✅ | ✅ | ✅ 🌏 | | |
139
+ | Roo Code | ✅ | ✅ | ✅ | ✅ | 🎮 | ✅ 🌏 |
140
140
  | Qwen Code | ✅ | ✅ | | | | |
141
141
  | Kiro IDE | ✅ | ✅ | | | | |
142
- | Amazon Q Developer CLI | ✅ | | ✅ | | | |
143
142
  | Google Antigravity | ✅ | | | ✅ | | |
144
143
  | JetBrains Junie | ✅ | ✅ | ✅ | | | |
145
144
  | AugmentCode | ✅ | ✅ | | | | |
@@ -787,39 +786,6 @@ Add the Rulesync MCP server to your `.rulesync/mcp.json`:
787
786
  }
788
787
  ```
789
788
 
790
- ## Contributing
791
-
792
- Issues and Pull Requests are welcome!
793
-
794
- For development setup:
795
-
796
- ```bash
797
- git clone https://github.com/dyoshikawa/rulesync # Should be your fork repository url actually
798
- cd rulesync
799
- pnpm i
800
- pnpm cicheck # Run code style check, type check, and tests
801
-
802
- # Manual test using current code
803
- pnpm dev generate -t claudecode -f "*"
804
- pnpm dev import -t claudecode -f "*"
805
-
806
- # Once you create .rulesync/rules/my-language.md and `pnpm dev generate`, you can use coding agents with your language.
807
- # Japanese setting example:
808
- cat << 'EOF' > .rulesync/rules/my-language.md
809
- ---
810
- root: false
811
- targets: ['*']
812
- description: "It's a rule about language. If the rule file exists, you must always follow this."
813
- globs: ["**/*"]
814
- ---
815
-
816
- I'm a Japanese developer. So you must always answer in Japanese. On the other hand, reasoning(thinking) should be in English to improve token efficiency.
817
-
818
- However, this project is for English speaking people. So when you write any code, comments, documentation, commit messages, PR title and PR descriptions, you must always use English.
819
- EOF
820
- pnpm dev generate
821
- ```
822
-
823
789
  ## FAQ
824
790
 
825
791
  ### Q. The generated `.mcp.json` doesn't work properly in Claude Code.