PerryLink/dsh-sop-sync-check ↗★ 0
dsh-sop-sync-check
作业规程与 FMEA/控制计划一致性核对(按编号与版本核对三份文件是否同步,仅提示差异,不作出定性结论) 适合质量工程师,用于核对三份文件的编号与版本是否同步。
Install
$
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:PerryLink/dsh-sop-sync-checkREADME
Read the full README ↗Configuration
| Key | Type | Default | Description |
|---|---|---|---|
rulesFile | string | rules/sop-sync-check.yaml | Rule-pack path, relative to the package root |
disabledRules | string[] | [] | Rule ids to stop running; each appears in skipped |
onlyRules | string[] | [] | Run only these rule ids; empty runs every rule |
skipNotes | string | "" | Note appended to every skipped reason |
timeoutMs | number | 120000 | Cooperative tool timeout budget |
Rule-level parameters worth knowing:
SS-003referenceField/actualVersionField/sameVersionField— where the cited revision and the document's current revision live.actualVersionFieldtakes a list; the first non-empty candidate wins, and a bare version (V2) or a reference carrying one (PFMEA-2026-003 V2) both work. If your register keeps the cited revision in its own column, name it insameVersionField.SS-004conditionField/requiredFields— which column triggers the requirement, and what it needs.