repr-cli 0.2.9__tar.gz → 0.2.12__tar.gz

{repr_cli-0.2.9/repr_cli.egg-info → repr_cli-0.2.12}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: repr-cli
-Version: 0.2.9
+Version: 0.2.12
 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
@@ -48,6 +48,7 @@ Requires-Dist: pygments>=2.16.0
 Requires-Dist: httpx>=0.25.0
 Requires-Dist: openai>=1.0.0
 Requires-Dist: keyring>=24.0.0
+Requires-Dist: pydantic>=2.0.0
 Provides-Extra: dev
 Requires-Dist: pytest>=7.0.0; extra == "dev"
 Requires-Dist: pytest-asyncio>=0.21.0; extra == "dev"

{repr_cli-0.2.9 → repr_cli-0.2.12}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "repr-cli"
-version = "0.2.9"
+version = "0.2.12"
 description = "A beautiful, privacy-first CLI that analyzes your code repositories and generates a compelling developer profile"
 readme = "README.md"
 license = {file = "LICENSE"}
@@ -32,6 +32,7 @@ dependencies = [
     "httpx>=0.25.0",
     "openai>=1.0.0",
     "keyring>=24.0.0",
+    "pydantic>=2.0.0",
 ]
 
 [project.optional-dependencies]

{repr_cli-0.2.9 → repr_cli-0.2.12}/repr/__main__.py

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

{repr_cli-0.2.9 → repr_cli-0.2.12}/repr/cli.py

@@ -610,7 +610,7 @@ async def _generate_stories_async(
 ) -> list[dict]:
     """Generate stories from commits using LLM (async implementation)."""
     from .openai_analysis import get_openai_client, extract_commit_batch
-    from .templates import build_generation_prompt
+    from .templates import build_generation_prompt, StoryOutput
     
     stories = []
     
@@ -643,8 +643,8 @@ async def _generate_stories_async(
                     custom_prompt=custom_prompt,
                 )
                 
-                # Extract story from batch
-                content = await extract_commit_batch(
+                # Extract story from batch using structured output
+                result = await extract_commit_batch(
                     client=client,
                     commits=batch,
                     batch_num=i + 1,
@@ -652,44 +652,60 @@ async def _generate_stories_async(
                     model=model,
                     system_prompt=system_prompt,
                     user_prompt=user_prompt,
+                    structured=True,
                 )
                 
-                if not content or content.startswith("[Batch"):
-                    continue
-                
-                # Extract summary (first non-empty line)
-                lines = [l.strip() for l in content.split("\n") if l.strip()]
-                summary = lines[0][:100] if lines else "Story"
-                # Clean up summary
-                summary = summary.lstrip("#-•* ").strip()
-                
-                # Build metadata
+                # Handle structured output - now returns list[StoryOutput]
+                story_outputs: list[StoryOutput] = []
+                if isinstance(result, list):
+                    story_outputs = result
+                elif isinstance(result, StoryOutput):
+                    story_outputs = [result]
+                else:
+                    # Fallback for string response
+                    content = result
+                    if not content or content.startswith("[Batch"):
+                        continue
+                    lines = [l.strip() for l in content.split("\n") if l.strip()]
+                    summary = lines[0] if lines else "Story"
+                    summary = summary.lstrip("#-•* ").strip()
+                    story_outputs = [StoryOutput(summary=summary, content=content)]
+
+                # Build shared metadata for all stories from this batch
                 commit_shas = [c["full_sha"] for c in batch]
                 first_date = min(c["date"] for c in batch)
                 last_date = max(c["date"] for c in batch)
                 total_files = sum(len(c.get("files", [])) for c in batch)
                 total_adds = sum(c.get("insertions", 0) for c in batch)
                 total_dels = sum(c.get("deletions", 0) for c in batch)
-                
-                metadata = {
-                    "summary": summary,
-                    "repo_name": repo_info.name,
-                    "repo_path": str(repo_info.path),
-                    "commit_shas": commit_shas,
-                    "first_commit_at": first_date,
-                    "last_commit_at": last_date,
-                    "files_changed": total_files,
-                    "lines_added": total_adds,
-                    "lines_removed": total_dels,
-                    "generated_locally": local,
-                    "template": template,
-                    "needs_review": False,
-                }
-                
-                # Save story
-                story_id = save_story(content, metadata)
-                metadata["id"] = story_id
-                stories.append(metadata)
+
+                # Save each story from this batch
+                for story_output in story_outputs:
+                    content = story_output.content
+                    summary = story_output.summary
+
+                    if not content or content.startswith("[Batch"):
+                        continue
+
+                    metadata = {
+                        "summary": summary,
+                        "repo_name": repo_info.name,
+                        "repo_path": str(repo_info.path),
+                        "commit_shas": commit_shas,
+                        "first_commit_at": first_date,
+                        "last_commit_at": last_date,
+                        "files_changed": total_files,
+                        "lines_added": total_adds,
+                        "lines_removed": total_dels,
+                        "generated_locally": local,
+                        "template": template,
+                        "needs_review": False,
+                    }
+
+                    # Save story
+                    story_id = save_story(content, metadata)
+                    metadata["id"] = story_id
+                    stories.append(metadata)
                 
             except Exception as e:
                 console.print(f"  [{BRAND_MUTED}]Batch {i+1} failed: {e}[/]")
@@ -788,7 +804,8 @@ def stories(
 @app.command()
 def story(
     action: str = typer.Argument(..., help="Action: view, edit, delete, hide, feature, regenerate"),
-    story_id: str = typer.Argument(..., help="Story ID (ULID)"),
+    story_id: Optional[str] = typer.Argument(None, help="Story ID (ULID)"),
+    all_stories: bool = typer.Option(False, "--all", help="Apply to all stories (for delete)"),
 ):
     """
     Manage a single story.
@@ -796,7 +813,38 @@ def story(
     Examples:
         repr story view 01ARYZ6S41TSV4RRFFQ69G5FAV
         repr story delete 01ARYZ6S41TSV4RRFFQ69G5FAV
+        repr story delete --all
     """
+    # Handle --all flag for delete
+    if all_stories:
+        if action != "delete":
+            print_error("--all flag only works with 'delete' action")
+            raise typer.Exit(1)
+        
+        story_list = list_stories()
+        if not story_list:
+            print_info("No stories to delete")
+            raise typer.Exit()
+        
+        console.print(f"This will delete [bold]{len(story_list)}[/] stories.")
+        if confirm("Delete all stories?"):
+            deleted = 0
+            for s in story_list:
+                try:
+                    delete_story(s["id"])
+                    deleted += 1
+                except Exception:
+                    pass
+            print_success(f"Deleted {deleted} stories")
+        else:
+            print_info("Cancelled")
+        raise typer.Exit()
+    
+    # Require story_id for single-story operations
+    if not story_id:
+        print_error("Story ID required (or use --all for delete)")
+        raise typer.Exit(1)
+    
     result = load_story(story_id)
     
     if not result:
@@ -1000,7 +1048,9 @@ def push(
     for s in to_push:
         try:
             content, meta = load_story(s["id"])
-            asyncio.run(api_push_story({**meta, "content": content}))
+            # Use local story ID as client_id for sync
+            payload = {**meta, "content": content, "client_id": s["id"]}
+            asyncio.run(api_push_story(payload))
             mark_story_pushed(s["id"])
             console.print(f"  [{BRAND_SUCCESS}]✓[/] {s.get('summary', s.get('id'))[:50]}")
             pushed += 1
@@ -1049,7 +1099,8 @@ def sync():
             for s in unpushed:
                 try:
                     content, meta = load_story(s["id"])
-                    asyncio.run(api_push_story({**meta, "content": content}))
+                    payload = {**meta, "content": content, "client_id": s["id"]}
+                    asyncio.run(api_push_story(payload))
                     mark_story_pushed(s["id"])
                 except Exception:
                     pass

{repr_cli-0.2.9 → repr_cli-0.2.12}/repr/doctor.py

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

{repr_cli-0.2.9 → repr_cli-0.2.12}/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.9 → repr_cli-0.2.12}/repr/llm.py

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

{repr_cli-0.2.9 → repr_cli-0.2.12}/repr/openai_analysis.py

@@ -11,10 +11,23 @@ import asyncio
 from typing import Any
 
 from openai import AsyncOpenAI
+from pydantic import BaseModel, Field
 
 from .tools import get_commits_with_diffs
 from .discovery import RepoInfo
 from .config import get_litellm_config, get_llm_config, get_api_base
+from .templates import StoryOutput
+
+
+class ExtractedStory(BaseModel):
+    """A single coherent block of work."""
+    title: str = Field(description="One-line title, max 120 chars. Dev jargon welcome. e.g. 'Wire up Redis caching for auth tokens'")
+    summary: str = Field(description="Markdown - what was built, how it works, why it matters")
+
+
+class ExtractedCommitBatch(BaseModel):
+    """Schema for extraction phase output - one or more stories from a batch of commits."""
+    stories: list[ExtractedStory] = Field(description="List of distinct blocks of work found in the commits")
 
 
 # Model configuration (defaults for OpenAI)
@@ -124,10 +137,11 @@ async def extract_commit_batch(
     model: str = None,
     system_prompt: str = None,
     user_prompt: str = None,
-) -> str:
+    structured: bool = False,
+) -> str | list[StoryOutput]:
     """
     Extraction phase: Extract accomplishments from a batch of commits.
-    
+
     Args:
         client: OpenAI client
         commits: List of commits with diffs
@@ -136,9 +150,10 @@ async def extract_commit_batch(
         model: Model name to use (defaults to stored config or DEFAULT_EXTRACTION_MODEL)
         system_prompt: Custom system prompt (optional, uses default if not provided)
         user_prompt: Custom user prompt (optional, uses default if not provided)
-    
+        structured: If True, return list of StoryOutput with summary/content fields
+
     Returns:
-        Summary of technical accomplishments in this batch
+        Summary of technical accomplishments (str) or list[StoryOutput] if structured=True
     """
     if not model:
         llm_config = get_llm_config()
@@ -176,60 +191,81 @@ Files changed:"""
         commits_formatted = "\n\n---\n".join(commits_text)
         
         if not system_prompt:
-            system_prompt = """You are analyzing a developer's actual code commits to extract specific technical accomplishments WITH the reasoning behind them.
-
-Your job: Read the commit messages and diffs, then list CONCRETE technical accomplishments with SPECIFIC details AND infer WHY those decisions were made.
-
-For each accomplishment, capture:
-1. WHAT was built (the technical implementation)
-2. WHY it was needed (the problem being solved, the user/business need, or the technical constraint)
-
-Rules:
-- Use EXACT technology names from the code (FastAPI, React, SQLAlchemy, not "web framework")
-- Describe SPECIFIC features built (e.g., "JWT authentication with refresh tokens", not "auth system")
-- INFER the motivation when possible:
-  - Performance changes → what latency/throughput problem was being solved?
-  - New features → what user capability was being enabled?
-  - Refactors → what maintainability or scalability issue was being addressed?
-  - Error handling → what failure mode was being prevented?
-- Mention architectural patterns when evident (microservices, event-driven, REST API, etc.)
-- Include scale indicators (number of endpoints, integrations, etc.)
-- Be concise but specific - bullet points are fine
-
-What NOT to do:
-- Don't write vague statements like "worked on backend"
-- Don't guess technologies not shown in the diffs
-- Don't include process/methodology unless there's evidence
-- Don't fabricate motivations that aren't supported by the code/commits"""
+            system_prompt = """Read the commits and diffs. Understand what the dev actually shipped.
 
-        if not user_prompt:
-            user_prompt = f"""Analyze commits batch {batch_num}/{total_batches} and extract technical accomplishments:
+Write it up like one dev explaining to another what got done. Use real dev jargon - talk about wiring up endpoints, spinning up services, hooking into APIs, plumbing data through, etc.
 
-{commits_formatted}
+Group related commits into one story. Split unrelated work into separate stories.
 
-List the specific technical work done in this batch. For each item:
-1. What was BUILT (the concrete implementation)
-2. Why it was needed (infer from context: what problem was solved? what user need? what constraint?)
+Per story:
+- title: One punchy line, max 120 chars. Say what was built. Tech details when relevant.
+  Good: "Wire up WebSocket streaming for chat responses"
+  Good: "Plumb user prefs through to the settings modal"
+  Good: "Fix race condition in token refresh flow"
+  Bad: "Improved authentication system" (too vague)
+  Bad: "Enhanced user experience" (meaningless)
+- summary: Markdown. What was built, how it works, any interesting decisions.
 
-Focus on substance, not process."""
+No corporate fluff. No "enhanced", "improved", "robust". Just say what happened."""
+
+        if not user_prompt:
+            user_prompt = f"""Commits batch {batch_num}/{total_batches}:
+
+{commits_formatted}"""
 
     try:
-        response = await client.chat.completions.create(
-            model=model,
-            messages=[
-                {"role": "system", "content": system_prompt},
-                {"role": "user", "content": user_prompt},
-            ],
-            temperature=EXTRACTION_TEMPERATURE,
-            max_tokens=16000,  # Increased for reasoning models that use tokens for thinking
-        )
-        
-        return response.choices[0].message.content or ""
+        if structured:
+            # Use structured output with Pydantic model
+            response = await client.beta.chat.completions.parse(
+                model=model,
+                messages=[
+                    {"role": "system", "content": system_prompt},
+                    {"role": "user", "content": user_prompt},
+                ],
+                temperature=EXTRACTION_TEMPERATURE,
+                max_tokens=16000,
+                response_format=ExtractedCommitBatch,
+            )
+
+            parsed = response.choices[0].message.parsed
+            if parsed and parsed.stories:
+                # Convert each story to StoryOutput
+                return [
+                    StoryOutput(summary=story.title, content=story.summary)
+                    for story in parsed.stories
+                ]
+            # Fallback if parsing failed (e.g., refusal)
+            content = response.choices[0].message.content or ""
+            return [
+                StoryOutput(
+                    summary=f"Batch {batch_num} analysis",
+                    content=content if content else "[No content extracted]",
+                )
+            ]
+        else:
+            response = await client.chat.completions.create(
+                model=model,
+                messages=[
+                    {"role": "system", "content": system_prompt},
+                    {"role": "user", "content": user_prompt},
+                ],
+                temperature=EXTRACTION_TEMPERATURE,
+                max_tokens=16000,
+            )
+            
+            return response.choices[0].message.content or ""
     except Exception as e:
         error_msg = str(e).lower()
         # Handle content moderation blocks gracefully
         if "blocked" in error_msg or "content" in error_msg or "moderation" in error_msg:
             # Skip this batch but continue with others
+            if structured:
+                return [
+                    StoryOutput(
+                        summary=f"Batch {batch_num} skipped",
+                        content=f"[Batch {batch_num} skipped - content filter triggered]",
+                    )
+                ]
             return f"[Batch {batch_num} skipped - content filter triggered]"
         # Re-raise other errors
         raise

{repr_cli-0.2.9 → repr_cli-0.2.12}/repr/privacy.py

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

{repr_cli-0.2.9 → repr_cli-0.2.12}/repr/telemetry.py

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

{repr_cli-0.2.9 → repr_cli-0.2.12}/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.9 → repr_cli-0.2.12}/repr/ui.py

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

{repr_cli-0.2.9 → repr_cli-0.2.12}/repr/updater.py

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

{repr_cli-0.2.9 → repr_cli-0.2.12/repr_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: repr-cli
-Version: 0.2.9
+Version: 0.2.12
 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
@@ -48,6 +48,7 @@ Requires-Dist: pygments>=2.16.0
 Requires-Dist: httpx>=0.25.0
 Requires-Dist: openai>=1.0.0
 Requires-Dist: keyring>=24.0.0
+Requires-Dist: pydantic>=2.0.0
 Provides-Extra: dev
 Requires-Dist: pytest>=7.0.0; extra == "dev"
 Requires-Dist: pytest-asyncio>=0.21.0; extra == "dev"

{repr_cli-0.2.9 → repr_cli-0.2.12}/repr_cli.egg-info/requires.txt

@@ -5,6 +5,7 @@ pygments>=2.16.0
 httpx>=0.25.0
 openai>=1.0.0
 keyring>=24.0.0
+pydantic>=2.0.0
 
 [dev]
 pytest>=7.0.0

{repr_cli-0.2.9 → repr_cli-0.2.12}/setup.py

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