skills.rest
CodeMachine0121
CodeMachine0121COMMUNITY
Explore all skills by this author →
WebsiteGitHub

gti-verify

Execute the final GTI workflow verification phase with test coverage and Playwright MCP validation.

Updated Aug 27, 2026
Search Tags:#code quality#testing#tdd#e2e#verification#playwright#bdd
One-click install
npx skills add https://github.com/CodeMachine0121/gti-agent-cycle-skill --skill gti-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gti-verify
Source: https://github.com/CodeMachine0121/gti-agent-cycle-skill/tree/main/skills/gti-verify
Command: npx skills add https://github.com/CodeMachine0121/gti-agent-cycle-skill --skill gti-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the final verification phase of the GTI development workflow, ensuring code quality and adherence to specifications before completion.

Core Features & Use Cases

  • Test Coverage Cross-check: Verifies that every feature scenario is mapped to a unit test with actual assertions.
  • Full Test Suite Execution: Runs all unit tests to ensure no regressions or new failures.
  • End-to-End (E2E) Validation: Uses Playwright MCP to validate scenarios in a running application.
  • Conclusion Document Generation: Creates a comprehensive report summarizing the verification results.
  • Use Case: After implementing a new feature, use this Skill to automatically confirm that all tests pass, coverage is complete, and the feature behaves as expected in the live application.

Quick Start

Run the gti-verify skill to finalize the verification of the new user authentication feature.

Frequently Asked Questions about gti-verify

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

FAQPage Schema
How do I verify code against specs and run E2E tests after implementing a feature?▼

End-to-end validation with Playwright MCP works by validating feature scenarios in a running application, confirming expected behavior. It requires detecting application startup scripts to comprehensively validate scenarios and ensure the feature behaves as expected live.

Do I need to provide project test commands and startup scripts for E2E validation?▼

Yes, E2E validation requires detecting project test commands and application startup scripts. This environment setup is necessary to run the full test suite and perform comprehensive validation via Playwright MCP against the live application.

How do I generate a verification conclusion document after running unit and E2E tests?▼

Generating a verification conclusion document happens automatically after cross-checking test coverage and running E2E validation. It summarizes the verification results, detailing whether all tests pass, coverage is complete, and the feature behaves as expected.

What are the limitations of automating spec verification and E2E testing?▼

Limitations of automating spec verification include the dependency on detecting project test commands and application startup scripts. Without these environment configurations, comprehensive E2E validation via Playwright MCP cannot be executed successfully.

Related Skills

Explore More Software Engineering Skills→
AshDaxAshDax

run-locally

Launch the agent locally and test API endpoints via curl.

Community
Intermediate
xg-gh-25xg-gh-25
36

health-check

Execute deterministic health checks on SwarmAI subsystems and summarize pass/fail results for CI workflows.

Community
Advanced
Svenja-devSvenja-dev
38

e2e-testing

Automate end-to-end browser testing for web applications with Playwright MCP.

Community
Intermediate
etylsarinetylsarin
59

testing-workflow

Plan, execute, and validate unit, integration, and E2E tests for feature releases.

Community
Advanced