code-dev-pipeline 代码开发流水线

This skill is largely coherent with its stated purpose (a multi-role code development pipeline), but pay attention to these points before you install or enable it: 1) The documentation expects Git usage, running servers/tests (uvicorn/node/browser tests), and invoking another skill (ui-ux-pro-max) — yet the skill metadata claims no required binaries or environment; ask the author to list required tools (git, Python/Node, browsers/test runners) so you can control them. 2) The workflow writes files under projects/{name}/, creates symlinks, and persists iteration artifacts; run it in an isolated workspace or container if you don’t want these files mixed with your system. 3) The skill will invoke subprocess-like behavior (spawn role workers) and may create commits — review what the agent will commit to any Git repo before giving it access to important repositories. 4) There are no requested secrets, which is good, but be cautious about logs or example code that reference user emails or other identifiers — avoid feeding sensitive production credentials into the pipeline. 5) If you need higher assurance, ask the publisher to: (a) declare required binaries and runtimes, (b) document exactly how 'spawn' is implemented (local processes, separate agents, remote calls), and (c) provide explicit opt-outs for filesystem persistence or a configurable project root.