docker-compose-healthcheck-injector
Skill14 starsChanged 5 months agoApache-2.0View on GitHub
Ensures every service in a Docker Compose file has a healthcheck block and depends_on uses condition: service_healthy. Trigger when generating or editing compose.yaml.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/aiup-alfresco.mdcCursor rule
- aca-extensionSkill
- actionsSkill
- aikauSkill
- aiup-alfrescoSkill
- alfresco-architect-agentSkill
- alfresco-debugger-agentSkill
- alfresco-migrator-agentSkill
- audit-config-validatorSkill
- auditSkill
- behavioursSkill
- bootstrap-loaderSkill
- content-modelSkill
- content-model-validatorSkill
- content-storeSkill
- docker-compose-healthcheck-injectorSkill
- docker-composeSkill
- event-api-topology-checkerSkill
- eventsSkill
- metadata-extractorSkill
- migration-advisorSkill
- permission-aware-query-builderSkill
- permission-model-validatorSkill
- permissionsSkill
- repository-patchSkill
- requirementsSkill
- rest-apiSkill
- rest-api-validatorSkill
- rule-conditionsSkill
- scaffoldSkill
- scheduled-jobsSkill
- sdk-version-detectorSkill
- share-configSkill
- subsystemSkill
- surfSkill
- testSkill
- transformsSkill
- web-scriptsSkill
- workflow-bpmn-validatorSkill
- workflowSkill
- audit-config-validatorSkill
- content-model-validatorSkill
- event-api-topology-checkerSkill
- migration-advisorSkill
- permission-aware-query-builderSkill
- permission-model-validatorSkill
- rest-api-validatorSkill
- sdk-version-detectorSkill
- workflow-bpmn-validatorSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Verify these services are present (when applicable):
- Very specific: line 21
Every service must have a healthcheck block with:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Docker Compose Healthcheck Injector
Validate and fix Docker Compose files for Alfresco deployments.
Required Services
Verify these services are present (when applicable):
alfresco— ACS repositorypostgres— databaseactivemq— message brokertransform-core-aioor individual transform servicessearch— Solr or Elasticsearchshare— (optional, if Share UI is used)
Healthcheck Rules
Every service must have a healthcheck block with:
test— appropriate health endpoint or commandinterval— recommended 30stimeout— recommended 10sretries— recommended 3start_period— recommended 60s for Alfresco, 30s for others
Dependency Rules
depends_onmust usecondition: service_healthy(not just service name)alfrescodepends onpostgresandactivemqsharedepends onalfrescosearchdepends onalfresco(for Solr) or is independent (Elasticsearch)
Known Healthcheck Endpoints
- Alfresco:
curl -f http://localhost:8080/alfresco/api/-default-/public/alfresco/versions/1/probes/-ready- - Share:
curl -s -o /dev/null -w '%{http_code}' http://localhost:8080/share/ | grep -qE '^[23]' - ActiveMQ:
curl -sf -u $${ACTIVEMQ_USER:-admin}:$${ACTIVEMQ_PASSWORD:-admin} http://localhost:8161/admin/ > /dev/null - PostgreSQL:
pg_isready -d alfresco -U alfresco - Solr (Search Services):
curl -f -H "X-Alfresco-Search-Secret: $${SOLR_ALFRESCO_SECRET}" http://localhost:8983/solr/alfresco/admin/ping - OpenSearch / Elasticsearch (Search Enterprise):
curl -s http://localhost:9200/_cluster/health | grep -q 'green\|yellow' - Transform:
curl -f http://localhost:8090/ready
Share Healthcheck — known bad patterns
FLAG as ERROR any Share healthcheck that uses a path other than /share/:
| Bad pattern | Why it fails |
http://localhost:8080/share/page/home | /page/home does not exist in Share 26.x — Spring Surf throws a 500 Could not resolve view 'home'; the container stays health: starting forever and blocks dependent services (proxy) |
http://localhost:8080/share/page/dashboard | Same issue — page routes are user-session-dependent |
Correct pattern: accept any 2xx or 3xx from the Share root (it redirects to the login page):
test: ["CMD-SHELL", "curl -s -o /dev/null -w '%{http_code}' http://localhost:8080/share/ | grep -qE '^[23]'"]Output
List all missing healthchecks and incorrect dependencies. Provide corrected YAML blocks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

