Civitas Cerebrum
Official@civitas-cerebrum · Netherlands
Developing automation solutions
Agent Skills by Civitas Cerebrum
Showing 11 vetted skills indexed across 1 GitHub repositories.
contract-testing
Write contract tests for HTTP APIs using the Steps API.
element-interactions
Runs Playwright UI tests using a page-repository-driven model with separated element acquisition and interaction.
agents-vs-agents
Evaluate adversarial AI behavior across triad interactions to uncover guardrail weaknesses.
test-repair
Repairs flaky or failing Playwright test suites via a multi-stage pipeline with clustered fixes and targeted validation.
work-summary-deck
Generate a self-contained HTML QA summary deck from project test data.
test-composer
Generates and updates a full test portfolio for a user journey using the Steps API.
bug-discovery
Probe deployed apps for software bugs after test suites pass.
failure-diagnosis
Diagnose failing Playwright tests through evidence-based triage and root-cause analysis.
coverage-expansion
Coordinate journey-level test coverage expansion across a mapped application.
journey-mapping
Generates a prioritized journey map with sub-journeys and test expectations from a web application.
onboarding
Orchestrate autonomous onboarding of new apps to the element-interactions framework.
Frequently Asked Questions About Civitas Cerebrum
FAQPage SchemaWhat specific quality assurance tasks does Civitas Cerebrum enable?▼
Civitas Cerebrum enables automated journey mapping, contract verification for HTTP interfaces, and systematic repair of flaky UI test suites. It further supports bug discovery in deployed environments and generates comprehensive HTML summary decks from project test data to visualize coverage and failure diagnostics.
Which engineering personas benefit from these capabilities?▼
These capabilities are designed for Quality Assurance Engineers, Software Development Engineers in Test (SDETs), and Reliability Engineers. The framework specifically targets teams managing complex Playwright-based test suites who require advanced triage, journey-level coverage expansion, and adversarial behavior testing to maintain high-velocity release cycles.
What are the prerequisites for integrating these testing capabilities?▼
Integration requires an existing Playwright-based testing environment and a defined application structure. Users must implement the Steps interface for contract verification and adopt the page-repository-driven model for element interactions to enable the framework's diagnostic, repair, and onboarding functions effectively.