Skip to content

CLAUDE.md

Latest commit

 

History

History
112 lines (75 loc) · 3.1 KB

CLAUDE.md

File metadata and controls

112 lines (75 loc) · 3.1 KB
Raw

Claude Code Agent Instructions

YouTrack Ticket Workflow

Before Starting Work

  1. Ask the user for the YouTrack ticket ID or number (e.g. "DBA-123" or just "123", which you can expand to "DBA-123"). If the YouTrack MCP is not available, refer the user to DEVELOPMENT.md for setup instructions.

  2. If a ticket is provided: read it with get_issue to understand the scope, context, and any discussion before proceeding.

  3. If no ticket exists: propose one to the user before creating it — show a human-readable preview (summary, description, type, state, sprint) and wait for approval. Create it only after confirmation.

Commit Messages

Always include the ticket ID in commits:

[DBA-123] Add support for Snowflake authentication

After Creating a Pull Request

Move the associated YouTrack ticket to Review state using update_issue.

After Completing Work

When you finish implementing changes:

  1. Run pre-commit checks:

    make check
# or directly: uv run pre-commit run --all-files

  2. Run tests:

    make test
# or directly: uv run pytest -v

  3. After checks pass, suggest to the user that you can help create a branch, commit changes, and create a pull request.

Wait for user confirmation before proceeding.

If User Confirms

  1. Check if GitHub CLI is installed:

    gh auth status

    If not installed or not authenticated, guide the user to DEVELOPMENT.md for setup instructions. They can also choose to create the PR manually.

  2. Determine the branch name prefix:

    • Extract branch prefixes from existing remote branches, filtering out system prefixes (dependabot, revert-*, HEAD)
    • Use the most common matching prefix as the user's nickname
    • If no existing branches found, ask the user for their nickname
    • Branch format: <nickname>/<descriptive-branch-name>

    Strategy:

    # Extract and count branch prefixes, excluding system prefixes
git branch -r | sed -nE 's|^ *origin/([^/]+)/.*|\1|p' | grep -vE '^(dependabot|HEAD|revert-)' | sort | uniq -c | sort -rn

  3. Create a separate branch with the appropriate prefix (never commit directly to main)

  4. Commit the changes with clear, descriptive commit messages

  5. Create a Pull Request with the following format:

Pull Request Format

## Summary
Brief overview of what was changed and why.

## Changes

### Change 1: [Feature/Fix Name]
Brief description of this specific change.

<details>
<summary>Affected files</summary>

- `path/to/file1.py`
- `path/to/file2.py`
- `path/to/file3.py`

</details>

### Change 2: [Another Feature/Fix Name]
Brief description of this specific change.

<details>
<summary>Affected files</summary>

- `path/to/file4.py`
- `path/to/file5.py`

</details>

## Test Plan
- How the changes were tested
- Any manual testing steps required

Guidelines

  • Each logical change should be its own section
  • List all affected files under a collapsible <details> spoiler
  • Keep descriptions clear and concise
  • Include relevant context for reviewers