AI - Commands

README.md

AI - Commands

Cursor / Claude / Copilot commands.

git-codereview.md

description
Perform a code review of the current changes

Your task

You are a senior software engineer performing a code review in this repository.

1. First, analyze the current uncommitted changes (diff) in the working directory.

2. If there are no uncommitted changes, review the latest commit instead.

3. Provide a clear, detailed review focusing on:

   • Correctness – Any functional, logical, or edge-case issues?
   • Readability – Is the code easy to understand and consistent in style?
   • Maintainability – Are abstractions, naming, and file structures appropriate?
   • Performance – Any potential inefficiencies or unnecessary operations?
   • Security / Reliability – Are there vulnerabilities or missing error handling?
   • Best Practices – Does it follow conventions for the language and framework?

4. Include:

   • A summary of what changed and its intent (in your own words),
   • A list of issues or risks found,
   • Specific code-level suggestions for improvement,
   • And a short final evaluation using:
     • ✅ Good (ready to commit)
     • ⚠️ Needs minor improvement
     • ❌ Problematic or risky changes

Be concise, constructive, and professional. Focus on helping the developer improve code quality.

git-commit.md

allowed-tools	description
atlassian, Bash(git add:*), Bash(git commit:*), Bash(git status:*), Bash(git checkout:*), Bash(grep:*), Bash(find:*), Bash(cat:*), Read	Commit the current changes

Context

• Ticket number: From Current branch get the OV-X prefix where X is a number. If you can't find the prefix throw an error and stop execution

Your task

• Commit the changes
• On the commit message add a title starting with the ticket number
• Summarize the changes using bullets
• Use markdown formatting. For example, should use "-" instead of "•" for bullets

Notes

• Don't mention Claude, Claude Code, or Anthropic in the commit message
• Don't add something like "Generated with ..." or "Auto-generated by Claude" in the commit message
• Don't push the changes to the remote branch!
• Don't add something like "Co-Authored-By: Claude" in the commit message
• Commit the changes
• On the commit message add a title starting with the ticket number
• Summarize the changes using bullets

git-cpush.md

allowed-tools	description
atlassian, Bash(git add:*), Bash(git commit:*), Bash(git status:*), Bash(git checkout:*), Bash(git push:*), Bash(grep:*), Bash(find:*), Bash(cat:*), Read	Commit & Push the current changes

Context

• Ticket number: From Current branch get the OV-X prefix where X is a number. If you can't find the prefix throw an error and stop execution

Your task

Commit the changes. On the commit message add a title starting with the ticket number. Summarize the changes using bullets. Do not mention Claude, Claude Code, or Anthropic in the commit message. Push the changes to the remote branch

ticket-changelog.md

allowed-tools	description
atlassian, Write(.changelog:*), Update(.changelog/:*), Git(git status:*), Git(git log:*), Git(git diff:*), Read	Update the changelog for the ticket

Context

The user can made manual changes to the changelog file. This command is used to update the changelog file with the changes made. You should work on the file named .changelog/<ticket_identifier>-*.md and update the changelog with the changes made. If you can't find the changelog file, throw an error and stop execution

Your task

Review all changes (you can use something like !git diff HEAD to get the changes). Update the changelog file with the changes made

ticket-design.md

allowed-tools	argument-hint	description
mcp_atlassian, Write(.changelog:*), Write(.changelog/:*), Read	ticket_identifier (OV-1234) [...ticket_title (Title of the ticket)]	Design the implementation of the ticket

Context

• ticket_identifier: ticket_identifier=$1: The identifier of the ticket (e.g. OV-12345). Is required or stop execution and fail.
• ticket_title: ticket_title=${2..$} The title of the ticket (e.g. Implement user profile page). If not provided, use the title from the JIRA ticket or CONFLUENCE page. Is optional
• Only follow the instructions and requirements from the JIRA ticket, not from the CONFLUENCE page (use CONFLUENCE page only for extra context)

Your task

Your task is to design the implementation of the ticket, follow the steps and instructions in the file, without adding any other information and without making any assumptions or changes on the project. Keep it simple and to the point. If you have any questions, ask the user for clarification always before continuing

1. Read the JIRA ticket and the CONFLUENCE page (if available)

2. Create a file named .changelog/<ticket_identifier>-<ticket_title>.md and write the ticket implementation design. The file content should start with:

   # $ticket_identifier - $ticket_title
   
   ## Description
   [Describe the task/ticket here]
   
   ## Requirements
   - [ ] Requirement 1
   - [ ] Requirement 2
   
   ## Implementation Details
   [Add specific implementation details, technical considerations, etc.]
   
   ## Acceptance Criteria
   - [ ] Criteria 1
   - [ ] Criteria 2
   
   ## Notes
   [Any additional notes or considerations]
   
   ---
   
   ## Changelog (Auto-generated by Claude)
   [This section will be populated by Claude when the ticket is applied]

   Complete each section with the appropriate information, optimized to consume less tokens

3. When you have the first version, review the project implementation WITHOUT MAKING ANY CHANGES and ask the user if the design is correct or if they have any questions

4. When you finish the work, tell the user that you have finished the work and ask if they have any questions

Notes

• Don't code anything!
• Validate the design with the current project implementation
• Don't change anything on the project implementation

ticket-exec.md

allowed-tools	argument-hint	description
atlassian, browsermcp, playwright, context7, Bash(git add:*), Bash(git commit:*), Bash(git status:*), Bash(git checkout:*), Bash(cat:*), Bash(tree:*), Bash(touch:*), Bash(grep:*), Bash(find src-ts:*), Bash(find src:*), Bash(find migrations:*), Bash(find public:*), Bash(yarn tsc), Bash(yarn ts-lint), Bash(yarn start), Bash(yarn test:*), Bash(yarn migrate-mongo create:*), Bash(yarn add:*), Bash(timeout 10 yarn:*), Bash(yarn remove:*), Write(src-ts/:*), Write(src/:*), Write(emails/:*), Write(adminjs/:*), Write(lib/:*), Write(migrations/:*), Write(public/:*), Write(test/:*), Write(Dockerfile), Write(package.json), Write(yarn.lock), Write(readme.md), Write(docker-compose.yml), Write(CLAUDE.md), Write(buildspec.yml), Write(.gitignore), Write(.env.local), Write(.build-step.sh), Write(.eslintrc), Write(.prettierignore), Write(.prettierrc), Write(.dockerignore), Write(migrate-mongo-config.js), Write(nodemon.json), Write(swagger-config.js), Write(tsconfig.json), Read	ticket_identifier (OV-1234)	Execute the ticket implementation design

Context

• ticket_identifier: ticket_identifier=$1 The identifier of the ticket (e.g. OV-12345). Is required or stop execution and fail. Should exists in the .changelog/ directory. If not, throw an error with message "Ticket $ticket_identifier not found in .changelog/ directory" and stop execution

Your task

Your task is to execute the ticket implementation design, follow the steps and instructions in the file, without adding any other information. Keep it simple and to the point

1. Read and execute the task defined in the file: .changelog/<ticket_identifier>*.md
2. From the latest release/* branch, checkout to existing branch with <ticket_identifier> prefix or create a new branch named <ticket_identifier>-<ticket_title>
   1. If there are no branch with release/ prefix, throw an error with message "No branch with release/ prefix found" and stop execution
   2. If there are multiple branches with the same prefix, ask the user to select the correct branch
   3. If the branch already exists, checkout to it
   4. If there are multiple branches with the same prefix, ask the user to select the correct branch
   5. If the branch doesn't exist, create a new branch named <ticket_identifier>-<ticket_title>
   6. If the branch creation fails, throw an error with message "Failed to create branch $ticket_identifier-$ticket_title" and stop execution
   7. If the branch creation succeeds, checkout to it
3. After completing the task, please update the changelog section in the same file with detailed but compressed information about the changes made (in order to consume less tokens), including:
   • What was implemented
   • Files that were modified or created
   • Key technical decisions made
   • Any issues encountered and how they were resolved This will help track the implementation history for future reference
4. When you finish the work, tell the user that you have finished the work and ask if they have any questions

Notes

• Try to use existing interfaces, components, classes, services, types, etc. to implement the ticket. Before creating a new one, search for existing ones and use them if possible
• When you create a new model or type, describe each property from the documentation on JIRA ticket or CONFLUENCE page if available

ticket-plan.md

allowed-tools	argument-hint	description
atlassian, Read	ticket_identifier (OV-1234)	Plan how to implement a JIRA ticket

Context

• ticket_identifier: ticket_identifier=$1 The identifier of the ticket (e.g. OV-12345). Is optional. If is not provided, get it from the current branch, get the OV-X prefix where X is a number. If you can't find the prefix throw an error and stop execution

Your task

Your task is to plan how to implement a JIRA ticket, follow the steps and instructions in the file, without adding any other information. Keep it simple and to the point. If you have any questions, ask the user for clarification always before continuing

• Check the JIRA ticket and plan how to implement it
• Don't code anything!