mockserver-monorepo: Skill for OpenCode

GitHub Issue Review and Resolution

Systematically review a GitHub issue to determine its validity, classify it, and take the appropriate action — whether that is improving documentation, fixing a bug, or closing as not-a-bug.

Prerequisites

• gh CLI authenticated to github.com (gh auth login --hostname github.com)

gh auth status --hostname github.com 2>/dev/null || echo "ERROR: run 'gh auth login --hostname github.com'"

Repository

• Owner: mock-server
• Repo: mockserver

Step 1: Parse Input and Fetch Issue

Extract the issue number from the user's input (URL or number).

URL Pattern:

https://github.com/mock-server/mockserver-monorepo/issues/{number}

Fetch the full issue with comments:

gh issue view {number} --repo mock-server/mockserver-monorepo --json number,title,body,author,createdAt,updatedAt,state,labels,comments,assignees

Read the issue carefully. Extract:

• Reported behaviour: what the user says is happening
• Expected behaviour: what the user expected
• Steps to reproduce: how to trigger the issue
• Environment: MockServer version, Java version, OS, deployment method (Docker, JAR, WAR, Maven plugin)
• Configuration: any custom properties, expectations, or settings mentioned
• Error messages: exact error text, stack traces, or log output
• Attachments: links to logs, screenshots, or configuration files

If critical information is missing (no version, no reproduction steps, no error output), note this as a gap but continue investigation with what is available.

Step 2: Validate the Issue — Is This Still Relevant?

Before deep investigation, check if the issue is outdated:

2a: Check MockServer Version

# Current released version
gh release list --repo mock-server/mockserver-monorepo --limit 1 --json tagName,publishedAt

# Version from pom.xml (development version — target the project version, not parent/plugin)
grep -m1 'SNAPSHOT' mockserver/pom.xml | sed 's/.*<version>\(.*\)<\/version>.*/\1/'