refactor(commands): fix maintenance typo and simplify command descriptions

Author: apiad

.gemini/commands/commit.toml

@@ -1,4 +1,4 @@
-description = "Analyze uncommitted changes, group them by feature, and commit them individually using Conventional Commits."
+description = "Group and commit uncommitted changes individually using Conventional Commits."
 
 prompt = """
 Please analyze all current uncommitted changes (including untracked files).

.gemini/commands/docs.toml

@@ -1,4 +1,4 @@
-description = "Analyze the codebase and update/generate project documentation in the docs/ folder."
+description = "Analyze codebase to update or generate project documentation in the docs folder."
 prompt = """
 You are a senior technical writer and software engineer. Your goal is to ensure the project documentation is accurate, comprehensive, and helpful for both human developers and AI agents.
 

.gemini/commands/issues.toml

@@ -1,4 +1,4 @@
-description = "Manage project issues with GitHub CLI: list summary, create, update, or plan work."
+description = "Manage project issues using GitHub CLI: list, create, update, or plan work."
 
 prompt = """
 You are an expert project lead. Your goal is to manage project issues using the `gh` (GitHub) CLI.

.gemini/commands/maintenance.toml

@@ -0,0 +1,22 @@
+description = "Analyze and propose refactoring plans to improve code readability and maintainability."
+prompt = """
+You are an expert software engineer performing a comprehensive codebase maintenance on the current workspace.
+
+**Phase 1: Deep Analysis & Planning**
+Run a deep analysis of the current codebase focusing on performance, security, readability, and overall maintainability.
+**Crucial:** Do NOT propose changes that alter existing functionality or fix bugs. This is strictly a maintenance, clean-up, and refactoring operation.
+
+Create a detailed and expressive plan with the following priorities:
+1. **DRY (Don't Repeat Yourself):** Identify and extract duplicated or near-duplicated code.
+2. **Documentation:** Add comprehensive, high-quality docstrings to all functions and classes following the project's conventions.
+3. **Test Coverage:** Identify missing test coverage and propose adding robust tests for corner and edge cases.
+4. **Simplification:** Split long, complex, or deeply nested logic into smaller, focused, and testable methods.
+
+Your proposed plan must be highly expressive and detailed. List all intended changes *file by file*, explicitly explaining the rationale and expected benefit behind each refactoring step.
+
+**Phase 2: User Agreement**
+Stop and present your complete plan to the user. Wait for their explicit agreement before making any file modifications.
+
+**Phase 3: Step-by-Step Implementation**
+Upon user agreement, implement the plan iteratively, step by step. Ensure that after each logical change, the code is properly formatted, passes all linters, and all tests pass, using the appropriate command for the current project.
+"""

.gemini/commands/onboard.toml

@@ -1,4 +1,4 @@
-description = "Onboard a new developer to the project by summarizing the architecture, coding standards, and current state."
+description = "Summarize architecture, standards, and state to onboard a new developer."
 prompt = """
 You are a senior software engineer responsible for onboarding a new developer to this project.
 Your goal is to provide a clear, concise, and professional orientation that allows the newcomer to understand the codebase and start contributing effectively.

.gemini/commands/release.toml

@@ -1,4 +1,4 @@
-description = "Automate the release process: check workspace, run tests, determine version bump, update CHANGELOG.md, tag, and push."
+description = "Automate the release process including testing, versioning, changelog, and tagging."
 
 prompt = """
 You are a senior software engineer responsible for the release process of this project.

.gemini/commands/research.toml

@@ -1,4 +1,4 @@
-description = "Perform deep research on a topic in a structured 3-phase workflow: planning, data gathering, and reporting."
+description = "Conduct structured research through planning, data gathering, and reporting phases."
 
 prompt = """
 You are an expert researcher. Follow this robust 3-phase workflow to conduct exhaustive research on the following topic: {{args}}

.gemini/commands/scaffold.toml

@@ -1,4 +1,4 @@
-description = "Scaffold a new project using modern standard practices and tooling (e.g., Python/uv, JS/npm, Rust, Go, C#)."
+description = "Scaffold a new project using modern standard practices and tooling."
 
 prompt = """
 You are an expert system architect and project scaffolder. Your goal is to initialize a new project from scratch, using modern, standard tooling for the chosen tech stack.

README.md

@@ -54,7 +54,7 @@ The `.gemini/commands/` directory defines specialized workflows:
 *   **/commit**: Analyzes changes, groups them logically, and commits them one-by-one using Conventional Commits.
 * **/release**: Automates version bumping, `CHANGELOG.md` updates, and git tagging.
 * **/issues**: Manage project issues with GitHub CLI: list summary, create, update, or plan work.
-* **/maintainance**: Performs deep analysis and proposes step-by-step refactoring plans.
+* **/maintenance**: Performs deep analysis and proposes step-by-step refactoring plans.
 *   **/docs**: Generates and maintains project documentation.
 *   **/onboard**: Helps new developers (or the agent itself) understand the project structure.