mirror of
https://github.com/automazeio/ccpm.git
synced 2025-10-09 13:41:06 +03:00
commit abf5bed203a9ac13579eac7c9299deee3b9c50c6 Author: Ran Aroussi <ranaroussi@users.noreply.github.com> Date: Wed Sep 24 18:46:43 2025 +0100 Refactor Bash command patterns in settings commit 1cc603ee2df72eb47b61df04b156dfadb70b5b58 Author: Ran Aroussi <ran@aroussi.com> Date: Wed Sep 24 15:23:43 2025 +0100 Remove outdated Chinese documentation files for agents, commands, and README to streamline project resources. commit 34d7e724e8159d5ec4aa6365940f355d8ed02872 Author: Ran Aroussi <ranaroussi@users.noreply.github.com> Date: Wed Sep 24 15:23:17 2025 +0100 Revise README with new badge links and documentation Updated links and added Chinese documentation reference. commit 0026086f7a118fd3c46161cde5becf52939ee6be Author: Ran Aroussi <ranaroussi@users.noreply.github.com> Date: Wed Sep 24 15:17:22 2025 +0100 RC => Main (stability and usability) (#954) * feat: Add automatic worktree directory fix via pre-tool-use hook Problem: Bash tool resets to main project directory after every command, breaking worktree operations for parallel agent development. Solution: Pre-tool-use hook that automatically detects worktree context and injects 'cd /path/to/worktree && ' prefix to all Bash commands. Features: - Zero-config: Agents don't need special instructions or awareness - Smart detection: Distinguishes worktrees (.git file) from repos (.git dir) - Edge case handling: Background processes, pipes, env vars, etc. - Debug mode: CLAUDE_HOOK_DEBUG=true for troubleshooting - Skip patterns: Avoids double-prefixing and unnecessary injections This enables true parallel development with multiple agents in different worktrees without any manual command prefixing or documentation burden. Tested via shell-shocked test suite: All 7 stress test scenarios passed. Or if you prefer a shorter version: feat: Auto-fix Bash tool worktree directory reset issue Implements pre-tool-use hook that transparently injects 'cd /worktree && ' prefix when operating in git worktrees. Handles background processes, pipes, and other edge cases. Agents need zero awareness of the fix. Enables parallel multi-agent development in worktrees without manual prefixing. * fix: script name in hooks README file * fix: make bash-worktree-fix POSIX-compliant * Update .claude/hooks/config.json Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * fix: improve bash worktree hook robustness and documentation - Fix critical bugs in worktree detection and command parsing: * Distinguish between git worktrees and submodules (check for /worktrees/ in gitdir path) * Fix TAB pattern bug using proper tokenization instead of brittle globbing * Fix overly broad dot-prefix skip that broke ./script.sh execution * Add proper path quoting to handle spaces and special characters * Capture all arguments with $* instead of just $1 - Improve documentation: * Remove personal paths from examples * Restructure troubleshooting steps for clarity * Switch from jq to python -m json.tool for wider compatibility * Clarify that hook config goes in main .claude/settings.json - Simplify configuration: * Remove redundant config.json * Add settings.json.example showing proper integration * Fix background process detection for both "cmd &" and "cmd&" patterns These changes prevent false positives on commands like "cdbuild", ensure relative scripts work in worktrees, and handle paths with spaces correctly. * docs: fix a path in the instructions for how to enable the bash worktree fix hook * fix: harden bash worktree hook against security vulnerabilities Security and robustness improvements to prevent shell injection and edge cases: - Prevent pathname expansion attacks by disabling globbing during tokenization * Commands like "echo *" no longer expand before parsing - Fix absolute path detection for environment-prefixed commands * Now correctly handles "VAR=1 /usr/bin/make" patterns - Implement secure path quoting using single quotes with proper escaping * Handles paths containing quotes, spaces, and special characters - Optimize .git file reading using shell built-ins instead of cat * Avoids subshell and only reads first line for efficiency - Improve debug mode to accept multiple truthy values (true/TRUE/1/yes/YES) - Add ShellCheck compliance with consistent variable bracing and default cases The hook now safely handles edge cases like: - Paths with single quotes: /path/to/joe's-project/ - Commands with wildcards that shouldn't expand - Mixed environment variables and absolute paths All changes maintain POSIX compatibility while significantly improving security posture and reliability. * refactor: improve worktree hook robustness and portability Major improvements to the bash worktree fix hook for better reliability: Validation & Safety: - Add gitdir path validation to verify the directory actually exists - Normalize relative gitdir paths to absolute for proper resolution - Add pwd directory check to handle edge cases - Use dirname with -- flag for safer path handling Portability: - Replace echo with printf throughout for consistent behavior - Use literal space/tab characters instead of [:space:] for POSIX compatibility - Rename shell_quote to shell_squote for clarity - Maintain set -f protection during pattern matching Simplification: - Streamline skip detection logic with cleaner patterns - Consolidate builtin command checks into single case statement - Remove unnecessary comments while keeping essential documentation - Cleaner whitespace detection using portable pattern The hook now properly validates that gitdir paths exist before treating them as worktrees, preventing false positives. Pattern matching is more portable across different POSIX shells, and printf usage eliminates echo's platform-specific quirks. All security improvements are retained: pathname expansion protection, proper single-quote escaping, and safe handling of background processes. * fix: restore [:space:] patterns and handle CRLF line endings Critical fixes and improvements to the bash worktree hook: Bug Fixes: - Handle CRLF line endings in .git files (Windows compatibility) * Strip trailing CR characters that break gitdir path parsing - Restore [:space:] character class for better Unicode support * Literal space/tab was too restrictive for international locales - Remove absolute path skip logic that broke many commands * Commands like `/usr/bin/npm install` still need correct cwd * Only skip builtins and commands that truly don't need directory context Performance: - Add fast-path exit when not in a worktree * Avoids unnecessary skip checks for common case - Remove redundant set -f globbing protection * Pattern matching doesn't trigger pathname expansion in case statements Clarity: - Streamline comments to be more concise - Quote original_command consistently - Better explain why absolute paths aren't skipped The hook now correctly handles Windows-created .git files with CRLF endings and properly supports all absolute-path commands that depend on the current working directory (which is most of them). * revert: remove dirname -- flag for broader compatibility Remove the '--' end-of-options flag from dirname command as it's not universally supported across all POSIX implementations. While '--' is good practice for handling filenames starting with dashes, dirname rarely encounters such edge cases in practice, and the compatibility issue is more pressing. Some older or minimal POSIX shells don't recognize '--' with dirname, causing the script to fail. Since we're already in a controlled loop walking up directory paths that come from pwd, the risk of dash-prefixed paths is negligible. Trade-off: Prioritizing compatibility over theoretical edge case protection. * Enhance context creation with comprehensive language detection Expand project detection capabilities to support 20+ programming languages and frameworks: - Add detection for JavaScript/TypeScript, Python (pyproject.toml), Java (Maven/Gradle), C#/.NET, Ruby, PHP, Dart/Flutter, Swift (including Xcode projects), C/C++, and Docker - Extend file type detection to include .ts, .jsx, .tsx, .kt, .cs, .rb, .php, .swift, .dart, .c, .h, .cpp, .hpp, and .sh files - Improve test detection to find both test directories and test files with common naming patterns (*test.*, *spec.*, test_*.*, *_test.*) - Exclude hidden directories in test detection for better performance This enhancement enables more accurate project analysis and better context creation across diverse development environments and technology stacks. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Expand comprehensive programming language support across all project components Complete systematic enhancement of language detection and build system support, following the comprehensive approach established in context/create.md: **Testing Framework Detection (.claude/commands/testing/prime.md):** - Add detection for PHP (PHPUnit, Pest), C#/.NET (MSTest, NUnit, xUnit), Java (JUnit/Maven/Gradle), Kotlin, Swift (XCTest), Dart/Flutter, C/C++ (GoogleTest, Catch2), Ruby (RSpec, Minitest) - Expand framework-specific configurations with proper commands and options - Add comprehensive dependency checking for all package managers - Include installation commands for all build systems (composer, mvn, gradle, dotnet, bundle, flutter, swift, ctest) - Add test file discovery patterns for all languages **Context Management Enhancement:** - Update dependency change detection in context/update.md for 11 build systems - Enhance context/prime.md project file analysis beyond basic detection - Maintain consistency with context/create.md comprehensive language support **Build System Integration:** - Expand pm/epic-merge.md test commands from 2 to 12 build systems - Add Maven, Gradle, Composer, .NET, Cargo, Go, Flutter, Swift, CMake support - Enable automated testing across all major development ecosystems **Infrastructure Support:** - Add bash permissions for 10 additional build tools in settings.local.json - Update process cleanup in test-execution.md and testing/run.md for all frameworks - Ensure consistent cross-language development workflow support This enhancement enables full development lifecycle support for 20+ programming languages and frameworks, providing consistent project detection, dependency management, testing, and build capabilities across diverse technology stacks. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Complete comprehensive programming language expansion with final enhancements Add final layer of language support improvements across infrastructure components: **Multi-Language Test Script (.claude/scripts/test-and-log.sh):** - Transform Python-only script to support 10+ languages and frameworks - Add intelligent test framework detection: Python (pytest), JavaScript/TypeScript (npm test, jest), Java (Maven, Gradle), C# (.NET), Ruby (RSpec), PHP (PHPUnit), Go, Rust, Swift, Dart/Flutter - Automatic file extension detection with appropriate test runner selection - Enhanced usage examples showing multi-language support **AST-Grep Language Reference (.claude/rules/use-ast-grep.md):** - Expand supported languages list from basic to comprehensive 50+ languages - Organize by categories: Primary Languages, Web & Markup, Configuration & Data, Shell & Scripts, and specialty languages - Add specific language codes for JavaScript/TypeScript variants, C/C++/C#, web frameworks (Vue, Svelte), and configuration formats (YAML, TOML, XML) **Issue Analysis Enhancement (.claude/commands/pm/issue-analyze.md):** - Generalize package.json references to support all project configuration files - Include build system coordination for Maven, Gradle, CMake, etc. **Test Runner Agent (.claude/agents/test-runner.md):** - Replace pytest-specific fallback with comprehensive multi-language fallback - Support framework detection and execution for all major testing ecosystems These enhancements complete the comprehensive language support initiative, ensuring consistent multi-language development workflow capabilities across all system components, from project detection to testing execution. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Fix ast-grep supported languages list to match official documentation Correct the ast-grep language support documentation to accurately reflect the actual 25 languages supported according to ast-grep.github.io: **Removed unsupported languages:** - Dart (not actually supported by ast-grep) - Vue, Svelte (framework-specific, not core languages) - SCSS, SASS, LESS (CSS preprocessors not supported) - TOML, XML (not in official support list) - PowerShell, shell variants beyond bash - OCaml and other languages incorrectly listed **Corrected to official 25 languages:** - System: C, C++, C#, Go, Rust - Web: JavaScript (js/jsx), TypeScript (ts), TSX, HTML, CSS, PHP - General: Python, Java, Kotlin, Ruby, Swift, Scala, Lua, Elixir, Haskell - Config: JSON, YAML - Other: Bash, Nix, Solidity **Updated examples:** - Use correct language aliases (js instead of javascript, ts instead of typescript) - Align with actual ast-grep command patterns This ensures accurate guidance for developers using ast-grep integration and prevents errors from referencing unsupported language identifiers. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Fix spelling error in README.md (#608) Bit of an inane PR but 🤷 * Fix path to install script in README.md (#570) * Add Chinese documentation and fix typo (#676) - Add Chinese documentation links in README.md, COMMANDS.md, and AGENTS.md - Fix typo: 'mutiple' -> 'multiple' in README.md - Include new Chinese documentation files in doc/ directory 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude <noreply@anthropic.com> * Fix: Prevent local file paths exposure in GitHub issue comments (#631) * Fix privacy issue: Add path standards validation and normalization - Add .claude/rules/path-standards.md with comprehensive path usage guidelines - Add .claude/scripts/check-path-standards.sh for automated validation - Add .claude/scripts/fix-path-standards.sh for automatic path normalization - Add documentation for path standards tools Addresses issue #630: Prevents local file paths from being exposed in GitHub issue comments, maintaining privacy and portability. Features: - Automatic detection of absolute path violations - Safe path normalization with backup support - Comprehensive validation with colored output - CI/CD integration ready - Cross-platform support (Unix/Windows paths) Author: Zephyr <zephyrTang@aliyun.com> * Fix PR feedback: Improve scripts and documentation - Enhanced shell error handling with 'set -Eeuo pipefail' - Fixed Windows path patterns in regex expressions - Added exclusions for rules and backup files to prevent false positives - Converted all Chinese text to English in documentation - Corrected path examples in standards documentation - Improved script robustness and cross-platform compatibility Addresses feedback from CodeRabbit AI and GitHub Copilot reviews. Author: Zephyr <zephyrTang@aliyun.com> * Polish: Final micro-optimizations for PR feedback - Fixed grammar issues in path-tools-README.md per LanguageTool feedback - Corrected path transformation examples in path-standards.md to match actual implementation - Ensured consistency between documentation examples and script behavior - Minor improvements for production-ready code quality All CodeRabbit AI and GitHub Copilot feedback addressed. Author: Zephyr <zephyrTang@aliyun.com> --------- Co-authored-by: dengzefeng <zephyr@shopline.com> * Fix: Ensure GitHub issues are created in correct repository (#532) - Add explicit --repo flag to all gh issue create commands - Create repository detection configuration file - Handle both SSH and HTTPS git remote formats - Add validation and error handling for repository detection This prevents issues from being created in automazeio/ccpm instead of the user's actual repository. Co-authored-by: jodagreyhame <jodagreyhame@users.noreply.github.com> * Major Cleanup & Issue Resolution - 2025-01-24 (#953) * feat: Major cleanup and issue resolution - 2025-01-24 release ✨ NEW FEATURES: - Add comprehensive LOCAL_MODE.md guide for offline workflow - Auto-create GitHub labels (epic, task) during init - Modernize PM command syntax with !bash pattern - Add context accuracy safeguards with self-verification - Create comprehensive CHANGELOG.md documentation 🔧 IMPROVEMENTS: - Update 4 core PM commands to use efficient !bash syntax - Enhance init.sh with automatic GitHub label creation - Document context accuracy improvements in CONTEXT_ACCURACY.md - Streamline command definitions for better token efficiency 📊 IMPACT: - Resolves 10+ GitHub issues with comprehensive solutions - Enables true local-only development workflow - Reduces AI hallucination in context generation - Improves Claude Code compatibility and performance 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * fix: improve GitHub detection and error handling in init.sh Address GitHub Copilot feedback for better robustness: 🔧 IMPROVED REPOSITORY DETECTION: - Replace string matching with `gh repo view` for robust detection - Handles SSH URLs, GitHub Enterprise, and edge cases properly - Graceful fallback for non-GitHub repositories 🛡️ ENHANCED ERROR HANDLING: - Replace silent failures with meaningful user feedback - Track label creation success/failure individually - Check for existing labels before reporting errors - Clear status messages: success, partial, or failure 🧪 TESTED: - Bash syntax validation passed - Repository detection logic verified - Error handling scenarios tested Addresses high and medium priority feedback from Copilot review. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com> * Complete Directory Restructure & PM Command Modernization - Restructure from .claude/ to ccpm/ directory - Update all PM commands to use !bash execution syntax - Modernize command frontmatter for better token efficiency - Complete the missing directory restructuring from previous PRs This completes the architectural shift to the ccpm/ template structure. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * fix: correct script paths from .claude/ to ccpm/ in all PM commands All PM commands now properly reference ccpm/scripts/pm/ instead of the old .claude/scripts/pm/ paths. This completes the directory restructure that was partially implemented. - Fixed 28 script path references across all PM command files - Commands now correctly point to ccpm/scripts/pm/ location - Resolves issue where PM commands couldn't find their scripts 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Update installation script URLs in README files - Changed installation script URLs from GitHub raw links to direct links at automaze.io for improved reliability. - Updated both English and Chinese README files to reflect the new URLs. - Ensured consistency across Unix/Linux/macOS and Windows installation instructions. This change enhances the user experience by providing a more stable source for installation scripts. 🤖 Generated with [Claude Code](https://claude.ai/code) * Update installation script URLs in README files to point to the new install path - Changed installation script URLs from the old path to the new `/install` path for improved clarity and reliability. - Updated both English and Chinese README files to reflect the new URLs. - Ensured consistency across Unix/Linux/macOS and Windows installation instructions. This change enhances the user experience by providing a clear and stable source for installation scripts. --------- Co-authored-by: James Ross <james@flyingrobots.dev> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Co-authored-by: Steven <tseven@gmail.com> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Connor Adams <connorads@users.noreply.github.com> Co-authored-by: Stefan Legg <legg.stefan@gmail.com> Co-authored-by: cyxer000 <48980829+cyxer000@users.noreply.github.com> Co-authored-by: Aka mo <56784262+ZephyrDeng@users.noreply.github.com> Co-authored-by: dengzefeng <zephyr@shopline.com> Co-authored-by: jodagreyhame <66655312+jodagreyhame@users.noreply.github.com> Co-authored-by: jodagreyhame <jodagreyhame@users.noreply.github.com>
3.7 KiB
3.7 KiB
代理
专门处理繁重工作的代理,返回简洁摘要以保留上下文。
核心理念
"不要将子代理拟人化。使用它们来组织你的提示并省略上下文。当子代理能够完成大量工作但只向主线程提供少量信息时效果最佳。"
– Adam Wolff, Anthropic
可用代理
🔍 code-analyzer
- 目的: 跨多个文件查找错误而不污染主线程上下文
- 模式: 搜索多个文件 → 分析代码 → 返回错误报告
- 用法: 当你需要追踪逻辑流、查找错误或验证更改时
- 返回: 仅包含关键发现的简洁错误报告
📄 file-analyzer
- 目的: 读取和总结详细文件(日志、输出、配置)
- 模式: 读取文件 → 提取见解 → 返回摘要
- 用法: 当你需要理解日志文件或分析详细输出时
- 返回: 关键发现和可操作的见解(减少80-90%的大小)
🧪 test-runner
- 目的: 执行测试而不将输出转储到主线程
- 模式: 运行测试 → 捕获到日志 → 分析结果 → 返回摘要
- 用法: 当你需要运行测试并理解失败原因时
- 返回: 包含失败分析的测试结果摘要
🔀 parallel-worker
- 目的: 协调处理问题的多个并行工作流
- 模式: 读取分析 → 生成子代理 → 整合结果 → 返回摘要
- 用法: 当在工作树中执行并行工作流时
- 返回: 所有并行工作的整合状态
为什么使用代理?
代理是保护主线程免受信息过载的上下文防火墙:
不使用代理:
主线程读取10个文件 → 上下文爆炸 → 失去连贯性
使用代理:
代理读取10个文件 → 主线程获得1个摘要 → 上下文得以保留
代理如何保留上下文
- 繁重工作 - 代理完成繁琐的工作(读取文件、运行测试、实现功能)
- 上下文隔离 - 实现细节保留在代理中,不在主线程
- 简洁返回 - 只有必要信息返回到主线程对话
- 并行执行 - 多个代理可以同时工作而不会产生上下文冲突
使用示例
# 分析代码查找错误
任务: "在代码库中搜索内存泄漏"
代理: code-analyzer
返回: "发现3个潜在泄漏: [简洁列表]"
主线程不会看到: 检查的数百个文件
# 运行测试
任务: "运行身份验证测试"
代理: test-runner
返回: "10个测试中有2个失败: [失败摘要]"
主线程不会看到: 详细的测试输出和日志
# 并行实现
任务: "使用并行流实现问题#1234"
代理: parallel-worker
返回: "完成4/4个流,修改了15个文件"
主线程不会看到: 单个实现细节
创建新代理
新代理应遵循以下原则:
- 单一目的 - 每个代理都有一个明确的工作
- 上下文缩减 - 返回处理内容的10-20%
- 不角色扮演 - 代理不是"专家",而是任务执行器
- 清晰模式 - 定义输入 → 处理 → 输出模式
- 错误处理 - 优雅地处理失败并清晰报告
需避免的反模式
❌ 创建"专家"代理 (数据库专家、API专家) 代理没有不同的知识 - 它们都是相同的模型
❌ 返回详细输出 违背了上下文保留的目的
❌ 让代理相互沟通 应该使用协调代理(如parallel-worker)
❌ 为简单任务使用代理 只有当上下文缩减有价值时才使用代理
与PM系统的集成
代理与PM命令系统无缝集成:
/pm:issue-analyze→ 识别工作流/pm:issue-start→ 生成parallel-worker代理- parallel-worker → 生成多个子代理
- 子代理 → 在工作树中并行工作
- 结果 → 整合回主线程
这创建了一个层次结构,在每个级别都最大化并行性同时保留上下文。