Menü
Stage, commit, and push changes to the remote repository with a well-formed commit message.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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 | commit-and-push |
| description | Stage, commit, and push changes to the remote repository with a well-formed commit message. |
When committing and pushing changes, always follow these steps:
Stage all relevant changes with git add. Be deliberate — stage only files related to the current topic. Never blindly stage everything with git add -A if unrelated changes are present.
Commit with a clear, concise message following the Conventional Commits standard (e.g., feat(bots): add favicon retry logic). The message should explain why the change was made, not just what changed.
Push the committed changes to the current branch on the remote repository.
Verify that the push succeeded and the remote is in sync with the local branch.
