# Construction Safety Rectification

> Generate, review, normalize, and track Chinese construction safety inspection records, hazard findings, safety rectification notices,整改通知单,隐患整改闭环 records,安全检查记录,安全周报,安全专项检查报告, incident/near-miss reports, and PPE/computer-vision finding summaries. Use when the user provides site safety notes, photos, AI vision outputs, voice-input text, checklists, previous rectification records, or asks to identify construction safety hazards, classify risk level, draft整改要求, assign responsibility, set整改期限, or produce closure/reinspection wording.

- Skill: `whb786200/construction-safety-rectification` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add whb786200/construction-safety-rectification`
- Raw SKILL.md: https://api.skillmd.com/api/skills/whb786200/construction-safety-rectification/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: whb786200 (https://skillmd.com/u/whb786200)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/whb786200/construction-safety-rectification

---


# Construction Safety Rectification

## Core Workflow

1. Identify the target document: 安全检查记录, 安全隐患整改通知单, 整改回复, 复查记录, 安全周报, 事故/未遂事件记录, or checklist.
2. Read all provided materials first: field notes, image observations, OCR text, voice-input text, previous整改记录, or templates.
3. Extract hazards into structured fields: location, hazard category, description, risk level, evidence, responsible unit, corrective action, deadline, verifier, status.
4. Draft in formal Chinese construction-safety language. Distinguish observed facts from inferred risks.
5. Do not invent laws, clause numbers, test results, responsible parties, photos, or closure results. Mark missing fields as `待补充`.
6. Every hazard must have a corrective action, deadline, and closure state.
7. If photos or AI vision outputs are used, state `疑似` or `根据图片可见` unless the user confirms现场核查.

## Reference Use

Use `references/safety-schema.md` for field definitions, hazard categories, risk-level rules, and common整改措辞.

Use `references/open-source-notes.md` to understand the local cloned project references:

- SecureEye: multimodal hazard detection + rectification report idea.
- safety-hazard-management: issue reporting, assignment,整改,验收, closure workflow.
- DDC safety-inspection: checklist, hazard, incident, statistics data model.
- YOLO PPE projects: helmet/vest/person detection as objective evidence, not full safety judgment.

## Quick Rectification Notice

Run the deterministic generator from text or a voice-input paragraph:

```powershell
python D:\Codex\Home\skills\construction-safety-rectification\scripts\generate_rectification_notice.py --project "项目名称" --date 2026-06-20 --inspector "监理人员" --contractor "施工单位" --notes "1号楼三层临边防护缺失，电梯井口防护门松动，部分作业人员未佩戴安全帽"
```

Use `--notes-file` for longer site inspection notes and `--output` to save Markdown.

## Drafting Rules

- Use direct, enforceable wording: `立即停止相关作业并整改`, `限期整改`, `整改完成后报监理复查`.
- Separate risk from action: describe the observed hazard first, then risk consequence, then整改要求.
- Avoid vague phrases such as `加强管理` unless paired with a concrete action.
- For重大/紧急风险, require immediate protective measures before continued work.
- For PPE findings from AI detection, write `图片识别疑似未佩戴安全帽/反光背心，需现场核实`.
- For closure, use one of: `待整改`, `整改中`, `已整改待复查`, `复查合格`, `复查不合格继续整改`.

## Output Checklist

- Each hazard has location, category, risk level,整改要求, deadline, responsible unit, and status.
- The notice does not claim closure unless there is reinspection evidence.
- Deadlines are realistic and concrete, such as `立即`, `当天`, `3日内`, or a date.
- PPE/image findings are clearly marked as AI-assisted or photo-based where applicable.
- The final document can be pasted into a project safety management system or Word template.

