local-dev-environment
Skill2 starsChanged 19 days agoApache-2.0View on GitHub
Start, stop, or check status of local dev environment using Podman Compose. Database, app services, migrations, health checks. Use when user says "start local env", "podman compose up", "dev environment status".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Hachimeder/local-dev-environment-skilltheir own version, first seen Oct 9, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Hachimeder/local-dev-environment-skill★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository124 other files it gives its agents.
- add-projectSkill
- ansible-configure-vmSkill
- api-smoke-testSkill
- appinterface-checkSkill
- attach-session-to-jiraSkill
- aws-rds-debugSkill
- beerSkill
- bootstrap-all-knowledgeSkill
- bootstrap-knowledgeSkill
- build-persona-styleSkill
- cancel-pipelineSkill
- cert-checkSkill
- check-ci-healthSkill
- check-integration-testsSkill
- check-mr-feedbackSkill
- check-my-prsSkill
- check-secretsSkill
- ci-retrySkill
- cleanup-branchesSkill
- cleanup-stale-executionsSkill
- clone-jira-issueSkill
- close-issueSkill
- close-mrSkill
- cloud-inventorySkill
- coffeeSkill
- compare-optionsSkill
- create-jira-issueSkill
- create-mrSkill
- create-slide-deckSkill
- data-migration-verifySkill
- debug-local-dbSkill
- debug-prodSkill
- deploy-to-ephemeralSkill
- dev-workflow-orchestratorSkill
- discovered-work-summarySkill
- edit-slide-deckSkill
- email-digestSkill
- environment-overviewSkill
- explain-codeSkill
- export-presentationSkill
- extend-ephemeralSkill
- find-similar-codeSkill
- gather-contextSkill
- gdrive-researchSkill
- gke-cluster-opsSkill
- hello-worldSkill
- hotfixSkill
- inscope-researchSkill
- investigate-alertSkill
- investigate-service-issuesSkill
- investigate-slack-alertSkill
- jira-hygiene-allSkill
- jira-hygieneSkill
- knowledge-refreshSkill
- konflux-statusSkill
- learn-architectureSkill
- learn-patternSkill
- list-presentationsSkill
- local-build-testSkill
- manage-local-servicesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Start, stop, or check status of local development environment using Podman Compose.
- Very specific: line 34
If action in [stop, restart]: podman_compose_down(project_dir=repo)
- Very specific: line 35
If action in [start, restart]: podman_compose_up(project_dir=repo, detach=true)
- Very specific: line 42
If run_migrations and action in [start, restart]: podman_exec(container="{repo_basename}-app-1", command="python manage.py migrate")
- Very specific: line 60
Run migrations: include run_migrations: true in inputs
≈ “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
Local Dev Environment
Start, stop, or check status of local development environment using Podman Compose.
Inputs
| Input | Type | Default | Purpose |
repo | string | required | Path to repo with podman-compose.yaml |
action | string | "status" | start, stop, status, restart |
run_migrations | bool | false | Run DB migrations after start |
health_check | bool | true | Run health check after start |
Persona
Load devops persona (podman, systemd). May need developer for curl; database for psql.
Workflow
1. Bootstrap
persona_load("devops")— podman toolssystemctl_is_active(unit="podman.socket")— ensure Podman socket active
2. Current Status
podman_compose_status(project_dir=repo)— compose statuspodman_ps()— running containers
3. Perform Action
- If action in [stop, restart]:
podman_compose_down(project_dir=repo) - If action in [start, restart]:
podman_compose_up(project_dir=repo, detach=true)
4. Post-Start (if action != status)
podman_compose_status(project_dir=repo)— verify statuspodman_logs(container="{repo_basename}-app-1", tail=30)— recent logs
5. Database
- If run_migrations and action in [start, restart]:
podman_exec(container="{repo_basename}-app-1", command="python manage.py migrate") psql_tables()— list tables (verify DB ready)psql_query(query="SELECT 1 as health_check;")— connectivity
6. Health Check (if health_check)
curl_get(url="http://localhost:8000/api/v1/health/")— API healthcurl_timing(url="http://localhost:8000/api/v1/health/")— response time
7. Error Handling
- On "port already in use": stop conflicting process or
podman_compose_downfirst - On "connection refused": wait for container startup, check
podman_logs
8. Session Log
memory_session_log("Local dev environment: {action}", "repo={repo}")
Quick Actions
- View logs:
podman_logs(container="<name>", tail=50) - Run migrations: include
run_migrations: truein inputs - Restart:
skill_run("local_dev_environment", '{"repo": "...", "action": "restart"}')
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

