makecoder 1.0.25

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 MakeCoder
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,281 @@
+# Coder 超级编程智能体
+
+## 简介
+
+**Coder** 是 MakeCoder 平台的核心生产力工具。它是一个运行在终端的**超级编程智能体**。
+
+* **多智能体引擎 (Multi-Agent)**：内置并自动调度 **Claude Code**, **Codex CLI**, **Gemini CLI** 等顶尖编程引擎。
+* **零配置 (Zero-Config)**：无需配置Claude Code等，开箱即用。
+* **全栈能力**：支持文件读写、命令执行、代码重构与自动排错。
+
+ ![](https://makecoder.com/wiki/api/attachments.redirect?id=eb3939cf-97d7-49c3-ad58-deaaabc42916)
+
+## 环境准备
+
+在安装 Coder 之前，请确保您的电脑满足以下要求。
+
+### Node.js 环境 (必须)
+
+Coder 依赖 Node.js 运行。推荐安装 **v20 或更高版本**。
+
+| 操作系统 | 安装方式 |
+|:---|:---|
+| **macOS** | 推荐使用 Homebrew: `brew install node` |
+| **Windows** | 访问 [Node.js 官网](https://nodejs.org/) 下载安装包 (LTS版本) |
+| **Linux** | 使用 apt: `sudo apt install nodejs npm` 或使用 nvm 管理 |
+
+> 🤖 **遇到困难？** [点击查看 AI 详细安装指导](https://makecoder.com/chat/share/0aeb363f-334e-4fc9-b59c-c70d5003d371)
+
+### Git Bash (Windows 用户必读)
+
+如果您使用的是 Windows 系统，**强烈建议**安装并使用 **Git Bash** 作为默认终端，以获得最佳的交互体验。
+
+
+1. **安装 Git Bash** (如果未安装): 打开 PowerShell 运行:
+
+   ```powershell
+   winget install --id Git.Git -e
+   ```
+2. **使用提示**: 安装完成后，请在 **Git Bash** 窗口中运行后续的所有 `npm` 和 `coder` 命令。
+
+> 🤖 **遇到困难？** [点击查看 Windows 环境配置 AI 解答](https://makecoder.com/chat/share/d2955b52-3da4-4ece-b71c-c0bccc3747d5)
+
+
+-----
+
+## 下载与安装
+
+### 安装 Coder CLI
+
+使用 npm 全局安装最新版 Coder：
+
+```bash
+npm install -g makecoder
+```
+
+* `-g`: 表示全局安装，允许在任何目录下使用 `coder` 命令。
+* `makecoder`: MakeCoder 官方 npm 包。
+* [国内 npm 安装加速](https://makecoder.com/chat/share/bf28a2af-4a39-4881-89c0-2552450c6c74)
+
+**验证安装**:
+
+```bash
+coder --version
+# 输出示例: 1.0.6
+```
+
+### 账号认证
+
+连接 Coder 到您的 MakeCoder 云端账户。
+
+
+1. 登录 [MakeCoder 控制台](https://makecoder.com/my/apikeys)。
+2. 点击 **"创建"** 并复制 API Key。
+3. 在终端运行以下命令：
+
+```bash
+coder --save-auth --apikey <粘贴您的_API_KEY>
+```
+
+✅ **成功提示**: 终端显示 `✅ 认证信息已保存到配置文件` 即表示连接成功。
+
+
+-----
+
+## 核心用法
+
+### 交互模式 (Interactive Mode)
+
+直接输入 `coder` 进入沉浸式编程对话。Coder 会记住上下文，适合处理复杂的重构任务。
+
+```bash
+coder
+```
+
+### 单任务模式 (Task Mode)
+
+通过命令行参数直接下达指令，适合快速生成脚本或文件。
+
+```bash
+# 示例：生成算法文件
+coder "使用 Python 编写一个快速排序算法并输出到 sort.py 文件"
+```
+
+* **参数技巧**:
+  * `-p`: 执行完成后自动退出 (Print & Exit)，不进入交互模式。
+
+### 切换模型内核
+
+在交互模式中，输入 `/model` 即可切换底层驱动的大模型。
+
+```bash
+/model
+
+ Select model
+ Switch between models. Applies to this session and future sessions. For custom model names, specify with --model.
+
+   1.  Claude Sonnet 4.5       Use the default model Claude Sonnet 4.5 · 1.5x/1.88x per Mtok
+   2.  Claude Haiku 4.5        Claude Haiku 4.5 模型。0.53x~
+ ❯ 3.  Claude Opus 4.5         Claude Opus 4.5 for complex tasks · 2.5x/3.12x per Mtok ✔
+   4.  GPT-5                   GPT-5 for complex tasks · 1x/1x per Mtok
+   5.  GPT-5.1                 GPT-5 for complex tasks · 1x/1x per Mtok
+   6.  GPT o3                  GPT o3 for complex tasks · 1x/1x per Mtok
+   7.  Gemini 2.5 Flash        Gemini 2.5 Flash for complex tasks · 0.15x/0.32x per Mtok
+   8.  Gemini 2.5 Pro          Gemini 2.5 Pro for complex tasks · 1x/1x per Mtok
+   9.  DeepSeek-V3.1           DeepSeek-V3.1 for complex tasks · 0.14x/0.17x per Mtok
+   10. DeepSeek-R1             DeepSeek-R1 for complex tasks · 0.29x/0.29x per Mtok
+   11. Qwen Max                Qwen Max for complex tasks · 0.17x/0.17x per Mtok
+   12. Qwen3 Coder Plus        Qwen3 Coder Plus for complex tasks · 0.29x/0.29x per Mtok
+   13. Kimi K2                 Kimi-K2 for complex tasks · 0.29x/0.29x per Mtok
+   14. Kimi-K2-Instruct-0905   Kimi-K2-Instruct-0905 for complex tasks · 0.29x/0.29x per Mtok
+   15. Kimi-K2-Thinking        Kimi-K2-Thinking for complex tasks · 0.29x/0.29x per Mtok
+   16. Doubao Seed 1.6         DoubanSeed-1.6 for complex tasks · 0.06x/0.04x per Mtok
+   17. GLM 4.5                 GLM-4.5 for complex tasks · 0.29x/0.29x per Mtok
+   18. GLM 4.6                 GLM-4.6 for complex tasks · 0.4x/0.24x per Mtok
+```
+
+*(支持 Claude 4.5, GPT-5, DeepSeek-V3, Qwen Max 等全球最新模型)*
+
+### 调用特定智能体
+
+如果您对特定引擎有偏好，也可以直接指定子智能体启动：
+
+```bash
+coder claude   # 强制使用 Claude Code 引擎
+coder codex    # 强制使用 Codex 引擎
+coder gemini   # 强制使用 Google Gemini 引擎
+```
+
+
+-----
+
+好的，为了让用户更直观地感受到 Coder 的强大，我们可以增加一个\*\*“最佳实践场景 (Use Cases)”\*\*章节。
+
+这些示例涵盖了**前端开发、后端脚本、数据分析、运维部署**以及**旧代码重构**等常见场景。您可以直接将以下内容添加到文档的“使用”或“示例”部分。
+
+### 模型与引擎推荐
+
+* Claude Code + Claude Opus 4.5：目前最强编程能力，特别是后端和综合开发
+  * 命令行启动 `coder claude`
+  * 选择模型 Claude Opus 4.5：`/model` 然后选择 `Claude Opus 4.5`
+* Gemini CLI + Gemini 3.0 Pro：前端开发能力最强
+  * 命令行启动 `coder gemini`
+  * 开启早期预览功能：`/settings` 确认 `Preview Features (e.g., models)` 是开启的 `true`。空格键可以切换状态。
+  * 选择模型 Gemini 3.0 Pro Preview：`/model` 然后选择 `Pro (gemini-3-pro-preview, gemini-2.5-pro)`
+  * 示例：[Gemini CLI + Gemini 3.0 Pro = 超级前端AI](https://makecoder.com/wiki/doc/Si5zJrirEa)
+
+## 最佳实践场景示例
+
+Coder 能够处理从简单的脚本编写到复杂的全栈项目构建。以下是一些真实的指令示例，您可以直接复制运行。
+
+### Web开发快速脚手架
+
+不想手动配置 Webpack 或 Vite？让 Coder 帮您瞬间搭建项目结构。
+
+```bash
+# 生成一个带有 TailwindCSS 的 Vue3 登陆页面
+coder "创建一个 Vue3 单页应用，使用 TailwindCSS，包含一个现代化的登录界面，背景要是深色科技风"
+```
+
+### 数据分析与可视化
+
+无需打开 Jupyter Notebook，直接在终端处理数据文件。
+
+```bash
+# 假设当前目录下有一个 sales.csv 文件
+coder "读取当前目录下的 sales.csv，分析每月的销售趋势，并使用 Matplotlib 生成一张折线图保存为 trend.png"
+```
+
+### 运维与自动化
+
+编写 Docker 配置或 Shell 脚本是 Coder 的强项。
+
+```bash
+# 为当前 Node.js 项目生成 Docker 环境
+coder "为这个项目编写一个 Dockerfile，基于 Node 18 Alpine 镜像，并生成一个包含 Redis 的 docker-compose.yml"
+
+# 批量处理文件
+coder "编写一个 Shell 脚本，递归查找当前目录下所有大于 100MB 的日志文件并将其压缩，保留原始文件"
+```
+
+### 代码重构与解释
+
+接手了别人的“屎山”代码？Coder 可以帮您阅读并优化。
+
+```bash
+# 为代码添加注释和类型提示
+coder "读取 utils.py，为所有函数添加 Python 类型提示(Type Hints)和详细的中文 Docstring 注释"
+
+# 解释复杂的正则表达式
+coder "解释一下这个正则是什么意思：^([a-z0-9_\.-]+)@([\da-z\.-]+)\.([a-z\.]{2,6})$"
+```
+
+### 爬虫与工具脚本
+
+编写一次性的小工具，不用动脑，直接下令。
+
+```bash
+# 编写一个简单的爬虫
+coder "写一个 Python 脚本，抓取 Hacker News 首页的前 10 条新闻标题和链接，保存到 hn_top.md 文件中"
+```
+
+## 进阶技巧：像专家一样使用 Coder
+
+Coder 内置了强大的**上下文管理**和**指令系统**。不需要离开终端，您就可以完成从项目分析、代码查阅、修改到提交的全流程。掌握这些技巧，能让您在终端内的开发效率提升 10 倍。
+
+### 内置 `/` 指令系统
+
+Coder 并不只是被动回答问题，它内置了一系列快捷指令来主动管理工作流。在交互模式下输入 `/` 即可唤起。
+
+#### 项目启动与维护
+
+* `/init` —— 项目初始化与全量分析 (推荐) **这是接手一个现有项目时的第一步。** 运行 `/init`，Coder 会快速扫描整个项目结构，分析配置文件（如 `package.json`, `requirements.txt`, `go.mod`），并建立项目的“知识索引”。
+  * *作用*：让 AI 瞬间理解当前项目的技术栈、依赖库和目录架构，避免 AI 瞎编不存在的函数或库。
+  * *场景*：刚 Clone 下来一个开源项目，或者刚打开一个复杂的旧项目时。
+* `/compact` —— 内存整理 当对话过长导致 Token 消耗过大（或变慢）时，使用此命令。它会“压缩”历史记忆，遗忘不重要的闲聊，仅保留核心的代码逻辑和文件上下文。
+* `/clear`：清屏并开启一个新的对话会话（重置上下文）。
+
+#### Git 自动化工作流
+
+Coder 深度集成了 git 工具链，从此告别繁琐的 git 命令行。
+
+* `/git:commit` —— 智能提交 Coder 会阅读您的 `git diff`，自动生成符合规范（Conventional Commits）的提交信息。
+
+  ```bash
+  > /git:commit
+  # 🤖 提议提交信息: "feat(auth): implement JWT login logic and add unit tests"
+  # ❓ 确认提交? (Y/n)
+  ```
+* `/git:status`：查看git修改状态。
+
+### 使用 `@` 精准引用上下文
+
+显式地告诉 Coder “看哪里”，可以显著提高代码生成的准确度，并节省 Token 费用。
+
+* **引用文件**：
+
+  ```bash
+  # 语法：coder "指令" @文件名
+  coder "解释这两个文件的调用关系，并修复循环引用" @src/main.py @src/utils.py
+  ```
+* **引用目录**：
+
+  ```bash
+  coder "根据这个模块的代码，为我生成一个 Swagger API 文档" @src/controllers/
+  ```
+
+## 常见问题 (FAQ)
+
+**Q: Windows 上运行** `coder codex` 报错 `Child process exited with code: 3221225781`？
+
+**A:** 这是由于系统缺少 C++ 运行库。
+
+* **解决方法**: 下载并安装 [Visual C++ Redistributable (x64)](https://aka.ms/vs/17/release/vc_redist.x64.exe)。安装后重启 Git Bash 即可。
+
+**Q: 如何升级 Coder？**
+
+**A:** 重新运行安装命令即可覆盖更新： `npm install -g makecoder`
+
+**Q: 遇到其他问题？**
+
+**A:** 您可以访问 [MakeCoder 官网](https://makecoder.com/) 直接询问 AI 客服。

package/claude/commands/dev/ultra-think.md

@@ -0,0 +1,153 @@
+# Deep Analysis and Problem Solving Mode
+
+Deep analysis and problem solving mode
+
+## Instructions
+
+1. **Initialize Ultra Think Mode**
+   - Acknowledge the request for enhanced analytical thinking
+   - Set context for deep, systematic reasoning
+   - Prepare to explore the problem space comprehensively
+
+2. **Parse the Problem or Question**
+   - Extract the core challenge from: **$ARGUMENTS**
+   - Identify all stakeholders and constraints
+   - Recognize implicit requirements and hidden complexities
+   - Question assumptions and surface unknowns
+
+3. **Multi-Dimensional Analysis**
+   Approach the problem from multiple angles:
+   
+   ### Technical Perspective
+   - Analyze technical feasibility and constraints
+   - Consider scalability, performance, and maintainability
+   - Evaluate security implications
+   - Assess technical debt and future-proofing
+   
+   ### Business Perspective
+   - Understand business value and ROI
+   - Consider time-to-market pressures
+   - Evaluate competitive advantages
+   - Assess risk vs. reward trade-offs
+   
+   ### User Perspective
+   - Analyze user needs and pain points
+   - Consider usability and accessibility
+   - Evaluate user experience implications
+   - Think about edge cases and user journeys
+   
+   ### System Perspective
+   - Consider system-wide impacts
+   - Analyze integration points
+   - Evaluate dependencies and coupling
+   - Think about emergent behaviors
+
+4. **Generate Multiple Solutions**
+   - Brainstorm at least 3-5 different approaches
+   - For each approach, consider:
+     - Pros and cons
+     - Implementation complexity
+     - Resource requirements
+     - Potential risks
+     - Long-term implications
+   - Include both conventional and creative solutions
+   - Consider hybrid approaches
+
+5. **Deep Dive Analysis**
+   For the most promising solutions:
+   - Create detailed implementation plans
+   - Identify potential pitfalls and mitigation strategies
+   - Consider phased approaches and MVPs
+   - Analyze second and third-order effects
+   - Think through failure modes and recovery
+
+6. **Cross-Domain Thinking**
+   - Draw parallels from other industries or domains
+   - Apply design patterns from different contexts
+   - Consider biological or natural system analogies
+   - Look for innovative combinations of existing solutions
+
+7. **Challenge and Refine**
+   - Play devil's advocate with each solution
+   - Identify weaknesses and blind spots
+   - Consider "what if" scenarios
+   - Stress-test assumptions
+   - Look for unintended consequences
+
+8. **Synthesize Insights**
+   - Combine insights from all perspectives
+   - Identify key decision factors
+   - Highlight critical trade-offs
+   - Summarize innovative discoveries
+   - Present a nuanced view of the problem space
+
+9. **Provide Structured Recommendations**
+   Present findings in a clear structure:
+   ```
+   ## Problem Analysis
+   - Core challenge
+   - Key constraints
+   - Critical success factors
+   
+   ## Solution Options
+   ### Option 1: [Name]
+   - Description
+   - Pros/Cons
+   - Implementation approach
+   - Risk assessment
+   
+   ### Option 2: [Name]
+   [Similar structure]
+   
+   ## Recommendation
+   - Recommended approach
+   - Rationale
+   - Implementation roadmap
+   - Success metrics
+   - Risk mitigation plan
+   
+   ## Alternative Perspectives
+   - Contrarian view
+   - Future considerations
+   - Areas for further research
+   ```
+
+10. **Meta-Analysis**
+    - Reflect on the thinking process itself
+    - Identify areas of uncertainty
+    - Acknowledge biases or limitations
+    - Suggest additional expertise needed
+    - Provide confidence levels for recommendations
+
+## Usage Examples
+
+```bash
+# Architectural decision
+/project:ultra-think Should we migrate to microservices or improve our monolith?
+
+# Complex problem solving
+/project:ultra-think How do we scale our system to handle 10x traffic while reducing costs?
+
+# Strategic planning
+/project:ultra-think What technology stack should we choose for our next-gen platform?
+
+# Design challenge
+/project:ultra-think How can we improve our API to be more developer-friendly while maintaining backward compatibility?
+```
+
+## Key Principles
+
+- **First Principles Thinking**: Break down to fundamental truths
+- **Systems Thinking**: Consider interconnections and feedback loops
+- **Probabilistic Thinking**: Work with uncertainties and ranges
+- **Inversion**: Consider what to avoid, not just what to do
+- **Second-Order Thinking**: Consider consequences of consequences
+
+## Output Expectations
+
+- Comprehensive analysis (typically 2-4 pages of insights)
+- Multiple viable solutions with trade-offs
+- Clear reasoning chains
+- Acknowledgment of uncertainties
+- Actionable recommendations
+- Novel insights or perspectives

package/claude/commands/docs/generate-api-documentation.md

@@ -0,0 +1,80 @@
+# Generate API Documentation
+
+Auto-generate API reference documentation
+
+## Instructions
+
+1. **API Documentation Strategy Analysis**
+   - Analyze current API structure and endpoints
+   - Identify documentation requirements (REST, GraphQL, gRPC, etc.)
+   - Assess existing code annotations and documentation
+   - Determine documentation output formats and hosting requirements
+   - Plan documentation automation and maintenance strategy
+
+2. **Documentation Tool Selection**
+   - Choose appropriate API documentation tools:
+     - **OpenAPI/Swagger**: REST API documentation with Swagger UI
+     - **Redoc**: Modern OpenAPI documentation renderer
+     - **GraphQL**: GraphiQL, Apollo Studio, GraphQL Playground
+     - **Postman**: API documentation with collections
+     - **Insomnia**: API documentation and testing
+     - **API Blueprint**: Markdown-based API documentation
+     - **JSDoc/TSDoc**: Code-first documentation generation
+   - Consider factors: API type, team workflow, hosting, interactivity
+
+3. **Code Annotation and Schema Definition**
+   - Add comprehensive code annotations for API endpoints
+   - Define request/response schemas and data models
+   - Add parameter descriptions and validation rules
+   - Document authentication and authorization requirements
+   - Add example requests and responses
+
+4. **API Specification Generation**
+   - Set up automated API specification generation from code
+   - Configure OpenAPI/Swagger specification generation
+   - Set up schema validation and consistency checking
+   - Configure API versioning and changelog generation
+   - Set up specification file management and version control
+
+5. **Interactive Documentation Setup**
+   - Configure interactive API documentation with try-it-out functionality
+   - Set up API testing and example execution
+   - Configure authentication handling in documentation
+   - Set up request/response validation and examples
+   - Configure API endpoint categorization and organization
+
+6. **Documentation Content Enhancement**
+   - Add comprehensive API guides and tutorials
+   - Create authentication and authorization documentation
+   - Add error handling and status code documentation
+   - Create SDK and client library documentation
+   - Add rate limiting and usage guidelines
+
+7. **Documentation Hosting and Deployment**
+   - Set up documentation hosting and deployment
+   - Configure documentation website generation and styling
+   - Set up custom domain and SSL configuration
+   - Configure documentation search and navigation
+   - Set up documentation analytics and usage tracking
+
+8. **Automation and CI/CD Integration**
+   - Configure automated documentation generation in CI/CD pipeline
+   - Set up documentation deployment automation
+   - Configure documentation validation and quality checks
+   - Set up documentation change detection and notifications
+   - Configure documentation testing and link validation
+
+9. **Multi-format Documentation Generation**
+   - Generate documentation in multiple formats (HTML, PDF, Markdown)
+   - Set up downloadable documentation packages
+   - Configure offline documentation access
+   - Set up documentation API for programmatic access
+   - Configure documentation syndication and distribution
+
+10. **Maintenance and Quality Assurance**
+    - Set up documentation quality monitoring and validation
+    - Configure documentation feedback and improvement workflows
+    - Set up documentation analytics and usage metrics
+    - Create documentation maintenance procedures and guidelines
+    - Train team on documentation best practices and tools
+    - Set up documentation review and approval processes

package/claude/commands/git/commit.md

@@ -0,0 +1,63 @@
+# Commit
+
+Create well-formatted commits with conventional commit messages and emojis.
+
+## Features:
+
+- Runs pre-commit checks by default (lint, build, generate docs)
+- Automatically stages files if none are staged
+- Uses conventional commit format with descriptive emojis
+- Suggests splitting commits for different concerns
+- Maintain good submission formatting, do not include invisible characters in submissions, use utf-8 encoding for submissions
+- NEVER include ANSI color codes or escape sequences in commit messages
+- Do NOT add "🤖 Generated with [Claude Code]" or "Co-Authored-By: Claude" signatures to commit messages
+
+## Usage:
+
+- `/commit` - Standard commit with pre-commit checks
+- `/commit --no-verify` - Skip pre-commit checks
+
+## Commit Types:
+
+| Emoji                  | Devmoji Code      | Description                                                                                                       |
+| ---------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------- |
+| :sparkles:             | `:feat:`          | **feat:** a new feature                                                                                           |
+| :bug:                  | `:fix:`           | **fix:** a bug fix                                                                                                |
+| :books:                | `:docs:`          | **docs:** documentation only changes                                                                              |
+| :art:                  | `:style:`         | **style:** changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) |
+| :recycle:              | `:refactor:`      | **refactor:** a code change that neither fixes a bug nor adds a feature                                           |
+| :zap:                  | `:perf:`          | **perf:** a code change that improves performance                                                                 |
+| :rotating_light:       | `:test:`          | **test:** adding missing or correcting existing tests                                                             |
+| :wrench:               | `:chore:`         | **chore:** changes to the build process or auxiliary tools and libraries such as documentation generation         |
+| :rocket:               | `:chore-release:` | **chore(release):** code deployment or publishing to external repositories                                        |
+| :link:                 | `:chore-deps:`    | **chore(deps):** add or delete dependencies                                                                       |
+| :package:              | `:build:`         | **build:** changes related to build processes                                                                     |
+| :construction_worker:  | `:ci:`            | **ci:** updates to the continuous integration system                                                              |
+| :rocket:               | `:release:`       | code deployment or publishing to external repositories                                                            |
+| :lock:                 | `:security:`      | Fixing security issues.                                                                                           |
+| :globe_with_meridians: | `:i18n:`          | Internationalization and localization.                                                                            |
+| :boom:                 | `:breaking:`      | Introducing breaking changes.                                                                                     |
+| :gear:                 | `:config:`        | Changing configuration files.                                                                                     |
+| :heavy_plus_sign:      | `:add:`           | add something                                                                                                     |
+| :heavy_minus_sign:     | `:remove:`        | remove something                                                                                                  |
+
+## Process:
+
+1. Check for staged changes (`git status`)
+2. If no staged changes, review and stage appropriate files
+3. Run pre-commit checks (unless --no-verify)
+4. Analyze changes to determine commit type
+5. Generate descriptive commit message (plain text only, no color codes)
+6. Include scope if applicable: `type(scope): description`
+7. Add body for complex changes explaining why
+8. Execute commit with clean message formatting
+
+## Best Practices:
+
+- Keep commits atomic and focused
+- Write in imperative mood ("Add feature" not "Added feature")
+- Explain why, not just what
+- Reference issues/PRs when relevant
+- Split unrelated changes into separate commits
+- Use clean, plain text commit messages without color codes or signatures
+- Prefer emoji codes (:gear:) over actual emoji characters (⚙️) for better compatibility and readability

package/claude/commands/git/status.md

@@ -0,0 +1,39 @@
+# Git Status Command
+
+Show detailed git repository status
+
+*Command originally created by IndyDevDan (YouTube: https://www.youtube.com/@indydevdan) / DislerH (GitHub: https://github.com/disler)*
+
+## Instructions
+
+Analyze the current state of the git repository by performing the following steps:
+
+1. **Run Git Status Commands**
+   - Execute `git status` to see current working tree state
+   - Run `git diff HEAD origin/main` to check differences with remote
+   - Execute `git branch --show-current` to display current branch
+   - Check for uncommitted changes and untracked files
+
+2. **Analyze Repository State**
+   - Identify staged vs unstaged changes
+   - List any untracked files
+   - Check if branch is ahead/behind remote
+   - Review any merge conflicts if present
+
+3. **Read Key Files**
+   - Review README.md for project context
+   - Check for any recent changes in important files
+   - Understand project structure if needed
+
+4. **Provide Summary**
+   - Current branch and its relationship to main/master
+   - Number of commits ahead/behind
+   - List of modified files with change types
+   - Any action items (commits needed, pulls required, etc.)
+
+This command helps developers quickly understand:
+- What changes are pending
+- The repository's sync status
+- Whether any actions are needed before continuing work
+
+Arguments: $ARGUMENTS