task-check

Task Check (QA Verification)

Verify that the implementation on the current branch satisfies the requirements defined in the linked GitHub issue. This is a QA gate that ensures we built what was asked for.

Arguments

• {issue} -- GitHub issue number (optional, extracted from branch name if not provided)
• --strict -- Fail on any unmet criterion (default: fail only on "Must Have" criteria)

Configuration

Auto-detect the GitHub repository from git remote -v (extract owner and repo name). If cloudstack.json exists, it may contain a project.repository field as a fallback.

Process

Step 1: Identify the Issue

# Get current branch
BRANCH=$(git branch --show-current)

# Extract issue number from branch name (e.g., username/42-feature-name)
ISSUE=$(echo "$BRANCH" | grep -oE '/[0-9]+' | tr -d '/')

# If no issue in branch name and not provided as argument, fail
if [ -z "$ISSUE" ]; then
  echo "ERROR: Could not determine issue number. Provide as argument: /task-check 42"
  exit 1
fi

# Auto-detect repo from git remote
REPO_URL=$(git remote get-url origin)
OWNER=$(echo "$REPO_URL" | sed -E 's#.*[:/]([^/]+)/[^/]+(\.git)?$#\1#')
REPO=$(echo "$REPO_URL" | sed -E 's#.*[:/][^/]+/([^/]+?)(\.git)?$#\1#')

Step 2: Fetch Issue Details

Use MCP for structured issue data:

mcp__github-mcp-server__get_issue(owner: "${OWNER}", repo: "${REPO}", issue_number: $ISSUE)

This returns structured JSON with number, title, body, labels, state, and comments -- no CLI output parsing needed.

Step 3: Parse Acceptance Criteria

Extract acceptance criteria from the issue body. Look for:

• Checkbox lists: - [ ] Criterion
• "Acceptance Criteria" section
• "Requirements" section
• "Definition of Done" section
• User stories with "so that" format

Categorize each criterion:

• Must Have: Explicitly marked as required, or in "Acceptance Criteria"
• Should Have: Listed but not critical
• Nice to Have: Suggestions, future improvements mentioned