ilyasturki

After a code change, test it end-to-end (bash, browser, or computer use — whichever fits) and then run `/simplify` to review and clean up the changed code. Use to confirm a change works and is tidy before wrapping up.

Create a git commit and push it

Create a git commit

Ask the user for maximum clarifications before acting on a prompt. Use when the user wants to ensure all ambiguity is resolved before work begins.

Write or refresh a README that earns the reader's attention — short, honest, with a real visual. Tailored to the project type.

Greenfield product spec for an empty repo. Clarifies scope, then challenges the idea — checking whether it already exists and whether the pain is real — before writing a concise spec.md.

Create multiple git commits, one per concern, from changes in the working tree, then push them

Create multiple git commits, one per concern, from changes in the working tree

Draft a new version section in CHANGELOG.md for prayer-times by summarising commits since the last release tag. Use when the user says "update the changelog", "prep the changelog for release", "add changelog entry", or anything similar. Draft-only — does not run cargo release.

Generate changelog and bump version. Use when the user invokes /release.

Bump version in flake.nix, commit, and tag the release