Loading...
Loading...
Found 694 Skills
Rebuilds the current implementation from scratch as the simplest design that satisfies what was learned, after the user approves the design. Use when the user explicitly asks to redo the work, start over, scrap the approach, or rewrite it more simply. Never infer from a failing or complex implementation. Not for fitting a new requirement into an existing design; use redesigning-from-first-principles.
Validate and push the current task's changes to main.
Execute an approved implementation plan phase by phase with verification and human gates.
Creates a task branch when asked to open a branch from main or develop; keeps the current branch when already on another branch.
Land the open PRs from parallel worktrees in one batch. Merges their heads onto one branch, resolves conflicts, runs the repository's full gate once on the combined tree and fast-forwards the base branch, so GitHub marks every PR merged. Defers any PR it cannot land with confidence.
[Git] Resolve git merge/cherry-pick/rebase conflicts with backup, analysis, and reporting
Compress the current session into a continuation prompt that can be pasted directly into a new session (print only; do not write to disk). Trigger only when the user explicitly invokes /handoff; never trigger it automatically.
Works through a project while you're away, finding improvements and new ideas, building the strongest few on a local branch and leaving a report for when you're back.
Hand this session to the next one, usually on the user's other machine — alert on work not merged to main, write a handoff document into the Handoffs folder, mark it active in handoff_map.json, then close out with end-session. The lets-go skill resumes it.
Resume this repository's active handoff — find it in handoff_map.json, read it, claim it, bring this checkout to its state, and continue the work. The receiving half of the handoff skill.
Development conventions and patterns for ECC. JavaScript project with conventional commits.
Fecha uma frente de trabalho e a leva para produção com UM ponto de aprovação: verifica sozinha o que vai subir (sintaxe, testes, segredo no diff, base desatualizada), mostra uma vez o que exatamente vai para produção e se o push publica sozinho, e só depois do OK do usuário commita, integra, publica e confere. Use de dentro da pasta da frente quando o usuário disser 'release', 'publicar', 'subir para produção', 'fechar a frente' ou 'integrar'. É a outra ponta da skill sdd-new-session.