synapse-sdk 0.1.2a0__tar.gz → 1.0.0__tar.gz

synapse_sdk-1.0.0/.claude/commands/compare-branch.md

@@ -0,0 +1,14 @@
+---
+name: compare-branches
+description: Compare changes between branches
+---
+
+Please compare the changes between the current branch and main using GitHub MCP.
+
+Analyze:
+1. File changes and their impact
+2. Code quality improvements or regressions
+3. Potential conflicts or issues
+4. Testing implications
+
+Branch to compare: $ARGUMENTS (default: main if not specified)

synapse_sdk-1.0.0/.claude/commands/review-pr.md

@@ -0,0 +1,137 @@
+---
+name: review-pr
+description: Comprehensive PR review using GitHub MCP with P1-P4 Code Review Rules
+---
+
+Please perform a comprehensive review of PR using the GitHub MCP server.
+
+**Arguments:**
+- First argument: PR number (required)
+- Second argument: Language for review comments - "en" for English, "ko" for Korean (optional, defaults to "en")
+
+**Usage Examples:**
+- `/review-pr 123` - Review PR #123 with English comments
+- `/review-pr 123 en` - Review PR #123 with English comments  
+- `/review-pr 123 ko` - Review PR #123 with Korean comments
+
+**Parse Arguments:**
+Extract PR number from first argument and language preference from second argument (if provided). If second argument is not "ko", default to English ("en").
+
+**IMPORTANT Review Decision Logic:**
+1. **Track all P1, P2, P3 violations found during review**
+2. **If ANY P1, P2, or P3 violations are found** → Use `--request-changes`
+3. **If ONLY P4 violations or no violations found** → Use `--approve`
+4. **Never use `--comment` as the main review action** - always choose between approve or request-changes
+
+**Review Process:**
+1. Read and load P1-P4 Code Review Rules from the following files:
+   - P1_rules.md (Critical - Security and Stability)
+   - P2_rules.md (High Priority - Core functionality and architecture)
+   - P3_rules.md (Medium Priority - Best practices and maintainability)
+   - P4_rules.md (Low Priority - Code style and formatting)
+2. Fetch PR details and file changes
+3. Apply P1-P4 Code Review Rules systematically against the changes
+4. Analyze code quality, security, and performance
+5. Check for test coverage and documentation
+6. Look for potential bugs or issues
+7. Provide specific, actionable feedback with priority levels
+8. Create review comments directly on the PR for each issue found
+
+**P1-P4 Code Review Rules Application:**
+
+IMPORTANT: Before starting the review, read the complete rule sets from these files:
+- `P1_rules.md`
+- `P2_rules.md`
+- `P3_rules.md`
+- `P4_rules.md`
+
+Apply ALL rules from these files during the review process. The rules cover:
+
+**P1 Rules (Critical - MUST FIX):**
+- Security and database integrity issues
+- Critical Django/DRF patterns
+- System stability concerns
+
+**P2 Rules (High Priority):**
+- Core Django/DRF best practices
+- Architecture and design patterns
+- Performance considerations
+
+**P3 Rules (Medium Priority):**
+- Code maintainability
+- Best practices and conventions
+- Safety and error handling
+
+**P4 Rules (Low Priority - Style):**
+- Code formatting and style
+- Naming conventions
+- Consistency standards
+
+**Review Output Format:**
+For each violation found:
+1. **Report to user** with this format:
+   - **Rule Category:** P1/P2/P3/P4
+   - **Specific Rule:** Quote the exact rule from the files
+   - **Location:** File and line number
+   - **Issue:** What violates the rule
+   - **Recommendation:** How to fix it based on the rule guidance
+   - **Impact:** Why this matters (reference rule explanation)
+
+2. **Create PR review comment** using GitHub CLI:
+   - Use `gh pr review {PR_NUMBER} --comment-body "comment text"` for general review comments
+   - Use `gh pr comment {PR_NUMBER} --body "comment text"` for specific line comments when applicable
+   - Format comments with clear priority indicators: [P1], [P2], [P3], [P4]
+   - Include rule reference and actionable guidance in each comment
+   - **IMPORTANT:** Write all comments in the selected language (English or Korean)
+
+**Review Actions:**
+1. **Submit overall review** with summary using: `gh pr review {PR_NUMBER} --approve/--request-changes --body "overall review summary"`
+2. **Add individual comments** for each rule violation found
+3. **Use appropriate review status:**
+   - `--request-changes` if any P1, P2, or P3 violations are found
+   - `--approve` if only P4 violations or no issues found
+   - `--comment` for informational feedback only (no rule violations)
+4. **Language Requirements:**
+   - Write ALL review comments and summary in the selected language
+   - Use appropriate technical terminology for the chosen language
+   - Maintain professional tone in both languages
+
+**Focus Areas:**
+- **Priority 1 (P1):** Critical security and stability issues (MUST FIX) → REQUEST CHANGES
+- **Priority 2 (P2):** Core functionality and architecture (SHOULD FIX) → REQUEST CHANGES  
+- **Priority 3 (P3):** Best practices and maintainability (SHOULD FIX) → REQUEST CHANGES
+- **Priority 4 (P4):** Code style and formatting (OPTIONAL) → APPROVE WITH COMMENTS
+- Test coverage and documentation completeness
+- Breaking changes and backward compatibility
+
+**GitHub CLI Commands to Use:**
+- `gh pr view {PR_NUMBER} --json title,body,state,author,files,commits`
+- `gh pr diff {PR_NUMBER}`
+- `gh pr review {PR_NUMBER} --comment-body "review summary"`
+- `gh pr comment {PR_NUMBER} --body "specific comment"`
+
+**Language-Specific Comment Templates:**
+
+**English Template:**
+```
+[P{LEVEL}] **{TITLE}**
+
+{DESCRIPTION}
+
+**Location:** {FILE}:{LINE}
+**Issue:** {ISSUE_DESCRIPTION}
+**Recommendation:** {RECOMMENDATION}
+**Rule Reference:** {RULE_QUOTE}
+```
+
+**Korean Template:**
+```
+[P{LEVEL}] **{TITLE}**
+
+{DESCRIPTION}
+
+**위치:** {FILE}:{LINE}  
+**문제점:** {ISSUE_DESCRIPTION}
+**권장사항:** {RECOMMENDATION}
+**규칙 참조:** {RULE_QUOTE}
+```

synapse_sdk-1.0.0/.claude/commands/update-pr-desc.md

@@ -0,0 +1,20 @@
+# Update PR Description Command
+
+You will help the user update a PR description with various options.
+
+## Available Options:
+- `--pr <number>`: Specify PR number (optional - uses current branch if not provided)
+- `--lang <language>`: Description language (korean/english, default: korean)
+
+## Examples:
+- `/update-pr-desc --pr 123 --lang ko`: Update PR #123 with Korean description
+- `/update-pr-desc --lang eng`: Update current branch PR with English description
+- `/update-pr-desc`: Update current branch PR with Korean description (default)
+
+## Implementation:
+1. If PR number not provided, find PR for current branch
+2. Generate commit diff analysis
+3. Create appropriate PR description in specified language
+4. Update the PR description
+
+Please provide the PR number and desired language, or use defaults for current branch and Korean

synapse_sdk-1.0.0/.claude/commands/update-pr-title.md

@@ -0,0 +1,32 @@
+# Update PR Title Command
+
+You will help the user update a PR title with various options.
+
+## Available Options
+
+- `--pr <number>`: Specify PR number (optional - uses current branch if not provided)
+- `--lang <language>`: Title language (korean/english, default: korean)
+
+## Examples
+
+- `/update-pr-title --pr 123 --lang ko`: Update PR #123 with Korean title
+- `/update-pr-title --lang eng`: Update current branch PR with English title
+- `/update-pr-title`: Update current branch PR with Korean title (default)
+
+## Implementation
+
+1. If PR number not provided, find PR for current branch
+2. Analyze commit messages and changes to understand the scope
+3. Generate a concise, descriptive title in specified language
+4. Keep any existing ticket ID (e.g., SYN-XXXX) at the beginning
+5. Update the PR title
+
+## Title Guidelines
+
+- Keep titles concise but descriptive (under 72 characters when possible)
+- Include the ticket ID if present
+- Summarize the main feature/fix/change
+- Use appropriate language (Korean/English)
+- Follow conventional commit style when applicable
+
+Please provide the PR number and desired language, or use defaults for current branch and Korean

synapse_sdk-1.0.0/.github/workflows/pypi-publish.yml

@@ -0,0 +1,102 @@
+# This workflow will upload a Python Package using Twine when a release is created
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries
+
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+name: Upload Python Package
+
+on:
+  workflow_dispatch:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    name: Build distribution 📦
+    runs-on: runner-set
+    steps:
+      - uses: actions/checkout@v5
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install build
+      - name: Compile i18n messages
+        run: |
+          msgfmt locale/ko/LC_MESSAGES/messages.po -o locale/ko/LC_MESSAGES/messages.mo
+          msgfmt locale/en/LC_MESSAGES/messages.po -o locale/en/LC_MESSAGES/messages.mo
+      - name: Build package
+        run: python -m build
+
+      - name: Install AWS CLI
+        run: pip install awscli
+
+      - name: Store the distribution packages to MinIO ☁️
+        env:
+          AWS_ACCESS_KEY_ID: ${{ secrets.ARTIFACTS_S3_ACCESS_KEY }}
+          AWS_SECRET_ACCESS_KEY: ${{ secrets.ARTIFACTS_S3_SECRET_KEY }}
+        run: |
+          # Create tarball of distribution packages
+          tar -czf dist.tar.gz -C dist .
+
+          # Upload to MinIO using AWS CLI
+          BUCKET_NAME="${{ vars.ARTIFACTS_S3_BUCKET_NAME }}"
+          OBJECT_KEY="dist.tar.gz"
+          
+          aws s3 cp dist.tar.gz s3://$BUCKET_NAME/$OBJECT_KEY --endpoint-url=https://datamaker-kr.cdn.datamaker.io
+
+          echo "Artifacts uploaded to: s3://$BUCKET_NAME/$OBJECT_KEY"
+          rm -f dist.tar.gz
+
+  publish-to-pypi:
+    name: Publish Python 🐍 distribution 📦 to PyPI
+    needs:
+      - build
+    environment: release
+    runs-on: runner-set
+    permissions:
+      # IMPORTANT: this permission is mandatory for trusted publishing
+      id-token: write
+    steps:
+      - name: Install AWS CLI
+        run: pip install awscli
+
+      - name: Retrieve distribution packages from MinIO ⬇️
+        env:
+          AWS_ACCESS_KEY_ID: ${{ secrets.ARTIFACTS_S3_ACCESS_KEY }}
+          AWS_SECRET_ACCESS_KEY: ${{ secrets.ARTIFACTS_S3_SECRET_KEY }}
+        run: |
+          # Download from MinIO using AWS CLI
+          BUCKET_NAME="${{ vars.ARTIFACTS_S3_BUCKET_NAME }}"
+          OBJECT_KEY="dist.tar.gz"
+          
+          aws s3 cp s3://$BUCKET_NAME/$OBJECT_KEY dist.tar.gz --endpoint-url=https://datamaker-kr.cdn.datamaker.io
+
+          # Extract artifacts
+          mkdir -p dist/
+          tar -xzf dist.tar.gz -C dist/
+          rm -f dist.tar.gz
+
+          echo "Artifacts retrieved from: s3://$BUCKET_NAME/$OBJECT_KEY"
+
+      - name: Publish distribution 📦 to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+      - name: Cleanup artifacts 🧹
+        if: always()
+        env:
+          AWS_ACCESS_KEY_ID: ${{ secrets.ARTIFACTS_S3_ACCESS_KEY }}
+          AWS_SECRET_ACCESS_KEY: ${{ secrets.ARTIFACTS_S3_SECRET_KEY }}
+        run: |
+          # Delete from MinIO using AWS CLI
+          BUCKET_NAME="${{ vars.ARTIFACTS_S3_BUCKET_NAME }}"
+          OBJECT_KEY="dist.tar.gz"
+          
+          aws s3 rm s3://$BUCKET_NAME/$OBJECT_KEY --endpoint-url=https://datamaker-kr.cdn.datamaker.io
+
+          echo "Artifacts cleaned up from: s3://$BUCKET_NAME/$OBJECT_KEY"

synapse_sdk-1.0.0/.github/workflows/test.yml

@@ -0,0 +1,35 @@
+name: Tests
+
+on:
+  pull_request:
+    types: [opened, reopened, synchronize]
+    branches: [main]
+  push:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: runner-set
+    strategy:
+      matrix:
+        python-version: ['3.12']
+      fail-fast: false
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Install uv
+      uses: astral-sh/setup-uv@v4
+      with:
+        version: "latest"
+
+    - name: Set up Python ${{ matrix.python-version }}
+      run: uv python install ${{ matrix.python-version }}
+
+    - name: Install dependencies
+      run: |
+        uv sync --extra test
+
+    - name: Run test with coverage
+      run: |
+        make test-coverage

synapse_sdk-1.0.0/.gitignore

@@ -0,0 +1,60 @@
+# virtualenv
+.venv
+
+# idea
+.DS_Store
+*.pyc
+.idea
+*.iml
+
+# vscode
+.vscode
+
+# http
+/http/
+
+# general things to ignore
+build/
+*.egg-info/
+*.egg
+*.py[cod]
+__pycache__/
+*.so
+*~
+
+# due to using tox and pytest
+.tox
+.cache
+
+# python
+/main.py
+
+*.mo
+messages.pot
+
+# Frontend development (keep only built assets)
+node_modules/
+dist/
+npm-debug.log*
+
+config.yaml*
+
+synapse-sample-plugin/
+
+# Environment variables
+.env
+
+# Local LLM Rule Files
+CLAUDE.local.md
+GEMINI.local.md
+AGENT.local.md
+
+# Specs for LLM development
+specs/*.local.md
+
+# Claude
+settings.local.json
+
+# Test
+.coverage
+coverage.xml

synapse_sdk-1.0.0/.mcp.json

@@ -0,0 +1,22 @@
+{
+  "mcpServers": {
+    "github": {
+      "command": "docker",
+      "args": [
+        "run",
+        "-i",
+        "--rm",
+        "-e",
+        "GITHUB_PERSONAL_ACCESS_TOKEN",
+        "ghcr.io/github/github-mcp-server"
+      ],
+      "env": {
+        "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_TOKEN}"
+      }
+    },
+    "filesystem": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-filesystem", "./"]
+    }
+  }
+}

synapse_sdk-1.0.0/.pre-commit-config.yaml

@@ -0,0 +1,7 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.11.10
+    hooks:
+      - id: ruff
+        args: [ --fix ]
+      - id: ruff-format