メニュー
Audit and fix documentation (README, ARCHITECTURE, CHANGELOG) against current codebase while waiting for CI/bot reviews on a PR. Fix factual drift, dead references, and add changelog entries — then commit docs to the same branch.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Systematic pre-merge verification workflow for Rust monorepo branches. Check compilation, tests, clippy, grep leftovers, then fix → commit → push → PR. Use when user says "check work done in this branch" or before merging any PR.
Dependency lock and Cargo.lock conflict policy for Rust workspaces. Covers when to update, when to regenerate, manual conflict handling, and merge/sync guidelines to prevent recurring Cargo.lock merge conflicts.
Daytona sandbox knowledge for answering user questions about remote development environments. Use when the user asks about Daytona, sandboxes, remote execution, cross-platform builds, or needs to run code on cloud infrastructure instead of locally. Provides API details, pricing, troubleshooting, and CLI commands.
Modal.com knowledge for answering user questions about serverless GPU compute, cost comparison with Daytona, and Python-based sandbox workflows. Use when the user asks about GPU access, ML training, Modal pricing, serverless sandboxes, or wants to compare cloud compute options for their Rust/Python projects.
Mandatory project quality workflow for the specgen Rust monorepo. Enforces zero-warning policy, formatting standards, and test compliance. Trigger before any commit, pull request, or completion of a coding task. Also trigger when the user says "check quality", "run QA", or "is it ready?".
Comprehensive toolkit for detecting and eliminating "AI slop" - generic, low-quality AI-generated patterns in natural language, code, and design. Use when reviewing or improving content quality, preventing generic AI patterns, cleaning up existing content, or enforcing quality standards in writing, code, or design work. Trigger on first run in any new codebase, after AI-assisted coding sessions, or when user says "clean up", "review quality", "check slop", or "anti-slop".
| name | doc-audit-ci-wait |
| description | Audit and fix documentation (README, ARCHITECTURE, CHANGELOG) against current codebase while waiting for CI/bot reviews on a PR. Fix factual drift, dead references, and add changelog entries — then commit docs to the same branch. |
| source | auto-skill |
| extracted_at | 2026-07-25T11:37:12.012Z |
When a PR is pushed and CI/bot reviews are pending, use the wait time proactively: audit documentation for drift against the current codebase, fix what's wrong, and push docs to the same branch so they become part of the PR.
After pushing a PR, when the user says "wait for bot" / "รอ bot comment" or CI checks are still running.
Check these against the actual project state:
| Check | Command / Method |
|---|---|
| File counts in structure tree | ls -la core/src/*.rs | wc -l, count actual .rs files per crate |
| Directories that no longer exist | ls each path mentioned in the structure — remove dead entries |
| Files that exist but aren't listed | ls root and each subdirectory — add missing entries (e.g., config.toml) |
| Date at bottom | Compare against today's date |
| Build/test counts | cargo test --workspace 2>&1 | grep "test result" — verify counts match |
| Deprecation/spec mentions | Does README reference removed deps, old APIs, or renamed commands? |
Fix: update dates, file counts, structure, and remove dead references.
| Check | What to look for |
|---|---|
| Dead directories | References to server/, model/engine/, model/, logs/, tests/ — these were deleted in Phase 1 |
| Missing crates | sandbox/, api/ — are they listed? If not, add |
| Outdated migration plans | Phase 1-3 concepts that are already done should be removed or archived |
| File names | craft.db → data/craft.db, backend/core/ → core/ |
| Key decisions | Are removed deps mentioned? (e.g., pyo3 removed, distiller stubbed) |
Fix: rewrite the architecture section to reflect current workspace layout only.
| Check | Action |
|---|---|
| Unreleased section exists | If no [Unreleased] section, add one |
| Current PR's changes recorded | Add entries under ### Fixed or ### Changed for what this branch does |
| Old repo URLs | Compare compare links against git remote get-url origin — fix if project was renamed |
| Date format consistency | Ensure all dates use same format (ISO 8601 recommended) |
Look at TODO.md for any unchecked doc tasks (e.g., README.md updated) — these are
explicitly waiting for the doc pass you're doing now.
git add README.md docs/ARCHITECTURE.md docs/CHANGELOG.md
git commit -m "[DOC] update <summary> for current state"
git push
The commit will appear on the same PR, so the CI re-runs with the docs fix included.