prompts.chatprompts.chatprompts.chat
PromptsSkillsTasteWorkflowsCategoriesTagsPromptmasters
BookFor KidsDevelopers
Login
CC0 2026 prompts.chat
DeepWikiHow to...DocsAPIPrivacyTermsSupportAboutGitHub
D

Doğu Deniz Uğur

@d

3prompts
0upvotes received
0contributions
Joined 4 days ago
3 contributions in the last year
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
M
W
F
Less
More
Claude Code Skill (Slash Command): review-and-commit.md
Text

A slash command for Claude Code to perform (a) commit(s) following the conventional style.

1---
2allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*)
3description: Create a git commit
4---
5
6## Context
7
8- Current git status: !`git status`
9- Current git diff (staged and unstaged changes): !`git diff HEAD`
10- Current branch: !`git branch --show-current`
...+5 more lines
Claude
D@d
0
Claude Code Skill (Slash Command): push-and-pull-request.md
Text

A Claude Code skill (slash command) to open a PR after committing all outstanding changes and pushing them.

1---
2allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*), Bash(git push:*), Bash(gh pr create:*)
3description: Commit and push everything then open a PR request to main
4---
5
6## Context
7
8- Current git status: !`git status`
9- Current git diff (staged and unstaged changes): !`git diff HEAD`
10- Current branch: !`git branch --show-current`
...+7 more lines
D@d
0
Work on Linear Issue
Text

An agent skill to work on a Linear issue. Can be used in parallel with worktrees.

1---
2name: work-on-linear-issue
3description: You will receive a Linear issue id usually on the the form of LLL-XX... where Ls are letters and Xs are digits. Your job is to resolve it on a new branch and open a PR to the branch main.
4---
5
6You should follow these steps:
7
81. Use the Linear MCP to get the context of the issue, the issue number is at $0.
92. Start on the latest version of main, do a pull if necesseray. Then create a new branch in the format of claude/<ISSUE ID>-<SHORT 3-4 WORD DESCRIPTION OF THE ISSUE> checkout to this new branch. All your changes/commits should happen on the new branch.
103. Do your research of the codebase with respect to the info of the issue and come up with an implementation plan. While planning if you have any confusions ask for clarifications. Enter to planning after every verification step.
...+3 more lines
claude-codeSkill
D@d
0