DeepSeek Harness Plugin

zjukop3/dsh-vertical-kit#dsh-meeting-notes-check

Stars ★ 0 Category Tools & Capabilities Added 2026-11-16 npm dsh-meeting-notes-check

Meeting-note hygiene from markdown: a date, the people in the room, recorded decisions, and every action item carrying an owner and a deadline. Its HTTP routes have no DSH access check, so a web page open in your browser could call them.

Install

# from npm (prebuilt)

dsh plugin --profile web add dsh-meeting-notes-check

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:zjukop3/dsh-vertical-kit#path:/packages/dsh-meeting-notes-check

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

README

This plugin publishes its README in Chinese only.

Meeting-note hygiene from markdown. A note is decidable: it must say when the meeting happened, who was in the room, what was decided, and every action item must carry an owner and a deadline. This verifies exactly those and names the line that is missing whom.

真实输入输出

输入:

# 项目周会

- 日期:2026-11-15
- 与会人:张三、李四、王五

## 议程

1. 讨论登录页改版
2. 评审导出性能

## 行动项

- [ ] 登录页模板替换
- [ ] 导出性能基线测试 负责人:李四

真实运行(逐字输出,由测试与工具保持同步):

$ meeting-notes-check meeting-sample.md
error action-no-owner 第13行 第 13 行行动项没有负责人(认得:负责人:…、@名字、X 负责):「- [ ] 登录页模板替换…」
error action-no-deadline 第13行 第 13 行行动项没有截止时间(认得:11月20日前、2026-11-20、下周三)
error action-no-deadline 第14行 第 14 行行动项没有截止时间(认得:11月20日前、2026-11-20、下周三)
warn decisions-missing 第0行 没有记录任何决定/决议/结论——如果这次会议真的没有决定,忽略这条
fail: 2 action items, 3 errors, 1 warnings

出口码:1。

Listed in awesome-dsh-plugin.

What it decides

rule level meaning
date-missing error no recognizable date anywhere (2026-11-16, 11月16日, 11/16, 下周三)
attendees-missing error no 与会人/参会人/出席/Attendees line or heading
action-no-owner error a checkbox or 待办-numbered item without 负责人:… / @名字 / X 负责
action-no-deadline error an action item without a date or a 周X deadline
agenda-missing warn no 议程/议题 heading or numbered discussion points
decisions-missing warn no 决定/决议/结论 — the message says to ignore it if the meeting truly made none
no-action-items warn no tasks at all — again with an escape hatch in the message

Numbered lines are how a whole note is structured, so plain numbered discussion points are not action items; only checkboxes, and numbered lines under a 行动/待办/Action heading, count.

Use

npx dsh-meeting-notes-check notes.md          # findings + summary, exit 1 on errors
npx dsh-meeting-notes-check notes.md --json   # machine output
npx dsh-meeting-notes-check notes.md --no-require-agenda

Same function over HTTP: POST /meeting-notes-check/api with {"text": "…"} or {"path": "…"}, optional {"rules": {"requireAgenda": false}} — the CLI and the host route share one implementation, so they cannot disagree.

Honest scope

This checks the note's bookkeeping, not the meeting's quality. It cannot tell whether 张三 really accepted the task or whether 下周三 was realistic — it verifies the note says who carries what by when. A meeting with genuinely no decisions passes with a warning, not a fake failure.

Content from the project README on GitHub ↗

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.