[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75852S1DXSQJN4EPKPQW55M":3,"skill-same:01M75852S1DXSQJN4EPKPQW55M":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M75852S1DXSQJN4EPKPQW55M","docker-test-isolation-harness",null,"Isolated throwaway containers for Docker test runs.","lukemcqueen\u002Fsteadfaste-fleet","lukemcqueen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F405240?v=4","01M757MHPAGRXTJAT46SKZP98R","Luke McQueen","01M757MHPZ573KP8DT9GB8SBQ7",4,"MIT","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fdocker-test-isolation-harness\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: docker-test-isolation-harness\ndescription: \"Isolated throwaway containers for Docker test runs.\"\ncategory: devops\nversion: 1.0.0\nplatforms: [linux, macos]\n---\n\n# Docker Test Isolation Harness\n\nRun a Docker-based project's integration test suite WITHOUT bringing up its full compose stack\non a shared host where that stack would collide with other running services. Uses isolated\nthrowaway containers with unique names\u002Fports, then tears them down.\n\n## When to Use\n\nTrigger when the project's stack can't come up safely on the host, yet the suite needs a real\nPostgres\u002FRedis:\n- The compose uses generic `container_name: postgres` \u002F `redis` that collide with another\n  project's already-running containers of the same name — running yours would attach to or\n  disturb the wrong project's DB.\n- You must not touch running services (a sibling project's production DB sharing the host).\n\n## Prerequisites\n- Docker CLI on the host (`docker ps`).\n- The project's own Python `.venv` with pytest + alembic installed (or the equivalent runner).\n\n## Diagnose ownership first (never assume)\n\n```bash\n# Which project owns the running 'postgres'? Read the compose-project label.\ndocker inspect postgres --format \\\n  'project={{index .Config.Labels \"com.docker.compose.project\"}} \\\n  workdir={{index .Config.Labels \"com.docker.compose.project.working_dir\"}}'\ndocker ps --format '{{.Names}}\\t{{.Status}}\\t{{.Ports}}'  # non-default port maps reveal a sibling\n```\n\nA postgres on `13211->5432` is *not* your project's default `5432` — it belongs to someone else.\n\n## Procedure\n\n```bash\n# 1. Throwaway Postgres + Redis with UNIQUE names and free ports.\ndocker run -d --name \u003Cproj>-test-pg -e POSTGRES_USER=\u003Cuser> -e POSTGRES_PASSWORD=\u003Cpw> \\\n  -e POSTGRES_DB=\u003Cdb> -p 127.0.0.1:\u003Cp1>:5432 postgres:16-alpine\ndocker run -d --name \u003Cproj>-test-redis -p 127.0.0.1:\u003Cp2>:6379 redis:7-alpine\n# wait for readiness: for i in $(seq 1 30); do \\\n#   docker exec \u003Cproj>-test-pg pg_isready -U \u003Cuser> >\u002Fdev\u002Fnull 2>&1 && break; sleep 1; done\n\n# 2. Point the app\u002Ftests at them via env. Env overrides .env in pydantic-settings.\nexport DATABASE_URL=\"postgresql:\u002F\u002F\u003Cuser>:\u003Cpw>@127.0.0.1:\u003Cp1>\u002F\u003Cdb>\"\nexport REDIS_URL=\"redis:\u002F\u002F127.0.0.1:\u003Cp2>\u002F0\"\n\n# 3. Alembic reads sqlalchemy.url from alembic.ini, NOT env -> throwaway ini via -c.\n#    env.py's sys.path insert is anchored to env.py location, so -c from \u002Ftmp still imports the project.\n#    [alembic] script_location = \u003Cabs>\u002F...\u002Fmigrations ; sqlalchemy.url = postgresql:\u002F\u002F\u003Cuser>:\u003Cpw>@127.0.0.1:\u003Cp1>\u002F\u003Cdb>\n.venv\u002Fbin\u002Fpython -m alembic -c \u002Ftmp\u002F\u003Cproj>-test-alembic.ini upgrade head\n\n# 4. Run the suite. The test harness spawns its own server subprocess -> inherits the env.\nDATABASE_URL=... REDIS_URL=... .venv\u002Fbin\u002Fpython -m pytest tests\u002F -q\n\n# 5. Teardown AND confirm the sibling project is still up.\ndocker rm -f \u003Cproj>-test-pg \u003Cproj>-test-redis && rm -f \u002Ftmp\u002F\u003Cproj>-test-alembic.ini\ndocker ps --format '{{.Names}}' | grep -E '^(postgres|redis|worker)$'   # sibling set present\n```\n\n## Pitfalls\n- **Endpoint dialect must match the app**: a sync SQLAlchemy `create_engine` wants `postgresql:\u002F\u002F`\n  (psycopg2), NOT `postgresql+asyncpg`. Match the project's database.py \u002F config default.\n- **Route env directly, not through `.\u002Frun`**: the suite's spawned subprocess inherits YOUR\n  exported env; a `.\u002Frun` wrapper may source `.env` and clobber the override.\n- **Check ports free first**: `nc -z 127.0.0.1 \u003Cport>` before `docker run -p`.\n- **Teardown is mandatory** — leftover `-test-` containers clutter the host and can be mistaken\n  for the real stack.\n\n## Related\n- The underlying collision (generic `container_name: postgres`\u002F`redis` across projects) and its\n  permanent fix (unique container names per project) is covered in the `engineering-approach` skill.\n- A sibling source-control hazard — an unanchored `api\u002F` gitignore silently dropping an app dir\n  from git — is in `git-forensics` \u002F `git-pull-local-changes`.\n\n## Verification\n- Full suite green against throwaway infra; count matches baseline after any fixture fixes.\n- Sibling containers reported by the teardown ownership check are unchanged.\n","# Docker Test Isolation Harness\n\nRun a Docker-based project's integration test suite WITHOUT bringing up its full compose stack\non a shared host where that stack would collide with other running services. Uses isolated\nthrowaway containers with unique names\u002Fports, then tears them down.\n\n## When to Use\n\nTrigger when the project's stack can't come up safely on the host, yet the suite needs a real\nPostgres\u002FRedis:\n- The compose uses generic `container_name: postgres` \u002F `redis` that collide with another\n  project's already-running containers of the same name — running yours would attach to or\n  disturb the wrong project's DB.\n- You must not touch running services (a sibling project's production DB sharing the host).\n\n## Prerequisites\n- Docker CLI on the host (`docker ps`).\n- The project's own Python `.venv` with pytest + alembic installed (or the equivalent runner).\n\n## Diagnose ownership first (never assume)\n\n```bash\n# Which project owns the running 'postgres'? Read the compose-project label.\ndocker inspect postgres --format \\\n  'project={{index .Config.Labels \"com.docker.compose.project\"}} \\\n  workdir={{index .Config.Labels \"com.docker.compose.project.working_dir\"}}'\ndocker ps --format '{{.Names}}\\t{{.Status}}\\t{{.Ports}}'  # non-default port maps reveal a sibling\n```\n\nA postgres on `13211->5432` is *not* your project's default `5432` — it belongs to someone else.\n\n## Procedure\n\n```bash\n# 1. Throwaway Postgres + Redis with UNIQUE names and free ports.\ndocker run -d --name \u003Cproj>-test-pg -e POSTGRES_USER=\u003Cuser> -e POSTGRES_PASSWORD=\u003Cpw> \\\n  -e POSTGRES_DB=\u003Cdb> -p 127.0.0.1:\u003Cp1>:5432 postgres:16-alpine\ndocker run -d --name \u003Cproj>-test-redis -p 127.0.0.1:\u003Cp2>:6379 redis:7-alpine\n# wait for readiness: for i in $(seq 1 30); do \\\n#   docker exec \u003Cproj>-test-pg pg_isready -U \u003Cuser> >\u002Fdev\u002Fnull 2>&1 && break; sleep 1; done\n\n# 2. Point the app\u002Ftests at them via env. Env overrides .env in pydantic-settings.\nexport DATABASE_URL=\"postgresql:\u002F\u002F\u003Cuser>:\u003Cpw>@127.0.0.1:\u003Cp1>\u002F\u003Cdb>\"\nexport REDIS_URL=\"redis:\u002F\u002F127.0.0.1:\u003Cp2>\u002F0\"\n\n# 3. Alembic reads sqlalchemy.url from alembic.ini, NOT env -> throwaway ini via -c.\n#    env.py's sys.path insert is anchored to env.py location, so -c from \u002Ftmp still imports the project.\n#    [alembic] script_location = \u003Cabs>\u002F...\u002Fmigrations ; sqlalchemy.url = postgresql:\u002F\u002F\u003Cuser>:\u003Cpw>@127.0.0.1:\u003Cp1>\u002F\u003Cdb>\n.venv\u002Fbin\u002Fpython -m alembic -c \u002Ftmp\u002F\u003Cproj>-test-alembic.ini upgrade head\n\n# 4. Run the suite. The test harness spawns its own server subprocess -> inherits the env.\nDATABASE_URL=... REDIS_URL=... .venv\u002Fbin\u002Fpython -m pytest tests\u002F -q\n\n# 5. Teardown AND confirm the sibling project is still up.\ndocker rm -f \u003Cproj>-test-pg \u003Cproj>-test-redis && rm -f \u002Ftmp\u002F\u003Cproj>-test-alembic.ini\ndocker ps --format '{{.Names}}' | grep -E '^(postgres|redis|worker)$'   # sibling set present\n```\n\n## Pitfalls\n- **Endpoint dialect must match the app**: a sync SQLAlchemy `create_engine` wants `postgresql:\u002F\u002F`\n  (psycopg2), NOT `postgresql+asyncpg`. Match the project's database.py \u002F config default.\n- **Route env directly, not through `.\u002Frun`**: the suite's spawned subprocess inherits YOUR\n  exported env; a `.\u002Frun` wrapper may source `.env` and clobber the override.\n- **Check ports free first**: `nc -z 127.0.0.1 \u003Cport>` before `docker run -p`.\n- **Teardown is mandatory** — leftover `-test-` containers clutter the host and can be mistaken\n  for the real stack.\n\n## Related\n- The underlying collision (generic `container_name: postgres`\u002F`redis` across projects) and its\n  permanent fix (unique container names per project) is covered in the `engineering-approach` skill.\n- A sibling source-control hazard — an unanchored `api\u002F` gitignore silently dropping an app dir\n  from git — is in `git-forensics` \u002F `git-pull-local-changes`.\n\n## Verification\n- Full suite green against throwaway infra; count matches baseline after any fixture fixes.\n- Sibling containers reported by the teardown ownership check are unchanged.\n",{"name":5,"version":24,"category":25,"platforms":26,"description":7},"1.0.0","devops",[27,28],"linux","macos","main","2e6aa8d15ab0a366c90be54f61bf9c6e97015e83","skills\u002Fdevops\u002Fdocker-test-isolation-harness",1,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet","steadfaste.com","https:\u002F\u002Fgithub.com\u002Flukemcqueen","AI Architect | Building Hermes Cortex: governed multi-agent AI for autonomous software engineering | Enterprise Tech Consultant","2026-11-14 22:33:34",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add lukemcqueen\u002Fsteadfaste-fleet --skill docker-test-isolation-harness",{"tool":44,"command":45},"bunx","bunx skills add lukemcqueen\u002Fsteadfaste-fleet --skill docker-test-isolation-harness",{"tool":47,"command":48},"pnpm","pnpm dlx skills add lukemcqueen\u002Fsteadfaste-fleet --skill docker-test-isolation-harness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fdocker-test-isolation-harness\u002FSKILL.md",true,[],[53,61,68,75,82,89],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":60},"01M7DXY4G8NSVB59K8B6S2AQNP","macbook-linux-maintenance","Legacy MacBook Linux fixes: GPU wedge, reboot hang, thermal.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fmacbook-linux-maintenance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":60},"01M7DXXYJCXFJ3TGB84ZQ8KFE6","governance-regression-triage","Triage a host's governance issues: what changed.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fgovernance-regression-triage\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":60},"01M7DXXSAP1G8FDRJAMXQGBBMK","enforcement-immutability","Use when enforcement files lose their immutable flag.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fenforcement-immutability\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":60},"01M78SSDQVRYX64Y16X32TC0NS","steadfaste-fleet-repo-deploy","Use when committing to the steadfaste-fleet repo.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-repo-deploy\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":60},"01M78SS928F3R2RJAYVW4E30CE","steadfaste-fleet-maintenance","Maintain an installed Steadfaste Fleet instance — update both the upstream Hermes Agent and the fleet repo layer, merge diverged histories, sync skills safely, and troubleshoot common issues. Covers the dual-update workflow (hermes update + fleet-update.sh), encrypted brain data backup, mycortex import, and recovery techniques.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-maintenance\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":60},"01M78SP1CHW0T0BWE5ZT6JBPX8","fleet-preflight","DEPRECATED alias — merged into survey-before-action (2026-08-20). Load survey-before-action instead; its \"Repo-Specific Pre-Flight\" section covers git search, Hermes boundary, and deployment verification.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Ffleet-preflight\u002FSKILL.md",[],[]]