VCS Issue Management (Agnostic)
Workflow
- •Information Gathering: Read the latest comments and current state of the issue.
- •Action Definition: Determine if you need to comment, assign, change state, or update the description.
- •Drafting:
- •Write in English only.
- •Use Markdown (Titles, Subtitles, Code Snippets, Items).
- •Use Emojis for clarity and tone.
- •Follow patterns from references/communication.md.
- •MITM Confirmation: Stop and present the drafted text to the USER for approval.
- •Execution: After approval, map to the correct platform tool (GitHub/GitLab).
Tool Mapping
| Action | GitHub Tool (mcp__github__) | GitLab Tool (mcp__gitlab__) |
|---|---|---|
| Comment | add_issue_comment(owner, repo, issue_number, body) | create_issue_note(project_id, issue_iid, body) |
| Change State | update_issue(..., state: 'open'|'closed') | edit_issue(..., state_event: 'reopen'|'close') |
| Assign | update_issue(..., assignees: [u1]) | edit_issue(..., assignee_ids: [id]) |
| Edit Body | update_issue(..., body: '...') | edit_issue(..., description: '...') |
Strategic Updates
- •Blockers: Post an immediate update using the Blocker template if progress stops.
- •Delays: Notify stakeholders as soon as a delay is detected with a revised ETA.
- •Planning: Propose an approach before starting complex work to get early feedback.
- •Professionalism: Always maintain a solution-oriented tone.
Guidelines
- •Be Concise: Avoid repetitive or redundant comments.
- •Context Awareness: Link relevant commits, PRs, or other issues.
- •State Hygiene: Close issues promptly when work is completed and verified.