gobby 0.2.6__py3-none-any.whl → 0.2.7__py3-none-any.whl

gobby/install/claude/commands/gobby/bug.md

@@ -1,51 +0,0 @@
----
-name: bug
-description: Quickly create a bug task. Usage: /bug <title> [description]
----
-
-# /bug - Create Bug Task
-
-Create a bug/defect task with the provided title and optional description.
-
-## Usage
-
-```text
-/bug <title>
-/bug <title> - <description>
-```
-
-## Examples
-
-```text
-/bug Fix login timeout
-/bug Database connection drops - Users report intermittent connection failures after 5 minutes of inactivity
-```
-
-## Action
-
-Call `gobby-tasks.create_task` with:
-
-- `title`: The bug title from user input
-- `task_type`: "bug"
-- `priority`: 1 (high - bugs are important)
-
-Parse the user input:
-
-- If input contains " - ", split into title and description
-- Otherwise, use entire input as title
-
-```python
-call_tool(
-    server_name="gobby-tasks",
-    tool_name="create_task",
-    arguments={
-        "title": "<parsed title>",
-        "description": "<parsed description if any>",
-        "task_type": "bug",
-        "priority": 1,
-        "session_id": "<session_id>"  # Required - from session context
-    }
-)
-```
-
-After creating, confirm with the task reference (e.g., "Created bug #123: Fix login timeout").

gobby/install/claude/commands/gobby/chore.md

@@ -1,51 +0,0 @@
----
-name: chore
-description: Quickly create a chore/maintenance task. Usage: /chore <title> [description]
----
-
-# /chore - Create Chore Task
-
-Create a maintenance or housekeeping task with the provided title and optional description. For tasks that keep the codebase healthy but aren't features or bugs.
-
-## Usage
-
-```
-/chore <title>
-/chore <title> - <description>
-```
-
-## Examples
-
-```
-/chore Update dependencies
-/chore Clean up CI pipeline - Remove deprecated jobs and consolidate test stages
-/chore Add missing type hints to utils module
-/chore Rotate API keys
-```
-
-## Action
-
-Call `gobby-tasks.create_task` with:
-- `title`: The chore title from user input
-- `task_type`: "chore"
-- `priority`: 3 (low - maintenance tasks are important but rarely urgent)
-
-Parse the user input:
-- If input contains " - ", split into title and description
-- Otherwise, use entire input as title
-
-```python
-call_tool(
-    server_name="gobby-tasks",
-    tool_name="create_task",
-    arguments={
-        "title": "<parsed title>",
-        "description": "<parsed description if any>",
-        "task_type": "chore",
-        "priority": 3,
-        "session_id": "<session_id>"  # Required - from session context
-    }
-)
-```
-
-After creating, confirm with the task reference (e.g., "Created chore #128: Update dependencies").

gobby/install/claude/commands/gobby/epic.md

@@ -1,52 +0,0 @@
----
-name: epic
-description: Quickly create an epic (parent task for large features). Usage: /epic <title> [description]
----
-
-# /epic - Create Epic Task
-
-Create an epic task - a parent container for a large feature or initiative that will be broken down into subtasks.
-
-## Usage
-
-```
-/epic <title>
-/epic <title> - <description>
-```
-
-## Examples
-
-```
-/epic User authentication system
-/epic API v2 migration - Migrate all endpoints from REST to GraphQL with backwards compatibility
-/epic Performance optimization sprint
-```
-
-## Action
-
-Call `gobby-tasks.create_task` with:
-- `title`: The epic title from user input
-- `task_type`: "epic"
-- `priority`: 2 (medium - epics are tracked but individual subtasks drive priority)
-
-Parse the user input:
-- If input contains " - ", split into title and description
-- Otherwise, use entire input as title
-
-```python
-call_tool(
-    server_name="gobby-tasks",
-    tool_name="create_task",
-    arguments={
-        "title": "<parsed title>",
-        "description": "<parsed description if any>",
-        "task_type": "epic",
-        "priority": 2,
-        "session_id": "<session_id>"  # Required - from session context
-    }
-)
-```
-
-After creating, confirm with the task reference and suggest next steps:
-- "Created epic #127: User authentication system"
-- "Use `expand_task` to break this down into subtasks."

gobby/install/claude/commands/gobby/eval.md

@@ -1,235 +0,0 @@
----
-name: eval
-description: This skill should be used when the user asks to "evaluate agent performance", "build test framework", "measure agent quality", "create evaluation rubrics", or mentions LLM-as-judge, multi-dimensional evaluation, agent testing, or quality gates for agent pipelines.
----
-
-# Evaluation Methods for Agent Systems
-
-Evaluation of agent systems requires different approaches than traditional software or even standard language model applications. Agents make dynamic decisions, are non-deterministic between runs, and often lack single correct answers. Effective evaluation must account for these characteristics while providing actionable feedback. A robust evaluation framework enables continuous improvement, catches regressions, and validates that context engineering choices achieve intended effects.
-
-## When to Activate
-
-Activate this skill when:
-
-- Testing agent performance systematically
-- Validating context engineering choices
-- Measuring improvements over time
-- Catching regressions before deployment
-- Building quality gates for agent pipelines
-- Comparing different agent configurations
-- Evaluating production systems continuously
-
-## Core Concepts
-
-Agent evaluation requires outcome-focused approaches that account for non-determinism and multiple valid paths. Multi-dimensional rubrics capture various quality aspects: factual accuracy, completeness, citation accuracy, source quality, and tool efficiency. LLM-as-judge provides scalable evaluation while human evaluation catches edge cases.
-
-The key insight is that agents may find alternative paths to goals—the evaluation should judge whether they achieve right outcomes while following reasonable processes.
-
-**Performance Drivers: The 95% Finding**
-Research on the BrowseComp evaluation (which tests browsing agents' ability to locate hard-to-find information) found that three factors explain 95% of performance variance:
-
-| Factor | Variance Explained | Implication |
-| :--- | :--- | :--- |
-| Token usage | 80% | More tokens = better performance |
-| Number of tool calls | ~10% | More exploration helps |
-| Model choice | ~5% | Better models multiply efficiency |
-
-This finding has significant implications for evaluation design:
-
-- **Token budgets matter**: Evaluate agents with realistic token budgets, not unlimited resources
-- **Model upgrades beat token increases**: Upgrading to Claude Sonnet 4.5 or GPT-5.2 provides larger gains than doubling token budgets on previous versions
-- **Multi-agent validation**: The finding validates architectures that distribute work across agents with separate context windows
-
-## Detailed Topics
-
-### Evaluation Challenges
-
-**Non-Determinism and Multiple Valid Paths**
-Agents may take completely different valid paths to reach goals. One agent might search three sources while another searches ten. They might use different tools to find the same answer. Traditional evaluations that check for specific steps fail in this context.
-
-The solution is outcome-focused evaluation that judges whether agents achieve right outcomes while following reasonable processes.
-
-**Context-Dependent Failures**
-Agent failures often depend on context in subtle ways. An agent might succeed on simple queries but fail on complex ones. It might work well with one tool set but fail with another. Failures may emerge only after extended interaction when context accumulates.
-
-Evaluation must cover a range of complexity levels and test extended interactions, not just isolated queries.
-
-**Composite Quality Dimensions**
-Agent quality is not a single dimension. It includes factual accuracy, completeness, coherence, tool efficiency, and process quality. An agent might score high on accuracy but low in efficiency, or vice versa.
-
-Evaluation rubrics must capture multiple dimensions with appropriate weighting for the use case.
-
-### Evaluation Rubric Design
-
-**Multi-Dimensional Rubric**
-Effective rubrics cover key dimensions with descriptive levels:
-
-Factual accuracy: Claims match ground truth (excellent to failed)
-
-Completeness: Output covers requested aspects (excellent to failed)
-
-Citation accuracy: Citations match claimed sources (excellent to failed)
-
-Source quality: Uses appropriate primary sources (excellent to failed)
-
-Tool efficiency: Uses right tools reasonable number of times (excellent to failed)
-
-**Rubric Scoring**
-Convert dimension assessments to numeric scores (0.0 to 1.0) with appropriate weighting. Calculate weighted overall scores. Determine passing threshold based on use case requirements.
-
-### Evaluation Methodologies
-
-**LLM-as-Judge**
-LLM-based evaluation scales to large test sets and provides consistent judgments. The key is designing effective evaluation prompts that capture the dimensions of interest.
-
-Provide clear task description, agent output, ground truth (if available), evaluation scale with level descriptions, and request structured judgment.
-
-**Human Evaluation**
-Human evaluation catches what automation misses. Humans notice hallucinated answers on unusual queries, system failures, and subtle biases that automated evaluation misses.
-
-Effective human evaluation covers edge cases, samples systematically, tracks patterns, and provides contextual understanding.
-
-**End-State Evaluation**
-For agents that mutate persistent state, end-state evaluation focuses on whether the final state matches expectations rather than how the agent got there.
-
-### Test Set Design
-
-**Sample Selection**
-Start with small samples during development. Early in agent development, changes have dramatic impacts because there is abundant low-hanging fruit. Small test sets reveal large effects.
-
-Sample from real usage patterns. Add known edge cases. Ensure coverage across complexity levels.
-
-**Complexity Stratification**
-Test sets should span complexity levels: simple (single tool call), medium (multiple tool calls), complex (many tool calls, significant ambiguity), and very complex (extended interaction, deep reasoning).
-
-### Context Engineering Evaluation
-
-**Testing Context Strategies**
-Context engineering choices should be validated through systematic evaluation. Run agents with different context strategies on the same test set. Compare quality scores, token usage, and efficiency metrics.
-
-**Degradation Testing**
-Test how context degradation affects performance by running agents at different context sizes. Identify performance cliffs where context becomes problematic. Establish safe operating limits.
-
-### Continuous Evaluation
-
-**Evaluation Pipeline**
-Build evaluation pipelines that run automatically on agent changes. Track results over time. Compare versions to identify improvements or regressions.
-
-**Monitoring Production**
-Track evaluation metrics in production by sampling interactions and evaluating randomly. Set alerts for quality drops. Maintain dashboards for trend analysis.
-
-## Practical Guidance
-
-### Building Evaluation Frameworks
-
-1. Define quality dimensions relevant to your use case
-2. Create rubrics with clear, actionable level descriptions
-3. Build test sets from real usage patterns and edge cases
-4. Implement automated evaluation pipelines
-5. Establish baseline metrics before making changes
-6. Run evaluations on all significant changes
-7. Track metrics over time for trend analysis
-8. Supplement automated evaluation with human review
-
-### Avoiding Evaluation Pitfalls
-
-Overfitting to specific paths: Evaluate outcomes, not specific steps.
-Ignoring edge cases: Include diverse test scenarios.
-Single-metric obsession: Use multi-dimensional rubrics.
-Neglecting context effects: Test with realistic context sizes.
-Skipping human evaluation: Automated evaluation misses subtle issues.
-
-## Examples
-
-### Example 1: Simple Evaluation
-
-```python
-def evaluate_agent_response(response, expected):
-    rubric = load_rubric()
-    scores = {}
-    for dimension, config in rubric.items():
-        scores[dimension] = assess_dimension(response, expected, dimension)
-    overall = weighted_average(scores, config["weights"])
-    return {"passed": overall >= 0.7, "scores": scores}
-```
-
-### Example 2: Test Set Structure
-
-Test sets should span multiple complexity levels to ensure comprehensive evaluation:
-
-```python
-test_set = [
-    {
-        "name": "simple_lookup",
-        "input": "What is the capital of France?",
-        "expected": {"type": "fact", "answer": "Paris"},
-        "complexity": "simple",
-        "description": "Single tool call, factual lookup"
-    },
-    {
-        "name": "medium_query",
-        "input": "Compare the revenue of Apple and Microsoft last quarter",
-        "complexity": "medium",
-        "description": "Multiple tool calls, comparison logic"
-    },
-    {
-        "name": "multi_step_reasoning",
-        "input": "Analyze sales data from Q1-Q4 and create a summary report with trends",
-        "complexity": "complex",
-        "description": "Many tool calls, aggregation, analysis"
-    },
-    {
-        "name": "research_synthesis",
-        "input": "Research emerging AI technologies, evaluate their potential impact, and recommend adoption strategy",
-        "complexity": "very_complex",
-        "description": "Extended interaction, deep reasoning, synthesis"
-    }
-]
-```
-
-## Guidelines
-
-1. Use multi-dimensional rubrics, not single metrics
-2. Evaluate outcomes, not specific execution paths
-3. Cover complexity levels from simple to complex
-4. Test with realistic context sizes and histories
-5. Run evaluations continuously, not just before release
-6. Supplement LLM evaluation with human review
-7. Track metrics over time for trend detection
-8. Set clear pass/fail thresholds based on use case
-
-## Integration
-
-This skill connects to all other skills as a cross-cutting concern:
-
-- context-fundamentals - Evaluating context usage
-- context-degradation - Detecting degradation
-- context-optimization - Measuring optimization effectiveness
-- multi-agent-patterns - Evaluating coordination
-- tool-design - Evaluating tool effectiveness
-- memory-systems - Evaluating memory quality
-
-## References
-
-Internal reference:
-
-- [Metrics Reference](./references/metrics.md) - Detailed evaluation metrics and implementation
-
-Internal skills:
-
-- All other skills connect to evaluation for quality measurement
-
-External resources:
-
-- LLM evaluation benchmarks
-- Agent evaluation research papers
-- Production monitoring practices
-
----
-
-## Skill Metadata
-
-**Created**: 2025-12-20
-**Last Updated**: 2025-12-20
-**Author**: Agent Skills for Context Engineering Contributors
-**Version**: 1.0.0

gobby/install/claude/commands/gobby/feat.md

@@ -1,49 +0,0 @@
----
-name: feat
-description: Quickly create a feature task. Usage: /feat <title> [description]
----
-
-# /feat - Create Feature Task
-
-Create a new feature task with the provided title and optional description.
-
-## Usage
-
-```
-/feat <title>
-/feat <title> - <description>
-```
-
-## Examples
-
-```
-/feat Add dark mode toggle
-/feat User profile avatars - Allow users to upload custom profile pictures with cropping support
-```
-
-## Action
-
-Call `gobby-tasks.create_task` with:
-- `title`: The feature title from user input
-- `task_type`: "feature"
-- `priority`: 2 (medium - standard priority for new features)
-
-Parse the user input:
-- If input contains " - ", split into title and description
-- Otherwise, use entire input as title
-
-```python
-call_tool(
-    server_name="gobby-tasks",
-    tool_name="create_task",
-    arguments={
-        "title": "<parsed title>",
-        "description": "<parsed description if any>",
-        "task_type": "feature",
-        "priority": 2,
-        "session_id": "<session_id>"  # Required - from session context
-    }
-)
-```
-
-After creating, confirm with the task reference (e.g., "Created feature #124: Add dark mode toggle").

gobby/install/claude/commands/gobby/nit.md

@@ -1,52 +0,0 @@
----
-name: nit
-description: Quickly create a nitpick/minor cleanup task. Usage: /nit <title> [description]
----
-
-# /nit - Create Nitpick Task
-
-Create a minor cleanup or nitpick task with the provided title and optional description. These are small improvements that don't warrant a full feature or bug.
-
-## Usage
-
-```
-/nit <title>
-/nit <title> - <description>
-```
-
-## Examples
-
-```
-/nit Rename confusing variable
-/nit Fix typo in error message - "authentification" should be "authentication"
-/nit Remove unused import in utils.py
-```
-
-## Action
-
-Call `gobby-tasks.create_task` with:
-- `title`: The nitpick title from user input
-- `task_type`: "chore"
-- `labels`: ["nitpick"]
-- `priority`: 4 (backlog - low priority, do when convenient)
-
-Parse the user input:
-- If input contains " - ", split into title and description
-- Otherwise, use entire input as title
-
-```python
-call_tool(
-    server_name="gobby-tasks",
-    tool_name="create_task",
-    arguments={
-        "title": "<parsed title>",
-        "description": "<parsed description if any>",
-        "task_type": "chore",
-        "labels": ["nitpick"],
-        "priority": 4,
-        "session_id": "<session_id>"  # Required - from session context
-    }
-)
-```
-
-After creating, confirm with the task reference (e.g., "Created nitpick #125: Rename confusing variable").

gobby/install/claude/commands/gobby/ref.md

@@ -1,52 +0,0 @@
----
-name: ref
-description: Quickly create a refactoring task. Usage: /ref <title> [description]
----
-
-# /ref - Create Refactoring Task
-
-Create a refactoring task with the provided title and optional description. For code improvements that don't change behavior.
-
-## Usage
-
-```
-/ref <title>
-/ref <title> - <description>
-```
-
-## Examples
-
-```
-/ref Extract database logic into repository class
-/ref Simplify authentication middleware - Current implementation has too many nested conditionals
-/ref Convert callbacks to async/await in file handlers
-```
-
-## Action
-
-Call `gobby-tasks.create_task` with:
-- `title`: The refactoring title from user input
-- `task_type`: "chore"
-- `labels`: ["refactor"]
-- `priority`: 3 (low - important but not urgent)
-
-Parse the user input:
-- If input contains " - ", split into title and description
-- Otherwise, use entire input as title
-
-```python
-call_tool(
-    server_name="gobby-tasks",
-    tool_name="create_task",
-    arguments={
-        "title": "<parsed title>",
-        "description": "<parsed description if any>",
-        "task_type": "chore",
-        "labels": ["refactor"],
-        "priority": 3,
-        "session_id": "<session_id>"  # Required - from session context
-    }
-)
-```
-
-After creating, confirm with the task reference (e.g., "Created refactor #126: Extract database logic into repository class").