Civitas Cerebrum
Official@civitas-cerebrum · Netherlands
Developing automation solutions
Agent Skills by Civitas Cerebrum
Showing 25 vetted skills indexed across 2 GitHub repositories.
civitas-cerebrumperformance-testing
Writes and runs k6 load tests that verify latency and error-rate SLOs via thresholds.
civitas-cerebrumdatabase-testing
Writes and runs SQL-backed tests asserting row counts, cell values, and transaction behavior via the Steps API.
civitas-cerebrumcompanion-mode
Runs single-task Playwright verifications and produces evidence bundles with screenshots, video, trace, and HAR.
civitas-cerebrumsecrets-sweep
Extracts hardcoded credentials, API keys, and URLs from Playwright test suites into .env files.
civitas-cerebrumticket-driven-testing
Verifies ticket and PR changes with Playwright evidence bundles, negative controls, and sentinel tests.
civitas-cerebrumcontributing-to-achilles-protocol
Guides contributions to the element-interactions Playwright facade package and its skill suite.
civitas-cerebrumself-repair
Repairs failing Playwright test suites by fanning out one repair worker per red spec file.
civitas-cerebrumtest-catalogue
Generate a stakeholder-facing PDF catalogue of Playwright test scenarios grouped by section and priority.
civitas-cerebrumselector-development
Adds a single inert test attribute to frontend elements lacking stable selectors for e2e tests.
civitas-cerebrumtest-data-conventions
Defines test data generation, resolution, and cleanup rules for Playwright end-to-end suites.
civitas-cerebrumbug-report
Generates structured Jira defect tickets with reproduction steps, severity, and traceability fields.
civitas-cerebrumperf-onboarding
Bootstraps a gated k6 performance test suite from zero through seven enforced phases.
civitas-cerebrumworkflow-reviewer
Reviews pipeline phase handovers against methodology exit criteria and returns approve, reject, or escalate verdicts.
civitas-cerebrumachilles-protocol
Orchestrates staged Playwright end-to-end test authoring, diagnosis, and coverage workflows.
civitas-cerebrumcontract-testing
Writes contract-style API tests asserting status codes, headers, and response schemas with Playwright.
civitas-cerebrumelement-interactions
Runs Playwright UI tests using a page-repository-driven model with separated element acquisition and interaction.
civitas-cerebrumagents-vs-agents
Evaluate adversarial AI behavior across triad interactions to uncover guardrail weaknesses.
civitas-cerebrumtest-repair
Repairs flaky or failing Playwright test suites via a multi-stage pipeline with clustered fixes and targeted validation.
civitas-cerebrumwork-summary-deck
Generate a self-contained HTML QA summary deck from project test data.
civitas-cerebrumtest-composer
Generates and updates a full test portfolio for a user journey using the Steps API.
civitas-cerebrumbug-discovery
Probe deployed apps for software bugs after test suites pass.
civitas-cerebrumfailure-diagnosis
Diagnose failing Playwright tests through evidence-based triage of traces, screenshots, and console logs.
civitas-cerebrumcoverage-expansion
Coordinate journey-level test coverage expansion across a mapped application.
civitas-cerebrumjourney-mapping
Discovers web application pages and user flows via Playwright to produce a prioritized journey map.
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.