Contributing to PptMcp

Thank you for your interest in contributing to PptMcp! This project is designed to be extended by the community, especially to support coding agents like GitHub Copilot.

🎯 Project Vision

PptMcp aims to be the go-to command-line tool for coding agents to interact with Microsoft PowerPoint files. We prioritize:

• Simplicity - Clear, predictable commands
• Reliability - Robust COM automation
• Extensibility - Easy to add new features
• Agent-Friendly - Designed for AI coding assistants

🚀 Getting Started

Development Environment

1. Prerequisites:

   • Windows OS (required for PowerPoint COM)
   • Visual Studio 2022 or VS Code
   • .NET 10 SDK
   • Microsoft PowerPoint installed

2. Setup:

   git clone https://github.com/trsdn/mcp-server-ppt.git
   cd PptMcp
   dotnet restore
   dotnet build
   

🚨 CRITICAL: Pull Request Workflow Required

All changes must be made through Pull Requests (PRs). Direct commits to main are prohibited.

Quick PR Process

1. Create feature branch: git checkout -b feature/your-feature
2. Make changes: Code, tests, documentation
3. Push branch: git push origin feature/your-feature
4. Create PR: Use GitHub's PR template
5. Address review: Make requested changes
6. Merge: After approval and CI checks pass

📋 Detailed workflow: See DEVELOPMENT.md for complete instructions.

3. Test Your Setup:

   dotnet run -- pq-list "path/to/test.pptx"
   

📋 Development Guidelines

Code Style

• C# 12 features encouraged (file-scoped namespaces, records, pattern matching)
• Nullable reference types enabled - handle nulls properly
• No warnings - project must build with zero warnings
• XML documentation for public APIs
• Consistent naming - follow established patterns

Architecture Patterns

Command Pattern

All commands follow this structure:

// Interface
public interface IMyCommands
{
    int MyOperation(string[] args);
}

// Implementation  
public class MyCommands : IMyCommands
{
    public int MyOperation(string[] args)
    {
        // Validation
        if (!ValidateArgs(args, expectedCount, "usage string"))
            return 1;
            
        // PowerPoint automation using batch API
        var task = Task.Run(async () =>
        {
            await using var batch = await PptSession.BeginBatchAsync(filePath);
            return batch.Execute((ctx, ct) =>
            {
                // Use ctx.Presentation for presentation access
                // Your implementation
                return 0; // Success
            });
        });
        return task.GetAwaiter().GetResult();
    }
}

Critical Rules

1. Always use batch API - Never manage PowerPoint lifecycle manually
2. PowerPoint uses 1-based indexing - collection.Item(1) is the first element
3. Release COM objects in finally - Every dynamic COM object needs ComUtilities.Release(ref obj!)
4. Escape user input - Always use .EscapeMarkup() with Spectre.Console
5. Return 0 for success, 1+ for errors - Consistent exit codes

PowerPoint COM Best Practices

• Late binding with dynamic types - Use Type.GetTypeFromProgID("PowerPoint.Application")
• Proper error handling - Catch COMException and provide helpful messages
• Resource cleanup - Batch API handles COM object lifecycle automatically
• Input validation - Check file existence and argument counts early

Testing

Before submitting:

1. Manual testing with various PowerPoint files
2. Verify PowerPoint process cleanup - No powerpnt.exe should remain after 5 seconds
3. Test error conditions - Missing files, invalid arguments, etc.
4. VBA script testing - For script-related commands, test with real VBA macros
5. Cross-version compatibility - Test with different PowerPoint versions if possible

🔧 Adding New Commands

1. Create Interface

// Commands/INewCommands.cs
namespace PptMcp.Commands;

public interface INewCommands
{
    int NewOperation(string[] args);
}

2. Implement Command Class

// Commands/NewCommands.cs
using Spectre.Console;

namespace PptMcp.Commands;

public class NewCommands : INewCommands
{
    public int NewOperation(string[] args)
    {
        // Implementation following established patterns
    }
}

3. Register in Program.cs

Add to the switch expression in Main():

return args[0] switch
{
    "new-operation" => newCommands.NewOperation(args),
    // ... existing commands
    _ => ShowHelp()
};

4. Update Help Text

Add your command to the help output in ShowHelp().

📝 Pull Request Process

Before Submitting

• Code builds with zero warnings
• All existing commands still work
• PowerPoint processes clean up properly
• Added appropriate error handling
• Updated help text if needed
• Tested with various PowerPoint files

PR Description Template

## Summary
Brief description of changes

## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Documentation update

## Testing
- [ ] Tested manually with PowerPoint files
- [ ] Verified PowerPoint process cleanup
- [ ] Tested error conditions
- [ ] VBA script execution tested (if applicable)
- [ ] No build warnings

## Checklist
- [ ] Code follows project conventions
- [ ] Self-review completed
- [ ] Updated documentation as needed

🎨 UI Guidelines

Spectre.Console Usage

// Success (green checkmark)
AnsiConsole.MarkupLine($"[green]✓[/] Operation succeeded");

// Error (red)  
AnsiConsole.MarkupLine($"[red]Error:[/] {message.EscapeMarkup()}");

// Warning (yellow)
AnsiConsole.MarkupLine($"[yellow]Note:[/] {message}");

// Info/debug (dim)
AnsiConsole.MarkupLine($"[dim]{message}[/]");

// Headers (cyan)
AnsiConsole.MarkupLine($"[cyan]{title}[/]");

Output Consistency

• Tables for structured data (query lists, sheet lists)
• Panels for code blocks (M code display)
• Progress indicators for long operations
• Clear error messages with actionable guidance

🐛 Bug Reports

When reporting bugs, please include:

• PowerPoint version and Windows version
• Command used and arguments
• Expected behavior vs actual behavior
• Sample PowerPoint file (if possible)
• Error messages (full text)

💡 Feature Requests

Great feature requests include:

• Use case description - Why is this needed?
• Proposed command syntax - How should it work?
• PowerPoint operations involved - What APIs would be used?
• Target users - Coding agents? Direct users?

📚 Learning Resources

• PowerPoint VBA Object Model Reference
• Spectre.Console Documentation
• .NET COM Interop Guide

📦 For Maintainers

• NuGet Publishing Guide - Complete guide for publishing all packages with OIDC trusted publishing

🏷️ Issue Labels

• bug - Something isn't working
• enhancement - New feature or improvement
• documentation - Documentation improvements
• good first issue - Good for newcomers
• help wanted - Extra attention needed
• ppt-com - PowerPoint COM automation issues
• vba - VBA automation specific
• coding-agent - Coding agent related

---

Thank you for contributing to PptMcp! Together we're making PowerPoint automation more accessible to coding agents and developers worldwide. 🚀