Menu
Audit and update all project documentation to stay in sync with the current development status.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Perform a dedicated, project-wide security audit of Baudrate — injection, XSS, SSRF, authentication/authorization, federation trust boundaries, key material, file handling, rate limiting, and dependencies — mapped to the OWASP Top 10, then report findings by severity and fix critical issues.
Check for available updates and security advisories across every dependency ecosystem Baudrate uses — Elixir/Hex packages, the esbuild/Tailwind/daisyUI frontend toolchain, and the Rust NIF crates — then report what is outdated, what is blocked by a version constraint, and what is retired/insecure, grouped by risk. Reports findings; does not upgrade without confirmation.
Perform a project-wide full-scope code review covering correctness, security auditing, test coverage, locale sync, documentation quality, code smells, UI/UX accessibility, and project conventions, then report findings and fix critical issues.
Stage, commit, and push changes to the remote repository with a well-formed commit message.
Audit and update all project documentation to stay in sync with the current development status.
Manage the full software release process, including version bumps, changelogs, Git tags, and GitHub releases.
| name | docs-engineering |
| description | Audit and update all project documentation to stay in sync with the current development status. |
When performing documentation engineering, always follow these steps:
Audit all documentation against the current codebase and development status. The review scope must include — without exception:
README.md — features list, prerequisites, acknowledgementsCLAUDE.md — stack, architecture, key gotchas, project conventionsdoc/ — development.md, sysop.md, api.md, troubleshooting.md, TODOs.md@moduledoc and @doc strings in changed or related modulesRevise and update any documentation that is stale, incomplete, or inconsistent with the current code. Ensure new features, removed dependencies, behavioral changes, and architectural decisions are reflected accurately.
Remove completed items from doc/TODOs.md. If a summary of completed work is warranted, add a brief note before removing the items.
Commit documentation changes in Git, grouped by topic. Do not mix unrelated documentation changes in a single commit.