Verified:GitHub

test-reporting

Post QA test results to GitLab issues via the REST API.

Updated Aug 23, 2026

Search Tags:#automation #qa #gitlab #test-reporting #test-status #issue-comments #qa-comments

One-click install

npx skills add https://github.com/midas44/ttt-expert-v2 --skill test-reporting

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: test-reporting
Source: https://github.com/midas44/ttt-expert-v2/tree/main/.claude/skills/test-reporting
Command: npx skills add https://github.com/midas44/ttt-expert-v2 --skill test-reporting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post QA test results to GitLab issues using a standardized, readable comment format to streamline communication and traceability.

Core Features & Use Cases

Post structured QA test result comments on GitLab issues via the REST API.
Use when documenting testing status, findings, or test summaries directly on a ticket.
Automatically adhere to the defined QA comment schema to ensure consistency across issues.

Quick Start

Post a sample QA test result to an issue by providing the issue number and the results payload.

Frequently Asked Questions about test-reporting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I post QA test results directly to a GitLab issue?▼

To post QA test results to a GitLab issue, you provide the issue number and test results payload. The skill uses the GitLab REST API to submit a structured comment documenting the testing status and findings directly on the ticket.

What is the best way to automate posting test status comments on GitLab tickets?▼

Automating test status comments on GitLab tickets is achieved by applying a standardized QA comment schema via the GitLab REST API. This ensures consistent documentation of test summaries and findings across multiple projects.

Do I need a GitLab API token to document testing findings on issues?▼

Yes, you need a GitLab API token to document testing findings. The skill reads the required API token from the .claude/.mcp.json configuration file to authenticate and post comments to the GitLab REST API.

Can I use this approach to standardize QA comments across different projects?▼

Yes, you can standardize QA comments across different projects. The skill automatically adheres to a defined QA comment schema, ensuring that testing status, summaries, and findings remain readable and consistent across all GitLab issues.

What format is required for the test results payload when posting to GitLab?▼

The test results payload must conform to a standardized, readable comment format defined by the QA schema. This structured format ensures that testing status, findings, and test summaries are properly documented and traceable on GitLab tickets.