← all publishers

inancgumus

@inancgumus source repo

19 published skills

  1. Go · inancgumus
    Use when writing/reviewing Go code to apply modern practices.
    0
    installs
  2. Init · inancgumus
    Use at the start of a session to load the standing engineering rules
    0
    installs
  3. Coder · inancgumus
    Use when you implement, debug, or change code.
    0
    installs
  4. Slack · inancgumus bundle
    Read, navigate, search, and send messages in Slack via the local desktop app. Use when the user mentions Slack, a *.slack.com URL, or a channel name.
    0
    installs
  5. Write · inancgumus bundle
    Write prose that does not read like AI, and strip AI tells from existing text without changing what it says. Use whenever drafting prose a human will read (docs, posts, announcements, emails, reports) and whenever asked to humanize text, make it sound less like AI or ChatGPT, remove AI slop, or give generated prose a quality pass, even when the request is just "clean this up" or "does this read like AI?". Detects the tells, rewrites only what has a real point, flags hollow spans instead of inventing claims, and self-scores against a rubric before delivering.
    0
    installs
  6. Git Pr · inancgumus
    Use when drafting or revising PR descriptions, including when the user asks for adding or updating a PR title or description.
    0
    installs
  7. Handoff · inancgumus
    Session handoff tool. Writes or loads a HANDOFF.md file to preserve and restore session state across agent sessions.
    0
    installs
  8. Architect · inancgumus
    Use when you design modules, refactor, or review architecture.
    0
    installs
  9. Designdoc · inancgumus bundle
    Write or rewrite internal technical design docs, RFCs, and proposal docs so a reader with no prior context can quickly understand the problem, the options, the tradeoffs, and the recommendation. Use when drafting a new design doc, restructuring a weak one, comparing proposals, or reviewing a doc that reads like a story instead of a design. Also use when the user mentions RFC, design review, architecture proposal, or ADR.
    0
    installs
  10. Flowchart · inancgumus bundle
    Generate flowcharts and architecture diagrams as interactive HTML or Markdown+ASCII. Use when asked to visualize, diagram, or map out any system, flow, or structure.
    0
    installs
  11. Git Issue · inancgumus
    Write and file GitHub issues, both bug reports and everything else (feature requests, proposals, tech-debt briefs, questions). Use when the user asks to file, open, write, or draft an issue, to report a bug upstream, to turn a finding into a ticket, or to rewrite an existing issue body. Not for pull requests.
    0
    installs
  12. Git Split · inancgumus bundle
    Use to split commits into atomic commits
    0
    installs
  13. Heartbeat · inancgumus bundle
    Team Heartbeat
    0
    installs
  14. Learnings · inancgumus
    Use to capture learnings from this session
    0
    installs
  15. Git Commit · inancgumus
    Write commit messages, create commits, and rewrite Git history safely. Use before drafting any commit message, running git commit, creating fixup commits, rebasing, squashing, amending, cherry-picking, or otherwise changing commit history.
    0
    installs
  16. Git Pr Review · inancgumus bundle
    Review a GitHub pull request. Use when asked to review a PR, given a PR URL, told to "review this", asked to annotate a diff or leave draft comments without sending a review, or asked to handle the author's replies to an earlier review.
    0
    installs
  17. Writing Style · inancgumus
    Writing Style
    0
    installs
  18. Gh Review Reqs · inancgumus bundle
    List open GitHub PRs that need my review attention, across all repos. Use when the user asks what PRs await their review, to check their review requests or review queue, which PRs are waiting on them, or what they should review today — even if they don't say "PR" explicitly.
    0
    installs
  19. Claude Sessions · inancgumus bundle
    List recent Claude Code sessions (name, last message date, working directory, last prompt) and resume any of them in new iTerm tabs. Use this whenever the user asks about their past or recent Claude sessions, wants to see or page through their session history, asks what they were working on in another session, or wants to reopen, resume, or "bring up" one session or the last N sessions — in a new tab or a new window — even if they never say the word "session".
    0
    installs