AGENT SKILL

workflow-docs-repair

Realign docs and code comments with the implementation in an existing project and bring them to the tech-docs standard. Evidence decides doc-side fixes; context-rich DRIFT decision cards go to a person when it does not; code-side fixes become findings for implement. Resumable ledger in docs-repair/. Use on /docs-repair or when docs and code have drifted apart.

License 许可
MIT
最近更新
2026-11-11
Stars
★ 3
Forks
0

01 前言 Front Matter

name
workflow-docs-repair
description
Realign docs and code comments with the implementation in an existing project and bring them to the tech-docs standard. Evidence decides doc-side fixes; context-rich DRIFT decision cards go to a person when it does not; code-side fixes become findings for implement. Resumable ledger in docs-repair/. Use on /docs-repair or when docs and code have drifted apart.
argument-hint
Name the scope (whole repo, components, or doc set), or "resume"

03 SKILL.md 正文

Execute /docs-repair workflow.

  • Read .github/copilot-instructions.md unless it is already in context.
  • Read .github/skills/workflow-docs-repair.md.
  • Apply rules exactly; do not restate them here.

04 同仓库更多 Skills

DevAM-Tools
DevAM-Tools/NetworkInspector

workflow-review

Skeptical auditor review. Answer ready-for-public-release for the scope. Summary is a findings table plus a hunt-results table. Ignore prior reviews unless named. Load skills from the Section 3 table. Locked finding How. Default runs tests; static on explicit reduced scope. Use on /review.

★ 3
DevAM-Tools
DevAM-Tools/NetworkInspector

workflow-review-loop

Review and remediate in a loop until findings are resolved. Use on /review-loop or when user wants review+fix cycles without a plan.

★ 3
DevAM-Tools
DevAM-Tools/NetworkInspector

workflow-requirements

Record an atomic, contradiction-free requirement list as REQ-<AREA>-<TOPIC> (shall / shall not / shall exhibit). The ID names the subject. Context prose gets no ID. Implementation-far. Use on /requirements, or before /plan when none exist. Use existing artifacts when the user already supplied them.

★ 3
DevAM-Tools
DevAM-Tools/NetworkInspector

workflow-port-dotnet-rust

Port a .NET/C# solution to Rust as a complete, content-equivalent port. Phase 0 intake and machine inventory, Phase 1 human alignment into port/MANIFEST.md, Phase 2 autonomous loop, Phase 3 closing audit. Full books: every public member, behavior item, and .NET test booked with a closed status set. Use on /port-dotnet-rust, when porting .NET or C# to Rust, or when port/** is in scope.

★ 3
DevAM-Tools
DevAM-Tools/NetworkInspector

workflow-port-dotnet-rust-loop

Autonomous .NET → Rust port loop. Requires an approved port/MANIFEST.md. Ports one unit per iteration completely (tests first, implement, verify, equivalence hunt), keeps the books in port/ balanced, books questions as blockers instead of asking, and resumes from port/STATUS.md. Use on /port-dotnet-rust-loop or to continue a port.

★ 3
DevAM-Tools
DevAM-Tools/NetworkInspector

workflow-plan

Create an implementation plan with locked How, Before/After, schematic API and interface snippets before the steps, first-class TEST-<AREA>-<TOPIC> content, linked requirements (no copied requirement list), and step acceptance. Run requirements first when none exist. Close with a requirements walk and a conversation walk. Use on /plan or before implementation without an approved plan.

★ 3