Reusable workflows, actions, presets, agent skills, and testing utilities for consistent engineering across projects.
- Turn repeated setup and maintenance into reusable automation
- Build composable CI/CD workflows and GitHub Actions
- Standardize dependency updates, releases, and project scaffolding
- Share portable agent workflows with explicit safety and recovery boundaries
- Make Docker Compose validation reliable and easy to diagnose
- Create practical testing utilities for real delivery pipelines
We build small, dependable tools that remove repetitive work from software delivery. The goal is straightforward: consistent project setup, predictable CI, safer dependency maintenance, and clear diagnostics when something fails.
| Repository | Version | Description |
|---|---|---|
| project-toolkit |  |
Reusable workflows, composite actions, and Copier templates for Python, Node.js, Java, Docker, and polyglot repositories. |
| renovate-presets |  |
Shared Renovate presets for consistent, reviewable dependency updates across projects. |
| Repository | Version | Description |
|---|---|---|
| skills |  |
Portable skills, adapters, and safety-focused execution patterns for Hermes, Claude Code, Codex, and compatible agents. |
| Repository | Version | Description |
|---|---|---|
| compose-health-check-action |  |
Runs Docker Compose with health checks, platform detection, and actionable failure diagnostics. |
| gh-pages-subdir-action |  |
Publishes generated sites and test reports into isolated GitHub Pages subdirectories while preserving sibling deployments. |
| allure-report-action |  |
Builds Allure reports, badges, and idempotent pull-request test summaries, with optional pyramid artifacts and Pages publishing. |
| Repository | Version | Description |
|---|---|---|
| q4j |  |
Modular Java libraries and integrations for test automation and quality engineering. |
project-toolkit
Scaffolding • CI workflows
↓
renovate-presets
Dependency maintenance
↓
compose-health-check-action + allure-report-action + q4j
Service, report, and test verification
Each repository can be used independently. Together they form a practical automation layer for creating, maintaining, and validating software projects without copying the same setup from repository to repository.
- Reusable over repeated — common engineering work belongs in versioned building blocks
- Composable over monolithic — adopt only the automation a project needs
- Predictable over clever — explicit versions, reviewable updates, and stable contracts
- Diagnostics by default — failures should explain what broke and where to look
- Automation with control — routine work runs automatically; important changes stay visible
Build once. Automate forever.
Good automation should save time without hiding how a project works. We favor tools that are easy to adopt, safe to update, and useful across different stacks.
Ideas, issues, and contributions are welcome. If you find repetitive engineering work that could become a reusable tool—or see a way to improve an existing project—open an issue in the relevant repository.