Stable
Git cherry-pick: Moving a Single Commit to the Right Branch
Why is git cherry-pick used, what problem does it solve, and how is it used in practice, including conflict handling?
Notes
Shorter technical entries — checklists, comparisons and things worth not re-deriving. Some are finished, some are still moving.
Stable (5)
Stable
[SKILL] - backend-change-doc
A skill that turns backend API and model changes into a short, developer-friendly change document for frontend or mobile teams.
Stable
[SKILL] - explain-reasoning
Runs AFTER a task/fix has been done. Retrospectively unpacks the engineering thought process behind the change - which clue, which chain of reasoning, which principle, how it would have been found without AI, how the user can catch it on their own next time. Use when the user says 'why did you do it this way', 'explain your chain of reasoning', 'how would I have found this', 'mentor me', 'reasoning', or when /explain-reasoning is invoked.
Stable
[SKILL] - requirements-to-plan
Reviews an existing REQUIREMENTS.md file and the project structure to produce a phased, actionable PLAN.md written in Turkish.
Stable
[SKILL] - universal-code-review
Reviews the given code at a senior level; prioritizes critical issues, explains the reasoning, and offers concrete fix suggestions.