Menu
Commit changes after running CI checks
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
duklog coding standards, testing requirements, and review checklist. Use when reviewing code, writing tests, or checking quality.
Create a pull request after code review
Process PR feedback, user corrections, code review findings, or self-observed patterns and update project memory, rules, and standards accordingly. Use proactively after receiving PR review comments, user corrections, or when patterns emerge from code review or self-reflection.
Post-implementation retrospective. Run after completing any non-trivial task to extract patterns, surprises, and lessons and persist them to rules and memory without waiting for user feedback. Use proactively after creating a PR or finishing a significant feature.
Search Rust crate documentation for a type, trait, function, or method. Usage: /search-rust-doc {crate} {query}
| name | commit |
| description | Commit changes after running CI checks |
make ci — all checks must pass before proceedinggit status to see all changesgit diff to review staged and unstaged changessimplify skill on the changed files — fix any issues found before staginggit log --oneline -5 to see recent commit message style.env, credentials, or secrets)Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
git status to verify successIf make ci fails, fix the issues first. Do not skip checks.