For teams with a Playwright suite on GitHub who want a test for each new feature without writing it themselves.

Your setup

A Playwright suite in a GitHub repo, with your own fixtures, page objects and naming.
The new feature is already deployed to a test environment, for example staging.
You review every change as a pull request.

Say this to Certyn

Add a Playwright test for the new coupon field on checkout in github.com/acme/web. Follow our style and open a PR.

If there is no GH_TOKEN yet, opens a form for it. Make a fine-grained token for that one repo with Contents and Pull requests set to Read and write. It is saved as a secret project variable, never shown in the chat.
Saves the repo as a project variable (GITHUB_REPO) so later runs know it.
Clones the repo and reads the tests next to the feature: folders, fixtures, page objects, locator style, naming.
Looks at the feature on the environment in a real browser to learn the real flow and texts.
Writes the test on a certyn/... branch, reusing your helpers instead of adding new ones.
Runs the new test several times against the environment.
Opens a pull request that says what the test covers and how it was checked.

One pull request with the new test, in your folders and style.
A run report. If the feature itself is broken, a Certyn issue with evidence instead of a test that hides it.

The test runs against a Certyn environment. If the feature is not deployed there yet, Certyn cannot check the test. Deploy it first, or give Certyn the preview URL as an environment.
Certyn never merges and never pushes to your default branch. You review and merge.
Tests that need Java or Docker: use a self-hosted runner, or let Certyn install a JDK at each cloud run.