@qazuor/claude-code-config 0.1.0

package/templates/commands/formatting/format-markdown.md

@@ -0,0 +1,197 @@
+---
+name: format-markdown
+description: Automatically detect and fix markdown formatting violations
+type: formatting
+category: quality
+config_required:
+  - rules_enabled: "Define which markdown rules to enforce"
+  - file_patterns: "Specify which files to format"
+  - formatting_options: "Configure formatting preferences"
+---
+
+# Markdown Format Command
+
+## Purpose
+
+Automatically detect and fix markdown formatting violations in documentation files using comprehensive linting rules and context-aware corrections.
+
+## ⚙️ Configuration
+
+| Setting | Description | Example |
+|---------|-------------|---------|
+| `rules_enabled` | Active markdown rules | `MD007, MD012, MD022, MD040, etc.` |
+| `file_patterns.include` | Files to format | `**/*.md` |
+| `file_patterns.exclude` | Files to skip | `node_modules/**, dist/**` |
+| `list_indentation` | Nested list spacing | `2` |
+| `max_blank_lines` | Consecutive blanks | `1` |
+| `code_language_default` | Fallback language | `text` |
+
+## Usage
+
+```bash
+/format-markdown [options]
+```
+
+### Options
+
+- `--file <path>`: Format specific file
+- `--validate-only`: Check without changes
+- `--rules <list>`: Apply specific rules only
+- `--report`: Show detailed report
+
+### Examples
+
+```bash
+/format-markdown
+/format-markdown --file path/to/file.md
+/format-markdown --validate-only
+/format-markdown --rules MD040,MD022
+```
+
+## Supported Rules
+
+| Rule | Fix | Description |
+|------|-----|-------------|
+| MD007 | Indentation | Normalize list indentation |
+| MD012 | Blank lines | Remove multiple consecutive blanks |
+| MD022 | Spacing | Add blank lines around headings |
+| MD024 | Duplicates | Resolve duplicate headings |
+| MD026 | Punctuation | Remove trailing punctuation in headings |
+| MD031 | Spacing | Add blank lines around code blocks |
+| MD032 | Spacing | Add blank lines around lists |
+| MD040 | Language | Add language to code blocks |
+| MD051 | Links | Fix link fragments |
+| MD058 | Spacing | Add blank lines around tables |
+
+## Processing Phases
+
+### Phase 1: Analysis
+
+- Scan target files
+- Parse markdown AST
+- Apply rule checkers
+- Collect violations
+- Generate fix recommendations
+
+### Phase 2: Planning
+
+- Determine fix strategy
+- Check for conflicts
+- Prioritize by severity
+- Generate atomic operations
+
+### Phase 3: Execution
+
+- Create backups
+- Apply fixes in order
+- Validate success
+- Verify no regressions
+
+### Phase 4: Validation
+
+- Re-scan for violations
+- Confirm semantic preservation
+- Generate report
+- Clean up temporary files
+
+## Context-Aware Features
+
+### Language Detection
+
+**Algorithm**:
+
+- Analyze preceding content for language hints
+- Check file extension context
+- Apply language mapping
+- Default to configured fallback
+
+**Mappings**:
+
+```text
+*.ts → typescript
+*.js → javascript
+*.py → python
+*.sql → sql
+*.yml, *.yaml → yaml
+*.json → json
+```
+
+### Duplicate Heading Resolution
+
+**Strategies**:
+
+1. Contextual prefixes
+2. Numbered suffixes
+3. Semantic alternatives
+4. Manual review flags
+
+## Safety Guarantees
+
+### Content Preservation
+
+- Automatic backup creation
+- Atomic operations
+- Rollback support
+- Encoding safety (UTF-8)
+
+### Validation
+
+- Semantic verification
+- Link integrity
+- Structure preservation
+- Performance monitoring
+
+## Output Format
+
+### Summary Report
+
+```text
+📊 Markdown Formatting Report
+Files Processed: {count}
+Rules Applied: {count}
+Violations Fixed: {count}
+Processing Time: {time}
+
+✅ Successfully formatted: {count}
+⚠️  Warnings: {count}
+❌ Errors: {count}
+```
+
+### Detailed Report
+
+```text
+📝 File-by-File Report
+✅ {filename}
+   - MD040: Added {count} language specifications
+   - MD022: Added {count} heading blank lines
+   - MD031: Added {count} code block blank lines
+```
+
+## Best Practices
+
+### Usage
+
+1. Run on committed changes
+2. Review critical document changes
+3. Start with specific rules
+4. Ensure team alignment
+5. Integrate into workflow
+
+### Maintenance
+
+- Regular rule effectiveness review
+- Performance monitoring
+- User feedback incorporation
+- Documentation synchronization
+
+## Related Commands
+
+- `/quality-check` - Includes markdown validation
+- `/update-docs` - Documentation maintenance
+
+## When to Use
+
+- Before committing documentation
+- Regular maintenance
+- Before releases
+- CI/CD quality gates

package/templates/commands/git/commit.md

@@ -0,0 +1,247 @@
+---
+name: commit
+description: Generate conventional commit messages following project standards
+type: git
+category: version-control
+config_required:
+  - commit_types: "Define allowed commit types (feat, fix, etc.)"
+  - scopes: "Configure project-specific scopes"
+  - message_format: "Specify commit message structure"
+  - max_lengths: "Define character limits for subject/body"
+---
+
+# Commit Command
+
+## Purpose
+
+Generate conventional commit messages following project standards, analyze changed files, group changes logically, and provide copy-paste ready git commands.
+
+## ⚙️ Configuration
+
+| Setting | Description | Example |
+|---------|-------------|---------|
+| `commit_types` | Allowed commit types | `feat, fix, refactor, docs, style, test, build, ci, chore` |
+| `scopes.backend` | Backend scopes | `api, db, services, auth` |
+| `scopes.frontend` | Frontend scopes | `web, admin, components, hooks` |
+| `scopes.shared` | Shared scopes | `types, schemas, config, deps` |
+| `subject_max_length` | Subject line limit | `72` |
+| `body_wrap_length` | Body line wrap | `72` |
+
+## Usage
+
+```bash
+/commit
+```
+
+## Execution Flow
+
+### Step 1: Analyze Git Status
+
+**Actions**:
+
+- Run `git status` for changed files
+- Run `git diff` for unstaged changes
+- Run `git diff --staged` for staged changes
+- Run `git log` for recent commit style
+
+### Step 2: Invoke Commit Helper
+
+**Process**:
+
+- Analyze changed files
+- Group by logical units
+- Identify commit types and scopes
+- Generate conventional messages
+- Format git commands
+
+### Step 3: Present Commit Strategy
+
+**Analysis**:
+
+1. Changed areas identification
+2. Commit grouping strategy
+3. Conventional format application
+
+### Step 4: Generate Commands
+
+**Output**: Copy-paste ready git commands
+
+## Commit Standards
+
+### Format
+
+```text
+{type}({scope}): {subject}
+
+{body}
+
+{footer}
+```
+
+### Types
+
+| Type | Description |
+|------|-------------|
+| `feat` | New feature |
+| `fix` | Bug fix |
+| `refactor` | Code refactoring |
+| `docs` | Documentation |
+| `style` | Code style (no logic change) |
+| `test` | Tests |
+| `build` | Build system |
+| `ci` | CI/CD |
+| `chore` | Other changes |
+
+### Scopes
+
+Configure based on project structure:
+
+- Backend: API, database, services
+- Frontend: Apps, components, pages
+- Shared: Types, config, dependencies
+
+## Examples
+
+### Single Feature
+
+```bash
+git add {files}
+git commit -m "feat({scope}): {subject}
+
+{body}
+
+Closes #{issue}"
+```
+
+### Multi-Layer Feature
+
+```bash
+# Commit 1: Schema
+git add {schema_files}
+git commit -m "feat(schemas): add {entity} schemas"
+
+# Commit 2: Database
+git add {db_files}
+git commit -m "feat(db): implement {entity} model"
+
+# Commit 3: Service
+git add {service_files}
+git commit -m "feat(services): implement {entity} service"
+```
+
+## Best Practices
+
+### Subject Line
+
+**DO**:
+
+- Use imperative mood
+- Keep under configured max length
+- Be specific and descriptive
+- Use lowercase for type/scope
+
+**DON'T**:
+
+- Use past tense
+- Capitalize first letter
+- End with period
+- Be vague
+
+### Body
+
+**DO**:
+
+- Explain why, not what
+- Use bullet points
+- Wrap at configured length
+- Include context
+
+**DON'T**:
+
+- Describe code (code shows that)
+- Skip for complex changes
+- Mix unrelated changes
+
+### Footer
+
+**Use for**:
+
+- Breaking changes
+- Issue references
+- PR references
+
+## Commit Strategy
+
+### Decision Tree
+
+```text
+1. One logical unit?
+   YES → Single commit
+   NO → Multiple commits
+
+2. Group by:
+   - Layer (if cross-layer)
+   - Feature (if independent)
+   - Type (if mixed types)
+
+3. Commit order:
+   1. Schemas
+   2. Database
+   3. Services
+   4. API
+   5. Frontend
+   6. Documentation
+   7. Configuration
+```
+
+## Output Deliverables
+
+1. Git status analysis
+2. Changed files grouped
+3. Commit strategy
+4. Conventional messages
+5. Copy-paste commands
+6. Issue references
+
+## Important Notes
+
+### Execution
+
+**CRITICAL**: Command generates suggestions but DOES NOT execute `git add` automatically.
+
+**User must**:
+
+1. Review suggestions
+2. Stage files with `git add`
+3. Execute `git commit` commands
+4. Verify with `git log`
+
+### When to Run
+
+- After feature completion
+- After bugfixes
+- Before pull requests
+- As part of quality workflow
+
+## Related Commands
+
+- `/quality-check` - Pre-commit validation
+- `/code-check` - Lint/typecheck before commit
+- `/run-tests` - Verify tests pass
+
+## Error Prevention
+
+### Avoid Committing
+
+- Unrelated changes together
+- Debug statements
+- Broken code
+- Secrets/credentials
+- Commented-out code
+
+### Always
+
+- Run quality checks first
+- Group related changes
+- Write descriptive messages
+- Reference issues

package/templates/commands/meta/create-agent.md

@@ -0,0 +1,257 @@
+---
+name: create-agent
+type: meta
+category: system
+description: Interactive wizard to create specialized AI agents
+config_required:
+  - agent_categories: "Define available agent categories"
+  - model_options: "Configure model preferences (sonnet, opus, haiku)"
+  - tool_sets: "Define standard tool combinations"
+  - template_types: "Specify agent template types"
+---
+
+# Create Agent Command
+
+## Purpose
+
+Interactive wizard for creating specialized AI agents following project standards. Ensures proper integration with workflow system and comprehensive documentation.
+
+## ⚙️ Configuration
+
+| Setting | Description | Example |
+|---------|-------------|---------|
+| `agent_categories` | Available categories | `product, engineering, quality, design, specialized` |
+| `model_options` | Available models | `sonnet, opus, haiku, inherit` |
+| `tool_sets.basic` | Basic tool set | `Read, Write, Edit` |
+| `tool_sets.advanced` | Advanced tool set | `Read, Write, Edit, Bash, Task, Skill` |
+| `template_types` | Agent templates | `technical, product, quality, design` |
+| `base_path` | Agent directory | `.claude/agents/` |
+
+## Usage
+
+```bash
+/create-agent [options]
+```
+
+### Options
+
+- `--name <kebab-case>`: Agent name
+- `--category <category>`: Category
+- `--interactive`: Full interactive mode (default)
+- `--template <type>`: Use template
+
+## When to Use
+
+- New specialized role needed
+- Responsibility gaps identified
+- Separation of concerns required
+- Team expansion
+
+## Agent Creation Process
+
+### Step 1: Discovery & Planning
+
+**Wizard Questions**:
+
+1. Agent Name (kebab-case)
+2. Category selection
+3. Primary responsibilities (3-5)
+4. Phase involvement
+5. Required tools
+6. Model preference
+7. Related agents
+
+### Step 2: File Generation
+
+**File Created**: `{base_path}/{category}/{agent-name}.md`
+
+**YAML Frontmatter**:
+
+```yaml
+---
+name: {agent-name}
+description: {description}
+tools: {tools}
+model: {model}
+responsibilities:
+  - {responsibility}
+---
+```
+
+**Structure Sections**:
+
+1. Role & Identity
+2. Core Responsibilities
+3. Working Context
+4. Best Practices
+5. Workflow Integration
+6. Quality Standards
+7. Tools & Resources
+8. Examples
+
+### Step 3: Integration & Documentation
+
+**Updates Required**:
+
+- Agent README
+- Main documentation
+- Glossary (if new pattern)
+- Template files (if applicable)
+
+### Step 4: Validation
+
+**Checks**:
+
+- Name follows conventions
+- YAML valid
+- All sections complete
+- Responsibilities clear
+- Tools appropriate
+- No overlap with existing
+- Documentation updated
+
+**Test Invocation**: Verify agent loads and functions
+
+### Step 5: Commit
+
+**Format**:
+
+```bash
+feat(agents): add {agent-name} agent
+
+- Core responsibilities: {list}
+- Integrates with: {agents}
+- Tools: {tools}
+- Model: {model}
+
+Updates:
+- {agent_file} (new)
+- README.md (updated)
+```
+
+## Interactive Wizard Flow
+
+```text
+🤖 Create New Agent Wizard
+
+📝 Step 1: Agent Identity
+Agent Name: {input}
+Category: {selection}
+Description: {input}
+
+📋 Step 2: Responsibilities
+Enter 3-5 primary responsibilities
+
+🔧 Step 3: Configuration
+Tools needed: {selection}
+Model preference: {selection}
+Phase involvement: {selection}
+
+🔗 Step 4: Relationships
+Related agents: {input}
+
+📝 Step 5: Review & Confirm
+{summary}
+Proceed? (y/n)
+
+✨ Creating Agent
+✓ Generated agent file
+✓ Updated documentation
+✓ Validation passed
+```
+
+## Agent Templates
+
+### Technical Agent
+
+```markdown
+---
+name: {agent-name}
+description: {description}
+tools: Read, Write, Edit, Bash
+model: sonnet
+---
+
+# {Agent Name}
+
+## Role & Identity
+{role_definition}
+
+## Core Responsibilities
+{responsibilities}
+
+## Working Context
+{context}
+
+## Best Practices
+{practices}
+
+[Additional sections...]
+```
+
+## Validation Rules
+
+### Agent Name
+
+- Format: kebab-case
+- Length: 3-30 characters
+- Pattern: `^[a-z][a-z0-9-]*[a-z0-9]$`
+- Must be unique
+
+### YAML Frontmatter
+
+**Required**: name, description, tools, model, responsibilities
+
+**Valid Tools**: Read, Write, Edit, Glob, Grep, Bash, Task, Skill, mcp__*
+
+**Valid Models**: sonnet, opus, haiku, inherit
+
+### Directory Structure
+
+```text
+{base_path}/
+├── product/
+├── engineering/
+├── quality/
+├── design/
+└── specialized/
+```
+
+## Best Practices
+
+### Design
+
+- Clear scope definition
+- No overlap with existing
+- Focused responsibilities
+- Comprehensive documentation
+- Multiple examples
+- Actionable checklists
+
+### Integration
+
+- Clear workflow integration
+- Defined collaboration patterns
+- Explicit input/output protocols
+
+## Common Patterns
+
+| Type | Category | Tools | Model | Phases |
+|------|----------|-------|-------|--------|
+| Backend | engineering | Read, Write, Edit, Bash | sonnet | Phase 2 |
+| QA | quality | Read, Bash, Skill | sonnet | Phase 3, All |
+| Product | product | Read, Write, Edit | sonnet | Phase 1 |
+
+## Related Commands
+
+- `/create-command` - Create new command
+- `/create-skill` - Create new skill
+- `/help` - System help
+
+## Notes
+
+- Consider consolidation before creating new
+- Prefer specialized for deep expertise
+- Only grant needed tools
+- Use sonnet for most cases
+- Test before committing