furkankoykiran

github-comment

Write GitHub issue comments, PR descriptions and review replies that read like a real developer wrote them, matching the thread's existing tone. Use before posting anything to a GitHub conversation.

solve-issue

Solve a GitHub issue end-to-end and open a pull request. Use when the user wants to fix or resolve a specific GitHub issue (often by number or URL), or says "solve issue

toolkit-update

Check for and apply FK Claude Toolkit updates, or switch the stable/edge channel.

humanizer

Strip the tells of AI-generated writing — inflated symbolism, promotional phrasing, vague attribution, em-dash and rule-of-three overuse. Use when text should read as human-written, or the user says it "sounds like AI".

find-issues

Find open issues in ONE GitHub repository that fit the user's contribution profile. Use for "what can I contribute to <repo>" or good-first-issue hunting in a single repo.

find-repos

Find contribution opportunities across an entire GitHub organisation, ranked by fit against the profile in ~/.claude/config.json. Use when no single repo is named.

pr-followup

Read a pull request's latest review discussion and act on the pending feedback. Use for "follow up on PR

manim-narration

Build a Manim video with spoken narration synced to the animation. Use for a "narrated Manim video", "anlatımlı manim", "manim with voice", a PR walkthrough video, or code that imports NarratedScene. ManimCE only.

blog-from-chat

Turn a chat log, conversation or discussion summary into a publishable blog post, in one or more languages. Use for "blog from this chat" or "write up our conversation".

github-profile-blog

Write an educational blog post analysing a GitHub profile's public activity. Use for "blog about my GitHub" or a write-up of someone's open-source work.