codegeass-testing

Run pre-merge regression tests across CodeGeass CLI commands and Dashboard API endpoints.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/DonTizi/CodeGeass --skill codegeass-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codegeass-testing
Source: https://github.com/DonTizi/CodeGeass/tree/main/.claude/skills/codegeass-testing
Command: npx skills add https://github.com/DonTizi/CodeGeass --skill codegeass-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates pre-merge verification and regression testing for CodeGeass. It ensures PR changes are validated before merging and that the full CLI and Dashboard API workflows remain stable.

Core Features & Use Cases

  • Pre-merge verification: automatically runs a focused suite on incoming PRs to catch regressions early.
  • Regression across CLI & API: executes end-to-end tests covering CLI commands and Dashboard API endpoints to ensure system integrity.
  • Artifacts & reporting: aggregates test results and surfaces actionable insights for developers and reviewers.

Quick Start

Run the pre-merge testing workflow in your PR by triggering the testing script or command defined for the CodeGeass project, then review the reported results and dashboards for any failures.

Frequently Asked Questions about codegeass-testing

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

FAQPage Schema
How do I automate pre-merge testing for CodeGeass PR changes?

Pre-merge testing for CodeGeass PR changes is automated by triggering a testing script that runs a focused suite on incoming PRs, catching regressions early. It reports outcomes for rapid merging decisions.

What does regression testing for CLI commands and Dashboard API endpoints cover?

Regression testing covers end-to-end execution across CLI commands and Dashboard API endpoints to validate system integrity. It ensures the full CodeGeass workflows remain stable after new changes.

Do I need network access to run CodeGeass dashboard and endpoint tests?

Yes, network access is required to run dashboards and endpoints during CodeGeass testing. The implementation relies on the CodeGeass CLI, test scripts, and network connectivity to execute dashboard API tests.

How are test results and artifacts reported for CodeGeass pre-merge verification?

Test results and artifacts for CodeGeass pre-merge verification are aggregated and surfaced as actionable insights for developers and reviewers. Reporting highlights failures to guide rapid decisions.

Can I use this pre-merge testing skill without the CodeGeass CLI installed?

No, the CodeGeass CLI is a required dependency for this pre-merge testing skill. The implementation relies on the CodeGeass CLI and test scripts to execute regression tests and validate PR changes.

Why run regression tests before merging CodeGeass pull requests?

Running regression tests before merging CodeGeass pull requests ensures PR changes are validated and that full CLI and Dashboard API workflows remain stable. This prevents regressions from entering the main branch.