repr-cli 0.2.11__tar.gz → 0.2.13__tar.gz

{repr_cli-0.2.11/repr_cli.egg-info → repr_cli-0.2.13}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: repr-cli
-Version: 0.2.11
+Version: 0.2.13
 Summary: A beautiful, privacy-first CLI that analyzes your code repositories and generates a compelling developer profile
 Author-email: Repr <hello@repr.dev>
 License: MIT License

{repr_cli-0.2.11 → repr_cli-0.2.13}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "repr-cli"
-version = "0.2.11"
+version = "0.2.13"
 description = "A beautiful, privacy-first CLI that analyzes your code repositories and generates a compelling developer profile"
 readme = "README.md"
 license = {file = "LICENSE"}

{repr_cli-0.2.11 → repr_cli-0.2.13}/repr/__main__.py

@@ -38,6 +38,8 @@ if __name__ == "__main__":
 
 
 
+
+
 
 
 

{repr_cli-0.2.11 → repr_cli-0.2.13}/repr/auth.py

@@ -5,12 +5,15 @@ Tokens are stored securely in OS keychain (see keychain.py).
 """
 
 import asyncio
+import platform
+import socket
 import time
 from dataclasses import dataclass
 
 import httpx
 
 from .config import set_auth, clear_auth, get_auth, is_authenticated, get_api_base
+from .telemetry import get_device_id
 
 
 def _get_device_code_url() -> str:
@@ -25,6 +28,16 @@ POLL_INTERVAL = 5  # seconds
 MAX_POLL_TIME = 600  # 10 minutes
 
 
+def _get_device_name() -> str:
+    """Get a friendly device name for display."""
+    try:
+        hostname = socket.gethostname()
+        system = platform.system()
+        return f"{hostname} ({system})"
+    except Exception:
+        return "Unknown Device"
+
+
 @dataclass
 class DeviceCodeResponse:
     """Response from device code request."""
@@ -106,6 +119,8 @@ async def poll_for_token(device_code: str, interval: int = POLL_INTERVAL) -> Tok
                     json={
                         "device_code": device_code,
                         "client_id": "repr-cli",
+                        "device_id": get_device_id(),
+                        "device_name": _get_device_name(),
                     },
                     timeout=30,
                 )
@@ -314,6 +329,8 @@ class AuthFlow:
                             json={
                                 "device_code": device_code_response.device_code,
                                 "client_id": "repr-cli",
+                                "device_id": get_device_id(),
+                                "device_name": _get_device_name(),
                             },
                             timeout=30,
                         )

{repr_cli-0.2.11 → repr_cli-0.2.13}/repr/doctor.py

@@ -490,6 +490,8 @@ def run_all_checks() -> DoctorReport:
 
 
 
+
+
 
 
 

{repr_cli-0.2.11 → repr_cli-0.2.13}/repr/hooks.py

@@ -423,6 +423,8 @@ def queue_commit(repo_path: Path, commit_sha: str, message: str | None = None) -
     """Add a commit to the queue.
     
     Uses file locking to handle concurrent commits safely.
+    If auto_generate_on_hook is enabled and queue size meets batch_size,
+    triggers background story generation.
     
     Args:
         repo_path: Path to repository root
@@ -435,6 +437,8 @@ def queue_commit(repo_path: Path, commit_sha: str, message: str | None = None) -
     queue_path = get_queue_path(repo_path)
     lock_path = queue_path.with_suffix(".lock")
     
+    queue_size = 0
+    
     try:
         fd = _acquire_lock(lock_path)
         try:
@@ -452,7 +456,7 @@ def queue_commit(repo_path: Path, commit_sha: str, message: str | None = None) -
             })
             
             save_queue(repo_path, queue)
-            return True
+            queue_size = len(queue)
             
         finally:
             _release_lock(fd)
@@ -460,6 +464,100 @@ def queue_commit(repo_path: Path, commit_sha: str, message: str | None = None) -
     except QueueLockError:
         # Could not get lock, skip queuing
         return False
+    
+    # Check if we should auto-generate stories
+    _maybe_auto_generate(repo_path, queue_size)
+    
+    return True
+
+
+def _maybe_auto_generate(repo_path: Path, queue_size: int) -> None:
+    """Check if auto-generation should be triggered and spawn background process.
+    
+    Args:
+        repo_path: Path to repository root
+        queue_size: Current number of commits in queue
+    """
+    from .config import load_config
+    
+    config = load_config()
+    generation_config = config.get("generation", {})
+    
+    # Check if auto-generation is enabled
+    if not generation_config.get("auto_generate_on_hook", False):
+        return
+    
+    batch_size = generation_config.get("batch_size", 5)
+    
+    # Only trigger if queue size meets batch threshold
+    if queue_size < batch_size:
+        return
+    
+    # Spawn background generation process
+    _spawn_background_generate(repo_path)
+
+
+def _spawn_background_generate(repo_path: Path) -> None:
+    """Spawn a background process to generate stories for a repo.
+    
+    Uses subprocess.Popen with detached process to not block the git hook.
+    Logs to ~/.repr/logs/auto_generate.log
+    
+    Args:
+        repo_path: Path to repository to generate stories for
+    """
+    import subprocess
+    import sys
+    from .config import REPR_HOME
+    
+    # Ensure log directory exists
+    log_dir = REPR_HOME / "logs"
+    log_dir.mkdir(parents=True, exist_ok=True)
+    log_file = log_dir / "auto_generate.log"
+    
+    # Build command - use sys.executable to find repr command
+    # repr generate --repo <path> --local --json
+    cmd = [
+        sys.executable, "-m", "repr",
+        "generate",
+        "--repo", str(repo_path),
+        "--local",  # Always use local LLM for auto-generation
+        "--json",
+    ]
+    
+    try:
+        # Open log file for appending
+        with open(log_file, "a") as log:
+            log.write(f"\n[{datetime.now().isoformat()}] Auto-generating for {repo_path}\n")
+            log.flush()
+            
+            # Spawn detached background process
+            # On Unix, use start_new_session=True to fully detach
+            # On Windows, use DETACHED_PROCESS flag
+            if sys.platform == "win32":
+                DETACHED_PROCESS = 0x00000008
+                subprocess.Popen(
+                    cmd,
+                    stdout=log,
+                    stderr=log,
+                    creationflags=DETACHED_PROCESS,
+                    close_fds=True,
+                )
+            else:
+                subprocess.Popen(
+                    cmd,
+                    stdout=log,
+                    stderr=log,
+                    start_new_session=True,
+                    close_fds=True,
+                )
+    except Exception as e:
+        # Silently fail - don't block the git commit
+        try:
+            with open(log_file, "a") as log:
+                log.write(f"[{datetime.now().isoformat()}] Error spawning auto-generate: {e}\n")
+        except Exception:
+            pass
 
 
 def dequeue_commits(repo_path: Path, commit_shas: list[str]) -> int:

{repr_cli-0.2.11 → repr_cli-0.2.13}/repr/llm.py

@@ -538,6 +538,8 @@ def get_effective_llm_mode() -> tuple[str, dict[str, Any]]:
 
 
 
+
+
 
 
 

{repr_cli-0.2.11 → repr_cli-0.2.13}/repr/privacy.py

@@ -365,6 +365,8 @@ def clear_audit_log() -> int:
 
 
 
+
+
 
 
 

{repr_cli-0.2.11 → repr_cli-0.2.13}/repr/telemetry.py

@@ -311,6 +311,8 @@ def get_pending_events() -> list[dict[str, Any]]:
 
 
 
+
+
 
 
 

{repr_cli-0.2.11 → repr_cli-0.2.13}/repr/templates.py

@@ -9,103 +9,107 @@ Provides different prompts for generating stories based on use case:
 """
 
 from typing import Any
+from pydantic import BaseModel, Field
+
+
+class StoryOutput(BaseModel):
+    """Structured output for a generated story."""
+    summary: str = Field(description="One-line technical summary of the work (max 120 chars, no fluff)")
+    content: str = Field(description="Full technical description in markdown")
 
 
 # Template definitions
 TEMPLATES = {
     "resume": {
         "name": "Resume",
-        "description": "Professional accomplishment summaries for resumes and portfolios",
-        "system_prompt": """You are helping a developer document their work accomplishments for a professional resume or portfolio.
-
-Focus on:
-- Quantifiable impact where possible (performance improvements, user metrics, etc.)
-- Technical complexity and problem-solving
-- Leadership and collaboration
-- Technologies and skills demonstrated
-
-Write in first person, using action verbs. Keep it concise and impactful.
-Format: 2-3 bullet points per accomplishment, each 1-2 sentences.""",
-        "user_prompt_template": """Based on these commits, write professional accomplishment summaries:
+        "description": "Technical work log for resumes and portfolios",
+        "system_prompt": """Extract technical work from commits. Be direct and specific.
+
+Output JSON with:
+- summary: One line, max 120 chars. State what was done technically. No adjectives, no fluff.
+  Good: "Added JWT refresh token rotation with Redis session store"
+  Bad: "Enhanced authentication system with improved security"
+- content: Markdown with technical details. What was built, how, what tech.
+
+Rules:
+- Name specific technologies, libraries, patterns
+- Describe the implementation, not the benefit
+- No marketing language (enhanced, streamlined, robust, seamless)
+- No resume verbs (spearheaded, leveraged, drove)
+- If there's a metric, include it. If not, don't invent one.""",
+        "user_prompt_template": """Repository: {repo_name}
 
-Repository: {repo_name}
 Commits:
 {commits_summary}
 
-Generate 1-3 accomplishment summaries suitable for a resume.""",
+Output JSON with summary and content.""",
     },
     
     "changelog": {
         "name": "Changelog",
         "description": "Technical change documentation for release notes",
-        "system_prompt": """You are writing technical changelog entries for a software project.
+        "system_prompt": """Extract changes from commits for a changelog. Be specific.
+
+Output JSON with:
+- summary: One line describing the main change (max 120 chars)
+- content: Markdown changelog with categories (Added/Changed/Fixed/Removed)
+
+Rules:
+- List actual changes, not benefits
+- Include file/module names when relevant
+- No fluff words (improved, enhanced, better)""",
+        "user_prompt_template": """Repository: {repo_name}
 
-Focus on:
-- What changed (features, fixes, improvements)
-- Why it matters (user impact, developer experience)
-- Breaking changes or migration notes
-- Technical details relevant to other developers
-
-Use conventional changelog format with categories:
-- Added: New features
-- Changed: Changes to existing functionality
-- Fixed: Bug fixes
-- Removed: Removed features
-- Security: Security improvements""",
-        "user_prompt_template": """Generate changelog entries from these commits:
-
-Repository: {repo_name}
 Commits:
 {commits_summary}
 
-Write changelog entries grouped by category.""",
+Output JSON with summary and content.""",
     },
     
     "narrative": {
         "name": "Narrative",
-        "description": "Storytelling format for blogs or case studies",
-        "system_prompt": """You are helping a developer tell the story of their work in an engaging narrative format.
+        "description": "Technical narrative for blogs or case studies",
+        "system_prompt": """Write a technical narrative from commits.
+
+Output JSON with:
+- summary: One-line description of what was built (max 120 chars)
+- content: Markdown narrative explaining the technical work
 
 Focus on:
-- The challenge or problem being solved
-- The approach and decision-making process
-- Obstacles encountered and how they were overcome
-- Results and lessons learned
+- What problem was solved
+- How it was implemented technically
+- What decisions were made and why
 
-Write in a conversational, engaging tone suitable for a blog post or case study.
-Use present tense for engagement. Include technical details but make it accessible.""",
-        "user_prompt_template": """Tell the story of this development work:
+No marketing language. Write like you're explaining to another engineer.""",
+        "user_prompt_template": """Repository: {repo_name}
 
-Repository: {repo_name}
 Commits:
 {commits_summary}
 
-Write a narrative (2-3 paragraphs) that would work as a blog post section.""",
+Output JSON with summary and content.""",
     },
     
     "interview": {
         "name": "Interview Prep",
-        "description": "Behavioral interview preparation with STAR format",
-        "system_prompt": """You are helping a developer prepare for behavioral interviews using the STAR method.
+        "description": "Technical interview preparation",
+        "system_prompt": """Extract technical work for interview prep.
 
-Format each accomplishment as:
-- Situation: Context and background
-- Task: What needed to be done
-- Action: What you did specifically
-- Result: The outcome and impact
+Output JSON with:
+- summary: One-line technical summary (max 120 chars)
+- content: Markdown with situation/task/action/result format
 
 Focus on:
-- Technical decision-making
-- Problem-solving approach
-- Collaboration and communication
-- Quantifiable results""",
-        "user_prompt_template": """Create interview-ready stories from these commits:
+- Specific technical decisions made
+- Problems encountered and solutions
+- Technologies and patterns used
+
+No resume language. Be specific about what you actually did.""",
+        "user_prompt_template": """Repository: {repo_name}
 
-Repository: {repo_name}
 Commits:
 {commits_summary}
 
-Generate 1-2 STAR-format stories for behavioral interviews.""",
+Output JSON with summary and content.""",
     },
 }
 

{repr_cli-0.2.11 → repr_cli-0.2.13}/repr/ui.py

@@ -177,6 +177,8 @@ def confirm(message: str, default: bool = False) -> bool:
 
 
 
+
+
 
 
 

{repr_cli-0.2.11 → repr_cli-0.2.13}/repr/updater.py

@@ -277,6 +277,8 @@ def perform_update(force: bool = False) -> bool:
 
 
 
+
+
 
 
 

{repr_cli-0.2.11 → repr_cli-0.2.13/repr_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: repr-cli
-Version: 0.2.11
+Version: 0.2.13
 Summary: A beautiful, privacy-first CLI that analyzes your code repositories and generates a compelling developer profile
 Author-email: Repr <hello@repr.dev>
 License: MIT License

{repr_cli-0.2.11 → repr_cli-0.2.13}/setup.py

@@ -39,6 +39,8 @@ if __name__ == "__main__":
 
 
 
+
+