|
| 1 | +# Analyze Commit and Create Documentation Issue |
| 2 | + |
| 3 | +Analyze commit `{COMMIT_SHA}` in repository `{REPOSITORY}` using the GitHub MCP server. |
| 4 | + |
| 5 | +## Your Task |
| 6 | + |
| 7 | +1. **Examine the commit** using MCP to access: |
| 8 | + - Commit diff and changed files |
| 9 | + - Current documentation structure |
| 10 | + - Project context |
| 11 | + |
| 12 | +2. **Decide if documentation is needed** based on these criteria: |
| 13 | + |
| 14 | + ### ✅ Document These: |
| 15 | + - Public APIs/Interfaces (functions, classes, endpoints) |
| 16 | + - Complex logic requiring explanation |
| 17 | + - Architectural or workflow changes |
| 18 | + - Breaking changes |
| 19 | + - New dependencies or integrations |
| 20 | + - Security/performance changes |
| 21 | + - Database schemas or data models |
| 22 | + - Unit tests |
| 23 | + |
| 24 | + ### ❌ Skip These: |
| 25 | + - Minor refactoring or formatting |
| 26 | + - Internal helpers |
| 27 | + - Trivial typo fixes |
| 28 | + - Code moves without logic changes |
| 29 | + - Patch dependency updates |
| 30 | +in the current repository |
| 31 | + - Add labels: `documentation`, `automated` |
| 32 | +3. **If documentation is needed:** |
| 33 | + - Use the GitHub MCP server to create a GitHub issue with title: "📚 Documentation needed for commit test" |
| 34 | + - Use assign_copilot_to_issue tool to assign @copilot to issue. |
| 35 | + - In the issue body, explain: |
| 36 | + - What changed and why it needs documentation |
| 37 | + - Which documentation files should be updated |
| 38 | + - Any breaking changes or migration notes needed |
| 39 | + - Confirm if all steps succeeded or not. |
| 40 | + |
| 41 | +4. **If documentation is NOT needed:** |
| 42 | + - Simply explain why in a brief response (no issue needed) |
0 commit comments