ynab-amazon-categorizer 0.0.0__tar.gz

ynab_amazon_categorizer-0.0.0/.claude/tdd-guard/data/.claude/tdd-guard/data/instructions.md

@@ -0,0 +1,50 @@
+## TDD Fundamentals
+
+### The TDD Cycle
+The foundation of TDD is the Red-Green-Refactor cycle:
+
+1. **Red Phase**: Write ONE failing test that describes desired behavior
+   - The test must fail for the RIGHT reason (not syntax/import errors)
+   - Only one test at a time - this is critical for TDD discipline
+   - **Adding a single test to a test file is ALWAYS allowed** - no prior test output needed
+   - Starting TDD for a new feature is always valid, even if test output shows unrelated work
+
+2. **Green Phase**: Write MINIMAL code to make the test pass
+   - Implement only what's needed for the current failing test
+   - No anticipatory coding or extra features
+   - Address the specific failure message
+
+3. **Refactor Phase**: Improve code structure while keeping tests green
+   - Only allowed when relevant tests are passing
+   - Requires proof that tests have been run and are green
+   - Applies to BOTH implementation and test code
+   - No refactoring with failing tests - fix them first
+
+### Core Violations
+
+1. **Multiple Test Addition**
+   - Adding more than one new test at once
+   - Exception: Initial test file setup or extracting shared test utilities
+
+2. **Over-Implementation**  
+   - Code that exceeds what's needed to pass the current failing test
+   - Adding untested features, methods, or error handling
+   - Implementing multiple methods when test only requires one
+
+3. **Premature Implementation**
+   - Adding implementation before a test exists and fails properly
+   - Adding implementation without running the test first
+   - Refactoring when tests haven't been run or are failing
+
+### Critical Principle: Incremental Development
+Each step in TDD should address ONE specific issue:
+- Test fails "not defined" → Create empty stub/class only
+- Test fails "not a function" → Add method stub only  
+- Test fails with assertion → Implement minimal logic only
+
+### General Information
+- Sometimes the test output shows as no tests have been run when a new test is failing due to a missing import or constructor. In such cases, allow the agent to create simple stubs. Ask them if they forgot to create a stub if they are stuck.
+- It is never allowed to introduce new logic without evidence of relevant failing tests. However, stubs and simple implementation to make imports and test infrastructure work is fine.
+- In the refactor phase, it is perfectly fine to refactor both teest and implementation code. That said, completely new functionality is not allowed. Types, clean up, abstractions, and helpers are allowed as long as they do not introduce new behavior.
+- Adding types, interfaces, or a constant in order to replace magic values is perfectly fine during refactoring.
+- Provide the agent with helpful directions so that they do not get stuck when blocking them.

ynab_amazon_categorizer-0.0.0/.claude/tdd-guard/data/config.json

@@ -0,0 +1 @@
+{"guardEnabled":false}

ynab_amazon_categorizer-0.0.0/.claude/tdd-guard/data/instructions.md

@@ -0,0 +1,118 @@
+## Rules
+
+TDD follows a strict Red-Green-Refactor cycle:
+
+### Red Phase - Write a Failing Test
+- Write ONE test that describes desired behavior
+- The test must fail for the right reason (not syntax/import errors)
+- No prior test output required - writing the first test starts the cycle
+- Starting a new cycle is always valid, even with no test output, all tests passing, or test output showing unrelated work
+- **Rule**: Only one new test at a time, regardless of operation type (Edit, MultiEdit, or Write)
+
+### Green Phase - Make the Test Pass
+- Write MINIMAL code to pass the current failing test
+- Match implementation precisely to the failure type:
+
+| Test Failure Message | Required Implementation |
+|---------------------|------------------------|
+| "not defined" / "undefined" / "not found" | Create empty stub/class/module only |
+| "not a constructor" / "cannot instantiate" | Create empty class only |
+| "not a function" / "not callable" / "not a method" | Add method/function stub only |
+| Assertion error (e.g., "expected X to be Y") | Implement minimal logic for assertion only |
+
+- **Rule**: No anticipatory coding, extra features, or untested error handling
+
+### Refactor Phase - Improve Existing Code
+- Only enter this phase when relevant tests are passing
+- Requires evidence of green tests before any refactoring
+- Applies to BOTH test and implementation code
+- Allowed: Type additions, extracting helpers, reorganizing code, replacing magic values
+- Allowed in tests: Moving setup to beforeEach, extracting test helpers
+- **Rule**: No new functionality during refactoring
+
+## Validation Rules
+
+### Absolute Violations
+These always result in blocking:
+
+1. **Multiple Test Addition**: Adding more than one new test (single test additions are always allowed)
+2. **Over-Implementation**: Code exceeding current test requirements
+3. **Premature Implementation**: Writing code without a failing test
+4. **Refactoring with Red Tests**: Attempting refactor when tests are failing or missing
+
+### File-Specific Rules
+
+#### New File Creation
+- **Test files**: Must contain exactly ONE test initially
+- **Implementation files**: Must have failing test evidence justifying creation
+
+#### Existing File Modification
+- **Test files**: Can add ONE new test, modify existing tests, or refactor (if green)
+- **Implementation files**: Changes must match current test failure type
+
+### Permitted Exceptions
+- Configuration files (generally allowed)
+- Initial test file setup with utilities
+- Test helper and utility files
+- Stubs to fix import/infrastructure issues
+- Simple stubs when test output shows no tests due to missing imports or constructors
+- Removing code, tests, validations, or functionality
+- **Important**: Never introduce new logic without evidence of relevant failing tests
+
+## How to Analyze Changes
+
+### Counting New Tests
+A test is "new" only if it doesn't exist in the old content. Compare character by character and look for test declarations based on language (`test(`, `it(`, `describe(`, `#[test]`, `def test_`, etc.).
+
+**Example**: File has 3 existing tests, edit adds 2 more
+- Old content: `test("A")...`, `test("B")...`, `test("C")...`
+- New content: `test("A")...`, `test("B")...`, `test("C")...`, `test("D")...`, `test("E")...`
+- **Count**: 2 new tests added (D and E), not 5 tests total
+
+Not considered new:
+- Moving, renaming, or reformatting existing tests
+- Converting to parameterized tests or splitting into multiple tests
+
+### Identifying Relevant Tests
+Tests are "relevant" when they:
+- Exercise the code being modified
+- Would fail if the modified code broke
+- Import or depend on the changed module
+
+### Using Context Clues
+- **Test output**: Shows current phase and required implementation
+- **File paths**: Identify test vs implementation files
+
+## Decision Framework
+
+### When to Block
+Block when detecting clear TDD violations. Provide:
+1. Specific violation type
+2. Why it violates TDD
+3. Correct next step
+
+Provide helpful directions so the agent doesn't get stuck when blocking them. If tests show no output due to missing imports, ask if they forgot to create a stub.
+
+Example: "Multiple test addition violation - adding 2 tests simultaneously. Add only ONE test first."
+
+### When to Approve
+Approve when:
+- Changes follow TDD principles
+- Insufficient information to determine violation
+
+Example: "Adding single test to test file - follows TDD red phase"
+
+## Quick Reference Examples
+
+### Blocked Scenarios
+- Test shows "Calculator not defined" → Implementation adds class WITH methods
+- No test output → Creating new implementation file
+- Test failures present → Attempting to refactor
+- Single operation → Adding two or more tests
+
+### Approved Scenarios
+- Test shows "Calculator not defined" → Implementation adds empty class only
+- No test output → Adding first test to test file
+- Tests passing → Refactoring code structure
+- Single operation → Adding exactly one test
+- Any phase -> Removing implementation or test code

ynab_amazon_categorizer-0.0.0/.claude/tdd-guard/data/modifications.json

@@ -0,0 +1,10 @@
+{
+  "session_id": "bffb4a40-5bd7-47b6-b7d2-ce8ec612b0c6",
+  "transcript_path": "C:\\Users\\ksutk\\.claude\\projects\\C--Users-ksutk-projects-ynab-amazon-categorizer\\bffb4a40-5bd7-47b6-b7d2-ce8ec612b0c6.jsonl",
+  "hook_event_name": "PreToolUse",
+  "tool_name": "Write",
+  "tool_input": {
+    "file_path": "C:\\Users\\ksutk\\projects\\ynab-amazon-categorizer\\src\\ynab_amazon_categorizer\\__main__.py",
+    "content": "\"\"\"Allow running the package as a module with python -m ynab_amazon_categorizer.\"\"\"\n\nfrom .cli import main\n\nif __name__ == \"__main__\":\n    main()"
+  }
+}

ynab_amazon_categorizer-0.0.0/.env.example

@@ -0,0 +1,14 @@
+# YNAB Amazon Categorizer Configuration
+# Copy this file to '.env' and fill in your values
+
+# Your YNAB Personal Access Token
+# Get this from: https://app.ynab.com/settings/developer
+YNAB_API_KEY=your_api_key_here
+
+# Your YNAB Budget ID
+# Find this in your YNAB URL: https://app.ynab.com/[budget_id]/budget
+YNAB_BUDGET_ID=your_budget_id_here
+
+# Optional: Specific Account ID to process (leave as 'none' to process all accounts)
+# Find this in your YNAB URL when viewing an account
+YNAB_ACCOUNT_ID=none

ynab_amazon_categorizer-0.0.0/.github/workflows/release.yml

@@ -0,0 +1,125 @@
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - 'v*'
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+    
+    - name: Set up Python
+      uses: actions/setup-python@v4
+      with:
+        python-version: '3.9'
+    
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install -e .
+    
+    - name: Test package can be imported and run
+      run: |
+        python -c "from ynab_amazon_categorizer.cli import main; print('Package imports successfully')"
+
+  publish:
+    needs: test
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+    
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+    
+    - name: Set up Python
+      uses: actions/setup-python@v4
+      with:
+        python-version: '3.9'
+    
+    - name: Install build dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install build twine
+    
+    - name: Build package
+      run: python -m build
+    
+    - name: Check package
+      run: twine check dist/*
+    
+    - name: Publish to PyPI
+      uses: pypa/gh-action-pypi-publish@release/v1
+
+  create-release:
+    needs: [test, publish]
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+      with:
+        fetch-depth: 0
+    
+    - name: Extract version from tag
+      id: version
+      run: echo "VERSION=${GITHUB_REF#refs/tags/}" >> $GITHUB_OUTPUT
+    
+    - name: Generate changelog
+      id: changelog
+      run: |
+        # Get commits since last tag
+        LAST_TAG=$(git describe --tags --abbrev=0 HEAD^ 2>/dev/null || echo "")
+        if [ -n "$LAST_TAG" ]; then
+          CHANGELOG=$(git log --pretty=format:"- %s" $LAST_TAG..HEAD)
+        else
+          CHANGELOG=$(git log --pretty=format:"- %s" --max-count=10)
+        fi
+        
+        # Create changelog file
+        cat > CHANGELOG.md << EOF
+        ## What's Changed
+        
+        $CHANGELOG
+        
+        ## Installation
+        
+        This package is now available on PyPI! Install it with:
+        
+        \`\`\`bash
+        # Install with pipx (recommended for CLI tools)
+        pipx install ynab-amazon-categorizer
+        
+        # Or install with pip
+        pip install ynab-amazon-categorizer
+        \`\`\`
+        
+        ## Usage
+        
+        After installation, run:
+        \`\`\`bash
+        ynab-amazon-categorizer
+        \`\`\`
+        
+        See README.md for detailed setup and configuration instructions.
+        EOF
+    
+    - name: Create GitHub Release
+      uses: softprops/action-gh-release@v1
+      with:
+        tag_name: ${{ steps.version.outputs.VERSION }}
+        name: Release ${{ steps.version.outputs.VERSION }}
+        body_path: CHANGELOG.md
+        files: |
+          README.md
+        draft: false
+        prerelease: false
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

ynab_amazon_categorizer-0.0.0/.gitignore

@@ -0,0 +1,50 @@
+# YNAB API Credentials - NEVER COMMIT THESE!
+.env
+ynab_config.txt
+api_key.txt
+
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# Virtual environments
+venv/
+env/
+ENV/
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# OS
+.DS_Store
+Thumbs.db
+
+# History files
+.ynab_amazon_cat_history
+.ynab_amazon_memo_history
+
+# Release files
+RELEASE_NOTES.md
+temp_release.json
+release/