@d
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 commit4---56## Context78- 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
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 main4---56## Context78- 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
An agent skill to work on a Linear issue. Can be used in parallel with worktrees.
1---2name: work-on-linear-issue3description: 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---56You should follow these steps:781. 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
There has been mulitple changes, improvements and new features since the last version tag 1.0.3. I want you to performa a full-scale review. Go through every file that has been changed while looking at the git logs to understand the intention. - What I want you to do is for the app side see if there is any new hardcoded string or a string that has been only added to English and missing from the Turkish one, if you find any fix it. - Again for the app side go through all the new changes and see if there is anything that could be simplifed, for example if there are identical style definitions merge them following the best practices. In general if any best practice nudges you to simplify a section, do so. - Perform a full security review on the app side.
