dev-workflow

Use when about to rebase, resolve rebase conflicts, or run any git operation that can silently drop commits — `git rebase`, `git rebase --continue`, `git rebase --skip`, `git pull --rebase`, `git reset --hard`, `git push --force`, cherry-pick chains, squashing, or "the branch has conflicts with main". Also use when a rebase already went wrong and commits or features appear to have vanished. Invoke this BEFORE running the rebase, not after the history is already rewritten.

Use whenever work starts, changes state, or finishes on anything bigger than a one-line fix — a new feature, a bug report, an idea raised but not finished in the same breath, work actually beginning, a blocker hit, a branch or PR opened, a scope change, work that just got verified, or a request being dropped or rejected. Also use when the user says "abre un issue", "trackea esto", "anota esto para después", "ya está listo, ciérralo", "esto ya no lo vamos a hacer", or asks what is pending. Apply this proactively at the START of non-trivial work, not only when the user mentions issues.

Use whenever code needs an independent review — reviewing the working diff before a commit, reviewing a branch or PR before merge, the `requesting-code-review` step of any workflow, "revisa esto", "haz code review", "¿está bien este cambio?", or a security/correctness pass over work that was just written. Use it BEFORE claiming a change is ready to merge. Applies to work the assistant wrote itself, which is exactly when an independent reviewer matters most.