merge-docs-870dd7 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited merge-docs-870dd7 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<!-- codex: tool-name mapping applied. See .codex/scripts/session-start.sh -->
Goal: Produce a single, unified set of feature docs from two separate designs for the same feature.
You have two feature directories under /docs/wip/ for the same feature — each with its own design, implementation plan, and task list — and you need to combine them into one coherent set of docs.
Mandatory order — grounding before merging. The flow below is strictly sequential. Do not categorize sections, surface contradictions, or write merged content until you have read both feature directories fully and built a codebase-grounded mental model. Merging without grounding produces decisions based on prose clarity rather than codebase reality — the wrong tiebreaker.
See merge-process.md for the detailed steps.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.