skills.rest
danielbaustin
danielbaustinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sor-editor

Repair SOR output cards in sor.md to reflect verified execution and evidence.

4|1|Updated Feb 3, 2026
Search Tags:#markdown#review#truthfulness#sor#sor-editor#output-card
One-click install
npx skills add https://github.com/danielbaustin/agent-design-language --skill sor-editor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sor-editor
Source: https://github.com/danielbaustin/agent-design-language/tree/main/adl/tools/skills/sor-editor
Command: npx skills add https://github.com/danielbaustin/agent-design-language --skill sor-editor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Normalize and correct an SOR output card so it records truthful execution and integration state without inventing validation or overstating completion. Use when an output card has placeholders, wrong integration wording, stale validation claims, or finish-blocking truth-model errors.

Core Features & Use Cases

  • Bounded editing of sor.md to reflect actual execution and PR state.
  • Aligns integration wording, validation claims, and evidence with observed results.
  • Prevents placeholders and stale prose from leaking into committed records.

Quick Start

Edit the sor.md card to reflect verified execution and evidence, stopping before PR publication.

Frequently Asked Questions about sor-editor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix placeholders and stale validation claims in an SOR output card?▼

To fix an SOR output card, apply bounded edits to sor.md that normalize integration wording and align validation claims with verified execution evidence, preventing stale prose from leaking into committed records.

What is the best way to normalize markdown truthfulness before a PR publication?▼

The best way to normalize markdown truthfulness is to enforce bounded edits on the SOR card, allowing only normalization and truth-based changes that reflect actual execution state, stopping immediately before PR publication.

Why does my SOR output card contain incorrect integration wording across worktrees?▼

Incorrect integration wording in an SOR card occurs when placeholders or stale validation claims are not updated to reflect actual execution and PR state across worktrees or release notes, requiring bounded normalization.

Can I use this approach to repair SOR cards across multiple release notes?▼

Yes, you can repair SOR cards across release notes by applying bounded edits to sor.md, ensuring that integration wording and evidence align with observed results without overstating completion.

When should I not use bounded edits for SOR card normalization?▼

You should not use bounded edits for SOR card normalization if the goal is to invent validation, overstate completion, or publish the PR, as the process stops before PR publication and enforces truth-based changes only.

Related Skills

Explore More Software Engineering Skills→
danielbaustindanielbaustin
4

pr-closeout

Automate issue and PR closeout by verifying closure outcomes and reconciling artifacts.

Community
Advanced
Mark393295827Mark393295827
133

loop-engineering

Design bounded agent loops with explicit triggers, budgets, and stop conditions.

Community
Advanced
aurora-atomsaurora-atoms

pr-to-release-summary

Generate structured release summaries from merged pull requests and validation evidence.

Community
Advanced
gaofeng21cngaofeng21cn
8

opl-charter-authority-reviewer

Classify statement authority types and flag forbidden claims in OPL foundation materials.

Community
Intermediate