这是一项有纪律氛围编码的技能。Claude 不会在没有你的情况下承诺 说说，不走门就不发货，也不能悄悄跳过。

** ⬇ 下载 dev-skills.skill** — 当前版本 v2026.10.23

GitHub仓库 ·v2026.10.23 发布说明

---

目录

• 它的作用——四条规则
• 执法检查——实际检查内容、全面披露及拒绝方式
• 最新消息 — 最近几次发行
• 看起来——一场会议，简略版
• 安装 — claude.ai、桌面、CLI、网页
• 六个门——每个门检查什么
• 两首曲目——为什么工作承诺不等同于发行
• 手动和半自主模式——由谁来执行命令
• 门的执行方式——状态文件，以及为什么内存不值得信任
• 执行环境——本地、容器与Termux
• 工作流检测——本地开发与配置
• 成本纪律——什么是自动的，什么是你必须提出的要求
• 项目标准 — 安全架构部分、静止加密、登录保护、主页链接、Apprise、快速编写
• 安全架构——该仓库如何构建安全性及其变化
• 审计模式 ·捷径检测 ·内部内容 ·维护者用

claude-vibe-skills

One skill for disciplined vibe coding. Claude doesn’t commit without your say-so, doesn’t ship without walking the gates, and can’t quietly skip either.

🔢 VERSION  →  🔨 BUILD  →  🔒 SECURITY  →  📄 DOCS  →  📦 RELEASE  →  🚀 SHIP

⬇ Download dev-skills.skill — current version v2026.10.23

GitHub repo · Release notes for v2026.10.23

---

Contents

• What it does — the four rules
• Enforcement checks — what’s actually checked, full disclosure, and how to decline
• What’s new — the last few releases
• What it looks like — a session, abridged
• Install — claude.ai, Desktop, CLI, web
• The six gates — what each one checks
• Two tracks — why a work commit isn’t a release
• Manual and semi-autonomous mode — who runs the commands
• How gates are enforced — the state file, and why memory isn’t trusted
• Execution environments — local vs. container vs. Termux
• Workflow detection — local dev vs. CI
• Cost discipline — what’s automatic, what you have to ask for
• Project standards — security architecture section, encryption at rest, login protections, main-page links, Apprise, compose quickstart
• Security architecture — how this repo is built with regard to security, and what has changed
• Audit mode · Shortcut detection · What’s inside · For maintainers

---

What it does

1. Commits require approval. Claude never runs git commit, git push, or gh pr create without your explicit say-so. No surprise commits after a single edit. A vague “ok” doesn’t count, and neither does a hook telling Claude the tree is dirty. This is the one rule semi-autonomous mode doesn’t relax.

2. All work happens on branches. Never directly on main/master. At session start the skill finds the repo, offers to sync when you’re behind origin, and flags you if you’re sitting on the default branch.

3. Gates run before anything ships. A work commit needs the security gate and your approval. Anything that bumps a version, builds an artifact, tags, or publishes runs all six, in order. Presenting a git command for you to paste counts as running it — the same pre-flight fires either way.

4. Security and quality get scanned. After every build, a full scan checks for hardcoded secrets, injection vectors, spaghetti code, N+1 queries, and more. Critical and High findings block the release.

---