Merge pull request #83 from huggingface/release/unit3

[RELEASE] Unit 3 and 3.1 for 12/6/25

Author: burtenshaw

.gitignore

@@ -173,4 +173,6 @@ cython_debug/
 # PyPI configuration file
 .pypirc
 
-.DS_Store
+.DS_Store
+
+videos/

projects/unit3/build-mcp-server/solution/README.md

@@ -0,0 +1,73 @@
+# Module 1: Basic MCP Server with PR Template Tools
+
+This module implements a basic MCP server that provides tools for analyzing git changes and suggesting appropriate PR templates.
+
+## Setup
+
+### 1. Install uv
+
+Follow the official installation instructions at: https://docs.astral.sh/uv/getting-started/installation/
+
+### 2. Install dependencies
+
+```bash
+# Install all dependencies
+uv sync
+
+# Or install with dev dependencies for testing
+uv sync --all-extras
+```
+
+### 3. Configure the MCP Server
+
+Add the server to Claude Code:
+
+```bash
+# Add the MCP server
+claude mcp add pr-agent -- uv --directory /absolute/path/to/module1/solution run server.py
+
+# Verify it's configured
+claude mcp list
+```
+
+## Tools Available
+
+1. **analyze_file_changes** - Get the full diff and list of changed files
+2. **get_pr_templates** - List available PR templates with their content
+3. **suggest_template** - Let Claude analyze changes and suggest a template
+
+## Usage Example
+
+1. Make some changes in a git repository
+2. Ask Claude: "Can you analyze my changes and suggest a PR template?"
+3. Claude will:
+   - Use `analyze_file_changes` to see what changed
+   - Analyze the diff to understand the nature of changes
+   - Use `suggest_template` to recommend the most appropriate template
+   - Help you fill out the template based on the specific changes
+
+## How It Works
+
+Unlike traditional template systems that rely on file extensions or simple patterns, this MCP server provides Claude with raw git data and lets Claude's intelligence determine:
+- What type of change is being made (bug fix, feature, refactor, etc.)
+- Which template is most appropriate
+- How to fill out the template based on the actual code changes
+
+This approach leverages Claude's understanding of code and context rather than rigid rules.
+
+## Running Tests
+
+```bash
+# Run the validation script
+uv run python validate_solution.py
+
+# Run unit tests
+uv run pytest test_server.py -v
+```
+
+## Running the Server Directly
+
+```bash
+# Start the MCP server
+uv run server.py
+```

projects/unit3/build-mcp-server/solution/manual_test.md

@@ -0,0 +1,115 @@
+# Manual Testing Guide for Module 1 Solution
+
+## Prerequisites
+
+1. Ensure you're in a git repository with some changes
+2. Install uv following instructions at: https://docs.astral.sh/uv/getting-started/installation/
+3. Install dependencies:
+   ```bash
+   uv sync --all-extras
+   ```
+
+## Test 1: Validate the Solution
+
+Run the automated validation script:
+```bash
+uv run python validate_solution.py
+```
+
+This will check:
+- Git environment
+- Python imports
+- Server creation
+- Tool registration
+- Tool execution
+- Template creation
+
+## Test 2: Run Unit Tests
+
+```bash
+uv run pytest test_server.py -v
+```
+
+## Test 3: Test with Claude Code
+
+1. **Configure MCP Server**
+   
+   Add the server to Claude Code:
+   ```bash
+   # Add the MCP server
+   claude mcp add pr-agent -- uv --directory /absolute/path/to/module1/solution run server.py
+   
+   # Verify it's configured
+   claude mcp list
+   ```
+
+2. **Restart Claude Code** to pick up the new server
+
+3. **Make Some Git Changes**
+   
+   In any git repository:
+   ```bash
+   echo "test change" >> README.md
+   git add README.md
+   ```
+
+4. **Test with Claude**
+   
+   Ask Claude:
+   - "Can you analyze my git changes?"
+   - "What PR templates are available?"
+   - "Based on my changes, which PR template should I use?"
+
+## Test 4: Direct Server Testing
+
+You can also test the server directly:
+
+```python
+import asyncio
+from server import analyze_file_changes, get_pr_templates, suggest_template
+
+async def test():
+    # Test analyze_file_changes
+    changes = await analyze_file_changes("main", True)
+    print("Changes:", changes[:200] + "...")
+    
+    # Test get_pr_templates
+    templates = await get_pr_templates()
+    print("Templates available:", len(json.loads(templates)))
+    
+    # Test suggest_template
+    suggestion = await suggest_template(
+        "Fixed authentication bug", 
+        "bug"
+    )
+    print("Suggestion:", json.loads(suggestion)["recommended_template"]["type"])
+
+asyncio.run(test())
+```
+
+## Expected Behavior
+
+1. **analyze_file_changes** should return JSON with:
+   - base_branch
+   - files_changed
+   - statistics
+   - commits
+   - diff (if include_diff=True)
+
+2. **get_pr_templates** should return JSON array of templates with:
+   - filename
+   - type
+   - content
+
+3. **suggest_template** should return JSON with:
+   - recommended_template
+   - reasoning
+   - template_content
+   - usage_hint
+
+## Troubleshooting
+
+- **"Git not found"**: Ensure you're in a git repository
+- **Import errors**: Check virtual environment is activated
+- **MCP connection failed**: Verify the path in the claude mcp add command is absolute
+- **No tools showing**: Restart Claude Code after adding the server

projects/unit3/build-mcp-server/solution/pyproject.toml

@@ -0,0 +1,28 @@
+[project]
+name = "pr-agent"
+version = "1.0.0"
+description = "MCP server for PR template suggestions"
+readme = "README.md"
+requires-python = ">=3.10"
+dependencies = [
+    "mcp[cli]>=1.0.0",
+]
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=8.3.0",
+    "pytest-asyncio>=0.21.0",
+]
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["."]
+
+[tool.uv]
+dev-dependencies = [
+    "pytest>=8.3.0",
+    "pytest-asyncio>=0.21.0",
+]