tools-cc 1.0.3 → 1.0.4

package/CHANGELOG.md

@@ -2,6 +2,14 @@
 
 本项目的所有重要变更都将记录在此文件中。
 
+## [1.0.4] - 2026-02-28
+
+### Added
+- 新增英文版项目说明文档 README_en.md
+
+### Changed
+- 优化项目初始化与源码同步逻辑
+
 ## [1.0.3] - 2026-02-26
 
 ### Changed

package/CHANGELOG_en.md

@@ -0,0 +1,71 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [1.0.4] - 2026-02-28
+
+### Added
+- Added English version of project documentation README_en.md
+
+### Changed
+- Optimized project initialization and source synchronization logic
+
+## [1.0.3] - 2026-02-26
+
+### Changed
+- Changed project configuration file location from `tools-cc.json` to `.toolscc/config.json`
+- Improved documentation command descriptions, clearly distinguishing global and project commands
+
+## [1.0.2] - 2026-02-26
+
+### Added
+- Added `tools-cc -s scan` command: scan sourcesDir directory to auto-discover and add configuration sources
+- Added `tools-cc -s upgrade [name]` command alias: execute git pull to update configuration source code
+- Added `tools-cc update [sources...]` command: sync configuration source content to project .toolscc directory
+
+### Changed
+- Improved help documentation, added workflow guide and command comparison table
+
+## [1.0.1] - 2026-02-25
+
+### Added
+- Added package.json repository metadata (repository, bugs, homepage)
+
+## [1.0.0] - 2026-02-25
+
+### Added
+- Project initialization, built CLI framework based on TypeScript + Commander
+- Global configuration management module
+  - `tools-cc -c set <key> <value>` set configuration
+  - `tools-cc -c get <key>` get configuration
+  - `tools-cc config list` view complete configuration
+- Configuration source management module
+  - `tools-cc -s add <name> <path-or-url>` add configuration source (supports Git URL and local path)
+  - `tools-cc -s list` list all configuration sources
+  - `tools-cc -s remove <name>` remove configuration source
+  - `tools-cc -s update [name]` update configuration source (git pull)
+- Project management module
+  - `tools-cc use [sources...]` enable configuration sources and create symbolic links
+  - `tools-cc list` list enabled configuration sources
+  - `tools-cc rm <source>` disable configuration source
+  - `tools-cc status` view project status
+- Symbolic link management module (supports Windows Junction)
+- Manifest loading and scanning module
+- Bilingual help information (Chinese/English) (`tools-cc help`)
+- Unit test coverage (vitest)
+
+### Supported Tools
+| Tool | Link Name |
+|------|-----------|
+| iflow | `.iflow` |
+| claude | `.claude` |
+| codebuddy | `.codebuddy` |
+| opencode | `.opencode` |
+
+---
+
+## Versioning
+
+- **Major version**: Incompatible API changes
+- **Minor version**: Backwards-compatible functionality additions
+- **Patch version**: Backwards-compatible bug fixes

package/README_en.md

@@ -0,0 +1,218 @@
+# tools-cc
+
+A CLI tool for unified management of skills/commands/agents configurations across multiple AI programming tools (iflow, claude, codebuddy, opencode, etc.). Uses symbolic links to avoid duplicate configurations across tools.
+
+## Installation
+
+```bash
+# Install from npm
+npm install -g tools-cc
+
+# Or build from source
+git clone https://github.com/q759410559/tools-cc.git
+cd tools-cc
+npm install
+npm run build
+npm link
+```
+
+## Quick Start
+
+```bash
+# 1. Set configuration source storage location (optional, default is ~/.tools-cc/sources)
+tools-cc -c set sourcesDir D:/skills-hub-sources
+
+# 2. Add configuration sources (supports Git URL or local path)
+tools-cc -s add my-skills https://github.com/user/my-skills.git
+tools-cc -s add local-skills D:/path/to/local-skills
+
+# Or scan source directory to auto-discover and add configurations
+tools-cc -s scan
+
+# 3. View added configuration sources
+tools-cc -s list
+
+# 4. Enable configuration sources in a project and create links
+cd my-project
+tools-cc use my-skills -p iflow claude
+
+# 5. View project status
+tools-cc status
+
+# 6. View enabled configuration sources
+tools-cc list
+
+# 7. Update configuration sources (sync latest content from source directory to project)
+tools-cc update my-skills
+tools-cc update              # Update all
+
+# 8. Remove configuration source
+tools-cc rm my-skills
+```
+
+## Workflow Guide
+
+### Global Source Management vs Project Configuration
+
+| Command | Scope | Description |
+|---------|-------|-------------|
+| `tools-cc -s add/remove/list` | Global | Manage global configuration sources |
+| `tools-cc -s update/upgrade` | Global | git pull to update source code |
+| `tools-cc -s scan` | Global | Scan directory to discover new sources |
+| `tools-cc use/rm` | Project | Enable/disable sources in project |
+| `tools-cc update` | Project | Sync source content to project |
+
+### Typical Workflow
+
+```bash
+# Scenario 1: Configuration source has updates, need to sync to project
+tools-cc -s upgrade my-skills    # 1. git pull to update source code
+cd my-project
+tools-cc update my-skills        # 2. Sync to project .toolscc directory
+
+# Scenario 2: Batch update all sources
+tools-cc -s upgrade              # 1. Update all git sources
+cd my-project
+tools-cc update                  # 2. Sync all sources to project
+```
+
+## Command Reference
+
+### Source Management
+
+```bash
+# Shortcuts (-s)
+tools-cc -s add <name> <path-or-url>     # Add configuration source (Git URL or local path)
+tools-cc -s list                          # List all configuration sources (alias: -s ls)
+tools-cc -s remove <name>                 # Remove configuration source (alias: -s rm)
+tools-cc -s update [name]                 # git pull to update source code (alias: -s up, -s upgrade)
+tools-cc -s scan                          # Scan sourcesDir to auto-discover and add configuration sources
+
+# Full commands (sources)
+tools-cc sources add <name> <path-or-url> # Add configuration source
+tools-cc sources list                     # List all configuration sources (alias: sources ls)
+tools-cc sources remove <name>            # Remove configuration source (alias: sources rm)
+tools-cc sources update [name]            # git pull to update source code (alias: sources up, sources upgrade)
+tools-cc sources scan                     # Scan sourcesDir to auto-discover and add configuration sources
+```
+
+### Project Configuration
+
+```bash
+tools-cc use [sources...] [-p tools...]   # Enable configuration sources and create symbolic links
+tools-cc update [sources...]              # Sync configuration source content to project .toolscc directory
+tools-cc list                             # List enabled configuration sources
+tools-cc rm <source>                      # Disable configuration source
+tools-cc status                           # View project status
+```
+
+### Config Management
+
+```bash
+# Shortcuts (-c)
+tools-cc -c set <key> <value>             # Set configuration
+tools-cc -c get <key>                     # Get configuration
+
+# Full commands (config)
+tools-cc config set <key> <value>         # Set configuration
+tools-cc config get <key>                 # Get configuration
+tools-cc config list                      # View complete global configuration
+```
+
+### Help
+
+```bash
+tools-cc help                             # Display bilingual help (Chinese/English)
+tools-cc --help                           # Display command line help
+tools-cc --version                        # Display version number
+```
+
+## Supported Tools
+
+| Tool | Link Name |
+|------|-----------|
+| iflow | `.iflow` |
+| claude | `.claude` |
+| codebuddy | `.codebuddy` |
+| opencode | `.opencode` |
+
+## Configuration Source Structure
+
+A configuration source directory should contain the following structure:
+
+```
+my-skills/
+├── manifest.json          # Optional, describes component information
+├── skills/
+│   └── my-skill/
+│       └── SKILL.md
+├── commands/
+│   └── my-command.md
+└── agents/
+    └── my-agent.md
+```
+
+### manifest.json Format
+
+```json
+{
+  "name": "my-skills",
+  "version": "1.0.0",
+  "skills": ["my-skill"],
+  "commands": ["my-command"],
+  "agents": ["my-agent"]
+}
+```
+
+If `manifest.json` is not present, the CLI will automatically scan the directory structure to generate one.
+
+## Project Structure
+
+After using `tools-cc use`, the project directory structure:
+
+```
+my-project/
+├── .toolscc/                     # Actual content directory
+│   ├── config.json               # Project configuration
+│   ├── skills/                   # Flattened, with source prefix
+│   │   └── my-skills-my-skill/
+│   ├── commands/
+│   │   └── my-skills/
+│   └── agents/
+│       └── my-skills/
+├── .iflow -> .toolscc            # Symbolic link
+└── .claude -> .toolscc
+```
+
+## Configuration Files
+
+### Global Configuration `~/.tools-cc/config.json`
+
+```json
+{
+  "sourcesDir": "D:/skills-hub-sources",
+  "sources": {
+    "my-skills": {
+      "type": "git",
+      "url": "https://github.com/user/my-skills.git"
+    },
+    "local-skills": {
+      "type": "local",
+      "path": "D:/local-skills"
+    }
+  }
+}
+```
+
+### Project Configuration `project/.toolscc/config.json`
+
+```json
+{
+  "sources": ["my-skills"],
+  "links": ["iflow", "claude"]
+}
+```
+
+## License
+
+MIT

package/dist/core/project.js

@@ -46,7 +46,8 @@ async function useSource(sourceName, sourceDir, projectDir) {
         const skills = await fs_extra_1.default.readdir(sourceSkillsDir);
         for (const skill of skills) {
             const srcPath = path_1.default.join(sourceSkillsDir, skill);
-            const destPath = path_1.default.join(toolsccDir, 'skills', `${sourceName}-${skill}`);
+            const name = `${sourceName}` == `${skill}` ? skill : `${sourceName}-${skill}`;
+            const destPath = path_1.default.join(toolsccDir, 'skills', name);
             // Remove existing if exists
             await fs_extra_1.default.remove(destPath);
             // Copy directory

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tools-cc",
-  "version": "1.0.3",
+  "version": "1.0.4",
   "description": "tools-cc [options] <command> [args]",
   "main": "index.js",
   "directories": {
@@ -11,7 +11,8 @@
     "dev": "ts-node src/index.ts",
     "start": "node dist/index.js",
     "test": "vitest",
-    "test:run": "vitest run"
+    "test:run": "vitest run",
+    "release": "npm publish && git tag v%npm_package_version% && git push origin v%npm_package_version% && gh release create v%npm_package_version% --title v%npm_package_version% --generate-notes"
   },
   "bin": {
     "tools-cc": "./dist/index.js"

package/src/core/project.ts

@@ -7,12 +7,12 @@ import { getToolsccDir, getProjectConfigPath } from '../utils/path';
 export async function initProject(projectDir: string): Promise<void> {
   const toolsccDir = getToolsccDir(projectDir);
   const configFile = getProjectConfigPath(projectDir);
-  
+
   // Create .toolscc directory structure
   await fs.ensureDir(path.join(toolsccDir, 'skills'));
   await fs.ensureDir(path.join(toolsccDir, 'commands'));
   await fs.ensureDir(path.join(toolsccDir, 'agents'));
-  
+
   // Create project config if not exists
   if (!(await fs.pathExists(configFile))) {
     const config: ProjectConfig = {
@@ -32,34 +32,35 @@ export async function useSource(
   if (!sourceName || !sourceName.trim()) {
     throw new Error('Source name is required');
   }
-  
+
   // Check source directory existence
   if (!(await fs.pathExists(sourceDir))) {
     throw new Error(`Source directory does not exist: ${sourceDir}`);
   }
-  
+
   const toolsccDir = getToolsccDir(projectDir);
   const manifest = await loadManifest(sourceDir);
-  
+
   // Ensure project is initialized
   await initProject(projectDir);
-  
+
   // Copy/link skills (flattened with prefix)
   const sourceSkillsDir = path.join(sourceDir, 'skills');
   if (await fs.pathExists(sourceSkillsDir)) {
     const skills = await fs.readdir(sourceSkillsDir);
     for (const skill of skills) {
       const srcPath = path.join(sourceSkillsDir, skill);
-      const destPath = path.join(toolsccDir, 'skills', `${sourceName}-${skill}`);
-      
+      const name = `${sourceName}` == `${skill}` ? skill : `${sourceName}-${skill}`;
+      const destPath = path.join(toolsccDir, 'skills', name);
+
       // Remove existing if exists
       await fs.remove(destPath);
-      
+
       // Copy directory
       await fs.copy(srcPath, destPath);
     }
   }
-  
+
   // Copy commands (in subdirectory by source name)
   const sourceCommandsDir = path.join(sourceDir, 'commands');
   if (await fs.pathExists(sourceCommandsDir)) {
@@ -67,7 +68,7 @@ export async function useSource(
     await fs.remove(destDir);
     await fs.copy(sourceCommandsDir, destDir);
   }
-  
+
   // Copy agents (in subdirectory by source name)
   const sourceAgentsDir = path.join(sourceDir, 'agents');
   if (await fs.pathExists(sourceAgentsDir)) {
@@ -75,7 +76,7 @@ export async function useSource(
     await fs.remove(destDir);
     await fs.copy(sourceAgentsDir, destDir);
   }
-  
+
   // Update project config
   const configFile = getProjectConfigPath(projectDir);
   const config: ProjectConfig = await fs.readJson(configFile);
@@ -90,10 +91,10 @@ export async function unuseSource(sourceName: string, projectDir: string): Promi
   if (!sourceName || !sourceName.trim()) {
     throw new Error('Source name is required');
   }
-  
+
   const toolsccDir = getToolsccDir(projectDir);
   const configFile = getProjectConfigPath(projectDir);
-  
+
   // Remove skills with prefix
   const skillsDir = path.join(toolsccDir, 'skills');
   if (await fs.pathExists(skillsDir)) {
@@ -104,13 +105,13 @@ export async function unuseSource(sourceName: string, projectDir: string): Promi
       }
     }
   }
-  
+
   // Remove commands subdirectory
   await fs.remove(path.join(toolsccDir, 'commands', sourceName));
-  
+
   // Remove agents subdirectory
   await fs.remove(path.join(toolsccDir, 'agents', sourceName));
-  
+
   // Update project config with error handling
   let config: ProjectConfig;
   try {
@@ -119,18 +120,18 @@ export async function unuseSource(sourceName: string, projectDir: string): Promi
     // If config file doesn't exist or is invalid, nothing to update
     return;
   }
-  
+
   config.sources = config.sources.filter(s => s !== sourceName);
   await fs.writeJson(configFile, config, { spaces: 2 });
 }
 
 export async function listUsedSources(projectDir: string): Promise<string[]> {
   const configFile = getProjectConfigPath(projectDir);
-  
+
   if (!(await fs.pathExists(configFile))) {
     return [];
   }
-  
+
   const config: ProjectConfig = await fs.readJson(configFile);
   return config.sources;
 }