Dzhuneyt
- 16 skills
- 0 followers
- 14 hours ago last updated
- ▌
- ▌ Gh Pr · dzhuneytOpen a GitHub pull request (draft or ready for review) from the current branch using the gh CLI. Use this whenever the user wants to open, create, raise, submit, or "ship" a PR / pull request, or says things like "open a PR", "PR this branch", "put this up for review", or invokes /gh-pr — even when they don't specify the base branch, title, or description. Handles pushing the branch, writing the title and body from the actual diff, respecting the repo's PR template, linking issues, and dropping to --draft for unfinished work.
- ▌ Reflect · dzhuneytUse when the user invokes /reflect or asks to reflect on, wrap up, or take stock of the current session. Re-reads the in-context conversation for anything that would die when the session closes — dropped action items, durable lessons with no home, stale docs, skillify opportunities, global/project CLAUDE.md and AGENTS.md and README gaps, and follow-ups worth an issue or a PR — surfaces them as one ranked shortlist, then acts on the ones the user selects. Not a git-history retro and not a full doc audit.
- ▌ Clipboard · dzhuneytCopy the last meaningful output from the conversation to the macOS clipboard via pbcopy. Use when user wants to copy, grab, or export the last response.
- ▌ Git Commit · dzhuneytAnalyze uncommitted changes and suggest a conventional commit message with option to commit and push
- ▌ Git Update · dzhuneytSafely update branch by fetching, checking for conflicts, stashing, rebasing, and restoring changes
- ▌
- ▌ Gh Pr Review · dzhuneytUse when user asks to review a pull request by number, URL, or branch ("review this PR", "review PR 123"). Fetches PR details, reads diff and failing checks, produces structured feedback across code quality, security, performance, testing, docs, architecture, dependencies, CI/CD coverage, and completeness. Accepts optional $ARGUMENTS for the PR reference.
- ▌ Refactor Safe · dzhuneytUse when user asks for safe refactoring suggestions, refactor opportunities, or cleanup ideas. Analyzes codebase patterns (duplicate blocks, long functions, magic values, unused code, simple type improvements) and proposes low-risk refactors grouped by safety level. Does not execute changes — suggests only.
- ▌ Apple Reminders · dzhuneytUse when user asks to manage Apple Reminders on macOS — create, list, update, complete, or delete reminders and lists via osascript/AppleScript. No dependencies required.
- ▌ Research Fanout · dzhuneytInteractive research orchestrator. Scopes a high-level research goal through a short interview, presents an approvable nested plan tree of sub-questions ("unknown unknowns"), then fans out parallel subagents (with per-branch model tiering for cost) and rolls up their findings live into a written report plus executive summary. Use when the user wants to research a broad or fuzzy topic, explore unknown unknowns, run a deep multi-angle investigation, or mentions fan-out research, a research plan, or a research report.
- ▌ Gh Notifications · dzhuneytUse when user wants to review, triage, or surface important GitHub notifications — daily digest, notification fatigue, or "what should I look at?"
- ▌ Git Diff Explain · dzhuneytUse when user asks what changed, requests a diff summary, or says "explain my changes". Scans uncommitted changes (staged and unstaged) and produces a one-sentence summary of what was modified.
- ▌ Git Branch Cleanup · dzhuneytUse when stale git branches pile up after pull requests merge — local branches marked [gone], squash-merged branches that `git branch --merged` does not list, or leftover remote branches in a repo without auto-delete. Also use when the user names branches to purge, or asks to clean up, prune, or purge branches.
- ▌ Pyramid Discussion · dzhuneytFacilitates a top-down pyramid discussion that calibrates the user's topic depth, then starts at high-level goals and progressively descends to concrete actionables, sharpening gaps and assumptions at each layer. Use when the user wants to break down a goal, explore a vision, elicit requirements, or mentions pyramid discussion, top-down planning, or progressive breakdown.
- ▌ Code Comments Improve · dzhuneytUse when user asks to improve, add, or clean up code comments, focusing on WHY over WHAT. Reads specified files (or recently modified ones), adds strategic inline comments for non-obvious logic, removes redundant ones, and converts WHAT-comments to WHY-comments. Accepts optional $ARGUMENTS for target files.