Vibe Coding Rules · AI 编程纪律：给 Agent 套上改码流水线
Vibe Coding Rules（@org-121tp3g2/vibe-coding-rules）是 SkillHub 上的 AI 编程纪律 Skill 组合，由云南躺不平网络科技有限公司发布。官方将其描述为 V2.5 外骨骼：六段自动流水线覆盖改前五大原则、终端安全执行、改后 28 条规则扫描、Playwright 回归与变更归档；文件头面包屑标记耦合文件与文档，重复 Bug 三次可升级为硬规则。支持 Cursor、Windsurf、CodeBuddy，Apache 2.0。安装需 skillhub CLI 并用 --dir 指向 Agent skills 目录，或按 skillhub.md 让 Agent 安装。
Read Morecoderules-skill：按技术栈自动套用代码规范的 Agent Skill
coderules-skill 是 SkillHub 社区技能（@user_3b34947d/coderules-skill，v1.0.0），定位为智能代码规范助手：识别 TypeScript/Python/Go/Rust/Java 及 React、Vue、Next.js 等框架，加载对应规范后用于生成代码、审查、修复与初始化配置。无需 API Key。本文基于官方页面与元数据说明安装方式（skillhub CLI 与 Cursor/Claude Code/Codex 的 skills 目录）、触发词与典型对话用法，并提示社区来源与统计数据的查阅方式。
Read More全栈开发伴侣：按项目类型自动切换开发流程的 Skill
全栈开发伴侣（@user_8a92847d/fullstack-companion）是 SkillHub 社区 dev-programming 类 Skill，v1.0.0，无需 API Key。它自动检测工作区偏前端、后端或全栈，路由到对应开发模式，并内置后端开发、前端开发与代码规范三套子流程。文章说明定位、能力边界，以及通过 skillhub CLI 安装到 Cursor、Claude Code、Codex 等 skills 目录的步骤与典型使用方式，并给出官方页面与安装文档链接。
Read MoreIntroduction to the DeepSeek Harness Strict Gate Plugin
The DeepSeek Harness plugin Strict Gate enforces policies that convert an agent’s “self-management” into a Harness-level oversight mechanism, ensuring that code changes on critical paths comply with established standards. It includes three core capabilities: repeated-failure intervention, critical-path protection gating, and automatic post-generation syntax checks. The plugin runs on Node.js, requires the `dsh-tool-strict-check` dependency, and is enabled through configuration. It is designed to consolidate code-generation risk under unified management by intercepting repeated errors, protecting core code, and performing immediate syntax checks, making it suitable for project processes that require strict governance.
Read Moredsh-thincoder-suite: Four Self-Discipline Plugins for DeepSeek Harness
`shenhuanageshei/dsh-thincoder-suite` is a DSH plugin ported from thincoder, designed around "everything is a plugin" to enforce four self-discipline rules for AI during development and turn trust-dependent workflows into auditable ones. It includes four core tools—advisor, eng/eng_coder, escalate, and consult_start—which address review loops, code direction, capability overflow, and blockers, respectively. Its core mechanisms include mandatory output reconciliation tables and citation verification to achieve review convergence; a "design review token" mechanism to control code-writing permissions; support for parallel multi-model consultation; and background task handling for long-running jobs. Installation requires DSH 0.2.0-rc.1 and job.
Read Moredsh-sql-format: SQL Formatting
`dsh-sql-format` is a DeepSeek Harness client plugin that formats messy SQL strings into standard, well-structured text with capitalized keywords. It only handles presentation-level formatting and does not make database connections or perform semantic analysis. Users can enable the plugin by running an install command and configuring `package.json`; after installation, they can call the `format_sql` function in a session to format SQL. Note that this plugin is implemented in Node; installation runs local code, so be sure to review its source code and license.
Read Moredsh-repo-health: Check Project Best Practices and Generate a Health Check Report
`dsh-repo-health` is a DeepSeek Harness plugin for automatically checking whether a repository complies with best practices. The plugin is implemented entirely in Node.js and requires no network access. It uses the `health_check` tool to check key files such as README, LICENSE, tests, and CI, and returns the results along with remediation suggestions. Users need to install the plugin in DSH and enable it in `package.json`. When using it, note that the plugin runs with the permissions of the current process, so review its source code and ensure the required dependencies are installed.
Read MoreGit Commit Message Template: Standardizing Team Collaboration Submission Norms
### Why Unified Commit Specification is Needed? A unified commit specification addresses issues like difficult code reviews, chaotic version iterations, and failed automation tools. It ensures clarity on the purpose and content of each change, facilitating team collaboration. ### Specification Format (Conventional Commits) - **Type** (Required): E.g., `feat` (new feature), `fix` (bug fix), `docs` (documentation). Incorrect types mislead version management. - **Description** (Required): Concise (≤50 characters), verb-starting (e.g., "optimize", "fix"), avoiding ambiguity. - **Body** (Optional): After a blank line, detail the reason for the change, implementation details, or problem-solving process. - **Footer** (Optional): Link to issues (e.g., `Closes #123`) or note breaking changes. ### How to Create a Commit Template? - **Global Template**: Create `.gitmessage` in the user’s root directory and configure Git with `git config --global commit.template ~/.gitmessage`. - **Project-level Template**: Create `.gitmessage` in the project root and run `git config commit.template .gitmessage`. ### Tool Assistance for Enforcing the Specification - **Commit
Read More