@melosic/dsh-dev-workflow：把开发规范写进 DSH，在关键节点自动校验与拦截
@melosic/dsh-dev-workflow 是 Melosic 维护的 DeepSeek Harness 插件，将分支、Conventional Commits、文档同步、PR 与发布等约定写成按需加载的 skill，并提供 check_commit_message、check_doc_sync 两项检查，在 commit、gh pr create、git tag/发布前触发。五类 guard 拦截不可恢复命令、破坏性 git、对外可见操作、敏感读取与凭证参数。通过 dsh plugin --profile 安装后，可用 /dev-workflow status 查看状态；Settings 面板可改开关且无需重启。要求 DSH >=0.2.0-rc.2、Node >=20、pnpm 10.x，MIT 许可。
Read MoreDeepSeek Harness Plugin: dsh-commit-ai (Auto-Generate Conventional Commit Messages)
dsh-commit-ai is a DeepSeek Harness Web GUI plugin designed to address the cumbersome task of manually writing Conventional Commits-compliant messages. By integrating a "Generate with AI" button into the commit interface, it automatically reads changes from the staging area and invokes the default LLM in the deployment environment to generate a standards-compliant commit message. Users need to obtain the source code from GitHub and install it themselves. This tool is suitable for developers who want to improve commit efficiency and follow standard conventions, but it is recommended to review the source code and license before installation.
Read Moredsh-git-conventions: Configuring Git commits, pushes, and PR conventions for DeepSeek Harness
dsh-git-conventions is a static plugin for DeepSeek Harness used to automatically perform Git commit, push, and PR convention checks. It supports configurable rules covering the `git commit`, `git push`, and `gh pr create` commands. Core features include: validating the Conventional Commits structure for `-m` inline commit messages and rejecting non-compliant ones; prompting the use of `--force-with-lease` instead of bare `--force` pushes when security options are enabled; and enforcing that `gh pr create` must include a title and description, intercepting if they are missing. Plugin rules are configured and persisted via the settings page and support both Chinese and English. If rules are left unconfigured...
Read More# Standard Conventional Commits Written with the `writing-commit-messages` Skill
### Translated English Abstract: This article introduces the `writing-commit-messages` section in spencerpauly/awesome-cursor-skills: how to use Agent Skill to constrain commit messages to follow Conventional Commits specifications (including type prefixes, scopes, body content, and BREAKING CHANGE sections). It verifies the rules in SKILL.md, good and bad examples, commit granularity requirements, as well as the installation methods for Cursor skills: manually installing to the `.cursor/skills/` directory, and using `npx skills add` to install to both Cursor and Claude Code. This guide is suitable for teams that need standardized collaboration and automated changelog generation.
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 MoreGit Commit Message Specification: Enhancing Team Collaboration Efficiency
In daily development, standardized Git commit messages are crucial for team collaboration and issue tracking, as non-standardized messages can lead to version history chaos. The current mainstream specification is Conventional Commits, with the following structure: mandatory type (e.g., `feat` for new features, `fix` for bug fixes, `docs` for documentation), optional scope (limiting module scope, e.g., `user module`), brief description (core content), optional body (detailed explanation), and optional footer (linking to issues or indicating breaking changes). Tools can help develop this habit: `commitizen` (interactive tool) or `commitlint + husky` (automatic pre-commit checks). The benefits of standardization include improved collaboration efficiency, automated version log generation, clear issue tracking, and early warning of breaking changes, making it worthwhile for teams to adopt.
Read MoreGit Commit Message Guidelines: Why Write a Clear Commit Message?
Have you ever encountered vague Git commit messages like "modified" or "fixed a bug", making it difficult to review the details of changes? Clear commit messages can solve this problem. They serve as a "diary" for code changes, needing to explain "what was done" and "why it was done". There are four key benefits to writing standardized commit messages: quick recall (understand changes even after half a year), team collaboration (members quickly locate feature changes), automated tool support (generate version logs, automatically upgrade version numbers), and rapid bug localization (use `git bisect` to quickly narrow down issues during production problems). Start with simplicity for standardization: at minimum, include a "type + description". Common types include `fix` (bug fixes) and `feat` (new features). For advanced usage, consider the Conventional Commits specification, with the format `<type>[optional scope]: <description>`, which can include a body and footer. Beginners can start with "type + description" and use tools like `cz-cli` for assistance. Spend 10 seconds clarifying the core content before each commit, and consistency will improve code management efficiency.
Read More