Introduction

When prompting an agent in a DSH session to generate git commit messages, a common problem arises: while the content can be generated, it may not necessarily conform to team submission standards. Non-compliant logs can impact code reviews, Release Notes, and version management.

7dgroup-ai/dsh-skill-7d-git-commit is a DSH bundle layer plugin package. It registers the 7d-git-commit skill on ctx.skills and performs client-side validation according to the 7DGroup submission standards before generating the git commit message.

The following sections introduce its positioning, validation rules, installation methods, usage examples, and the GitLab integration boundaries confirmed in the current documentation.

Plugin Positioning

  • Repository owner: 7dgroup-ai
  • NPM package name: @7dgroup/dsh-skill-7d-git-commit
  • Version: 0.1.0-rc.3
  • License: MIT
  • Type: DSH bundle plugin, belonging to the bundle layer, marked as “zero core changes” in documentation
  • Enabling method: Available in the corresponding DSH profile session after installing the bundle; remove the bundle to uninstall

Its main function is to move submission standard checks into the DSH session: checking whether the commit message conforms to 7DGroup standards before actually executing git commit.

Validation Rules

Confirmed validation points in the documentation include:

  • Client-side submission message validation before git commit execution
  • Supports 9 fixed Chinese type labels, such as 【新增】 (New), 【修复】 (Fix), 【优化】 (Optimization), 【文档】 (Docs); refer to the standard file for the complete list of labels
  • Validate title length, punctuation, prohibited characters / prohibited phrases, and wording rules
  • Validate body format: numbered lists, maximum 70 characters per line
  • Provide exemptions for merge commits and urgent [skip-check] deployments
  • Includes references/git-commit-message.md as an on-demand loaded source of standards

High-level rules given in the README are as follows:

  • Title format: 【Type】Short Description
  • Title length: not exceeding 50 characters after the label
  • Do not use 。, ，, ., or , at the end of the title
  • Prohibited characters in title and body: @ # $ % ^ & * ~
  • Prohibited phrases: temporary notes, TODO, FIXME, emotional wording
  • Body lines maximum 70 characters, and use only numbered lists

The project structure in README writes the standard file path as:

assets/7d-git-commit/references/git-commit-message.md

Installation and Enablement

Environment Requirements

dsh CLI
Node ^22.19.0 || >=24.0.0
pnpm 10+

peerDependencies are:

@deepseek-ai/cordis ^4.0.1
@deepseek-ai/dsh-invariants ^0.1.0-rc.5
@deepseek-ai/dsh-skill ^0.1.0-rc.5

The dsh.bundle.patch in the package points to:

./cordis.patch.yml

Install using GitHub

The installation command given in the documentation is:

dsh plugin --profile web add github:7dgroup-ai/dsh-skill-7d-git-commit

This example uses the web profile.

When installing via git for the first time, pnpm will refuse to run the build script until you add the exact package key to allowBuilds in the pnpm-workspace.yaml of the corresponding profile. After adding it, rerun the same installation command.

Install using NPM package

The documentation also provides an NPM package installation command:

dsh plugin --profile web add @7dgroup/dsh-skill-7d-git-commit

The documentation states that to avoid build authorization issues, you can use a pre-built tarball or a published npm package. The current documentation does not specify which of the GitHub installation or npm installation is the sole default method.

Install in DSH session

The documentation suggests directly asking the agent to install in a DSH session:

Install the plugin github:7dgroup-ai/dsh-skill-7d-git-commit

The documentation explains that when installing via git, the agent may encounter the same pnpm allowBuilds check and print the key that needs to be added. After adding the key to the pnpm configuration file of the corresponding profile as prompted, ask the agent to retry.

The session example path given in the documentation is:

~/.dsh/profiles/<name>/pnpm-workspace.yaml

Typical Usage

After installation, simply raise commit-related requests in the DSH session. The examples given in the documentation include:

  • Generate a commit message for the current changes.
  • Write a commit message for these changes.
  • Check whether my commit message follows the 7DGroup convention.
  • Fix the commit message so it passes the validation rules.

You can also explicitly trigger the skill:

/7d-git-commit

The skill steps described in the documentation are as follows:

  1. Analyze the current changes.
  2. Select the most matching type label from the allowed 9 categories.
  3. Generate the subject line in the format 【Type】Action + Object, not exceeding 50 characters after the label, and ending without punctuation.
  4. Add a numbered body for complex changes, with a maximum of 70 characters per line.
  5. Run the validation checklist, rejecting or fixing non-compliant items.

GitLab Integration

The documentation states that this plugin provides both a client-side DSH skill and a server-side GitLab hook, used for “client-side pre-check + server-side enforcement”.

  • Client: assets/7d-git-commit/SKILL.md validates the commit message before git commit
  • Server: docs/gitlab-integration/pre-receive validates before the push reaches GitLab
  • Shared rule source: assets/7d-git-commit/references/git-commit-message.md
  • Compatibility note: Server-side integration is adapted and verified against GitLab CE 19.2.0 server-side hooks

The pre-receive flow given in the documentation is: reading pushed refs from stdin in the format oldrev newrev refname, then using git log to extract author, date, and subject, and checking the subject prefix via regex.

It should be noted that the pre-receive regex example in the documentation is truncated, and the complete server-side hook rules are not confirmed. When using GitLab-side rules, please refer to the actual files and configuration in the repository.

Applicable Scenarios and Notes

Suitable for the following usage modes:

  • Want to perform fixed standard checks before generating a commit message in a DSH session
  • Want the client pre-check and server-side GitLab hook to use the same source of standards
  • Want to install via a bundle to avoid core changes

Notes:

  • DSH plugins run related actions under the permissions of the current DSH process. You should check the source code, license, and dependencies before installing.
  • This plugin’s license is MIT.
  • Runtime requirements include dsh CLI, Node ^22.19.0 || >=24.0.0, pnpm 10+, and the peerDependencies mentioned above.
  • Installing via git triggers the pnpm build script authorization check; if the environment does not allow running build scripts, you can switch to the npm package installation method provided in the documentation.
  • The documentation does not provide fields such as category, star count, directory page URL, etc.; this article does not state these unconfirmed pieces of information as definite facts.

Conclusion

The value of 7dgroup-ai/dsh-skill-7d-git-commit lies in making the 7DGroup commit standards a pre-check in the DSH session, and using it in conjunction with the GitLab server-side hook when necessary.

The currently verified documentation does not provide a directory page URL; the GitHub repository is:

https://github.com/7dgroup-ai/dsh-skill-7d-git-commit