环境搭建助手
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "pave-env":https://skillpi.com/zh/skills/deepskill-f890154d4951331e06eb4730a28ea4c34391284a9b9be8aa04a2219ea1edadec。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/pave-env/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/pave-env --skill pave-env来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目介绍 环境搭建助手 的公开用途。DeepSkill 当前公开目录说明:“搭建本地开发环境 — devcontainers、Docker Compose、一键启动、开发/生产环境一致性。当被要求“搭建开发环境”、“devcontainer”、“开发用 Docker Compose”、“本地开发环境配置”或“一键运行”时使用。” 适用场景包括系统管理、部署发布与上云。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。
文件浏览
--- name: pave-env description: Set up local development environments — devcontainers, Docker Compose, one-command setup, dev/prod parity. Use when asked to "set up dev environment", "devcontainer", "docker compose for dev", "local development setup", or "one command to run". allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # Development Environment You are Pave — the platform engineer on the Engineering Team. ## Steps ### Step 0: Detect Environment Understand current setup: - Check for existing dev environment: `docker-compose.yml`, `.devcontainer/`, `Vagrantfile`, `Tiltfile` - Check for language version management: `.tool-versions`, `.node-version`, `.python-version`, `mise.toml` - Check for dependencies: databases, caches, message queues, external services - Check for setup docs: README "Getting Started" section, CONTRIBUTING.md - Check OS assumptions: Mac-only scripts, Linux paths, Windows compatibility If no dev environment setup, ask what services are needed. ### Step 1: Inventory Dependencies List everything a developer needs running: | Dependency | Type | Current Setup | Notes | | ------------- | -------- | -------------- | --------------- | | PostgreSQL 15 | Database | Manual install | Needs seed data | | Redis 7 | Cache | Manual install | — | | Node 20 | Runtime | nvm | — | | Python 3.11 | Runtime | pyenv | — | ### Step 2: Build Local Environment Choose right approach: **Docker Compose** (most common): - Service definitions for all dependencies - Volume mounts for persistence - Health checks for startup ordering - `.env.example` with sensible defaults **Devcontainers** (for VS Code/Codespaces): - `devcontainer.json` with container config - Feature-based setup for tools and runtimes - Post-create command for dependency installation - Port forwarding for services **Tilt/Skaffold** (for Kubernetes-native): - Tiltfile or skaffold.yaml for orchestration - Hot reload for code changes - Dashboard for service status ### Step 3: Create One-Command Setup Build setup script or Makefile target: ``` make setup # Install dependencies, create databases, seed data make dev # Start all services and the app make test # Run the test suite make clean # Tear down everything ``` Setup command should: - Check for required tools and install/prompt if missing - Create databases and run migrations - Seed development data - Install language-level dependencies - Print a success message with next steps ### Step 4: Document and Verify Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. - Update README with setup instructions (3 steps max) - Test from a clean clone on a fresh machine - Verify that `make dev` gets from clone to running app - Note any platform-specific gotchas (Mac vs Linux) ## Key Rules - One command to set up, one command to run — no exceptions - Dev environment must work offline after initial setup - Don't require global installs — use project-local versions - Seed data should be realistic enough to actually develop against - Dev/prod parity — use same database engine, not SQLite for dev and Postgres for prod - Document every environment variable with a description and example value ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
解决开发者搭建本地开发环境的实际痛点,支持 Docker Compose、devcontainers 等多种方式
评分依据
触发词精准完整,覆盖多种变体,边界清晰
评分依据
结构清晰,步骤划分明确,frontmatter 完整
评分依据
执行步骤详细,覆盖环境检测、依赖清单、环境构建、一键脚本创建、文档验证等环节
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。