steerdev 0.4.27__py3-none-any.whl

steerdev_agent/setup/templates/settings.json

@@ -0,0 +1,69 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(steerdev tasks:*)",
+      "Bash(steerdev specs:*)",
+      "Bash(steerdev context:*)",
+      "Bash(steerdev activity:*)",
+      "Bash(steerdev git:*)",
+      "Bash(steerdev hooks:*)",
+      "Bash(git checkout:*)",
+      "Bash(git branch:*)",
+      "Bash(git add:*)",
+      "Bash(git commit:*)",
+      "Bash(git push:*)",
+      "Bash(git status:*)",
+      "Bash(git diff:*)",
+      "Bash(git log:*)",
+      "Bash(gh pr create:*)",
+      "Bash(gh pr view:*)",
+      "Bash(gh pr list:*)"
+    ]
+  },
+  "hooks": {
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "steerdev hooks session-start",
+            "timeout": 10
+          }
+        ]
+      }
+    ],
+    "SessionEnd": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "steerdev hooks session-end",
+            "timeout": 10
+          }
+        ]
+      }
+    ],
+    "Stop": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "steerdev hooks agent-stop",
+            "timeout": 10
+          }
+        ]
+      }
+    ],
+    "SubagentStop": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "steerdev hooks subagent-stop",
+            "timeout": 10
+          }
+        ]
+      }
+    ]
+  }
+}

steerdev_agent/setup/templates/skills/activity/SKILL.md

@@ -0,0 +1,160 @@
+# Activity Skill
+
+This skill enables self-reporting of progress, blockers, and querying activity history via the steerdev.com API.
+
+Activity reporting provides visibility into agent work and enables better coordination and debugging.
+
+## Event Types
+
+| Type | Description | When to Use |
+|------|-------------|-------------|
+| `progress` | Progress update | Report incremental progress on a task |
+| `blocker` | Blocked on something | Report when stuck or waiting |
+| `question` | Need clarification | Report questions about requirements |
+| `milestone` | Reached a milestone | Report significant achievements |
+| `error` | Encountered an error | Report errors during execution |
+| `warning` | Warning/heads-up | Report potential issues |
+| `info` | General information | Report general updates |
+
+## When to Use
+
+- **Making progress**: Report progress updates periodically
+- **Encountering blockers**: Report blockers that prevent progress
+- **Need clarification**: Report questions about requirements or approach
+- **Completing milestones**: Report when significant milestones are reached
+- **Debugging issues**: Query activity history to understand what happened
+
+## Available Commands
+
+### Report Activity
+
+```bash
+steerdev activity report --type TYPE --message "MESSAGE" [OPTIONS]
+```
+
+Self-report progress, blockers, or other activity events.
+
+**Options:**
+- `--type`, `-t`: Event type (required) - `progress`, `blocker`, `question`, `milestone`, `error`, `warning`, `info`
+- `--message`, `-m`: Human-readable message (required)
+- `--metadata`: Additional metadata as JSON string
+- `--run-id`, `-r`: Run ID to associate with
+- `--session`, `-s`: Session name
+
+**Examples:**
+```bash
+# Report progress
+steerdev activity report \
+  --type progress \
+  --message "Completed authentication module, starting API endpoints"
+
+# Report a blocker
+steerdev activity report \
+  --type blocker \
+  --message "Need database credentials to continue testing"
+
+# Report with metadata
+steerdev activity report \
+  --type milestone \
+  --message "All unit tests passing" \
+  --metadata '{"tests_passed": 42, "coverage": "85%"}'
+
+# Report a question
+steerdev activity report \
+  --type question \
+  --message "Should login endpoint support OAuth or just email/password?"
+
+# Report an error
+steerdev activity report \
+  --type error \
+  --message "Build failed: missing dependency @types/node"
+```
+
+### Query Activity
+
+```bash
+steerdev activity query [--run-id RUN_ID] [--type TYPE] [--limit N]
+```
+
+Query activity history with optional filters.
+
+**Options:**
+- `--run-id`, `-r`: Filter by run ID
+- `--type`, `-t`: Filter by event type
+- `--limit`, `-l`: Maximum events to return (default: 20)
+
+**Examples:**
+```bash
+# Get recent activity
+steerdev activity query
+
+# Get activity for a specific run
+steerdev activity query --run-id abc123...
+
+# Get only blockers
+steerdev activity query --type blocker
+
+# Get recent errors
+steerdev activity query --type error --limit 10
+```
+
+## Workflow Example
+
+```bash
+# Starting a task - report progress
+steerdev activity report \
+  --type progress \
+  --message "Starting work on user authentication feature"
+
+# Working on implementation
+steerdev activity report \
+  --type progress \
+  --message "Implemented JWT token generation"
+
+# Hit a blocker
+steerdev activity report \
+  --type blocker \
+  --message "Blocked: Need Redis connection for session storage"
+
+# Ask a question
+steerdev activity report \
+  --type question \
+  --message "Token expiry: 1 hour or 24 hours?"
+
+# Reached a milestone
+steerdev activity report \
+  --type milestone \
+  --message "Authentication module complete with tests"
+
+# Check what happened in a run
+steerdev activity query --run-id abc123...
+```
+
+## Best Practices
+
+1. **Report progress regularly** - Helps track work and identify issues
+2. **Be specific about blockers** - Include what's needed to unblock
+3. **Include relevant metadata** - Add structured data for better tracking
+4. **Report milestones** - Helps identify when major pieces are complete
+5. **Report errors immediately** - Helps with debugging and recovery
+6. **Write progress logs** - Also write to `docs/progress.jsonl` for local visibility
+
+## Complementary: Progress Logging
+
+Activity reporting sends events to the steerdev.com API. You should ALSO write progress logs locally:
+
+- **`docs/progress.jsonl`**: Append JSON lines for each significant event
+- **`docs/{timestamp}_{task}.md`**: Detailed markdown progress notes
+
+See the Progress Logging skill for full details. Both systems work together:
+- Activity API: Real-time server-side visibility
+- Progress logs: Local audit trail and documentation
+
+## Environment
+
+Requires `STEERDEV_API_KEY` environment variable to be set.
+
+**Optional:**
+- `STEERDEV_API_ENDPOINT`: Override the API base URL (default: https://steerdev.com/api/v1)
+- `STEERDEV_AGENT_ID`: Agent identifier for tracking
+- `STEERDEV_AGENT_NAME`: Agent name for display

steerdev_agent/setup/templates/skills/context/SKILL.md

@@ -0,0 +1,122 @@
+# Project Context Skill
+
+This skill provides access to project context information via the steerdev.com API.
+
+Project context includes tech stack, patterns, conventions, and structure information that helps AI agents understand and work effectively within a codebase.
+
+## When to Use
+
+- **Starting work on a project**: Get context to understand tech stack and conventions
+- **Before making architectural decisions**: Check existing patterns
+- **After major codebase changes**: Refresh context to update cached information
+
+## Available Commands
+
+### Get Context
+
+```bash
+steerdev context get [--project-id PROJECT_ID]
+```
+
+Retrieve project context including tech stack, patterns, and structure.
+
+**Options:**
+- `--project-id`, `-p`: Project ID (or use `STEERDEV_PROJECT_ID` env var)
+
+**Example:**
+```bash
+# Get context for the current project
+steerdev context get
+
+# Get context for a specific project
+steerdev context get --project-id abc123...
+```
+
+**Returns:**
+- **Tech Stack**: Languages, frameworks, and tools used
+- **Patterns**: Common code patterns in the project
+- **Conventions**: Coding conventions and style guidelines
+- **Structure**: Project directory structure
+- **Dependencies**: Key dependencies and versions
+
+### Refresh Context
+
+```bash
+steerdev context refresh [--project-id PROJECT_ID]
+```
+
+Force a refresh of cached project context.
+
+Use this after making significant changes to the codebase structure or dependencies.
+
+**Options:**
+- `--project-id`, `-p`: Project ID (or use `STEERDEV_PROJECT_ID` env var)
+
+**Example:**
+```bash
+# Refresh context for the current project
+steerdev context refresh
+```
+
+**Note:** Context refresh happens asynchronously. Run `context get` after a moment to see updated information.
+
+## Workflow Example
+
+```bash
+# At the start of a new task, get project context
+steerdev context get
+
+# Use the context to understand:
+# - What framework to use for new features
+# - What coding patterns to follow
+# - Where to place new files
+
+# After adding new dependencies or changing structure
+steerdev context refresh
+
+# Verify the refresh
+steerdev context get
+```
+
+## Context Information
+
+The context includes:
+
+### Tech Stack
+Languages and frameworks used in the project:
+- Programming languages (Python, TypeScript, etc.)
+- Web frameworks (FastAPI, Next.js, etc.)
+- Database technologies
+- Build tools
+
+### Patterns
+Common patterns observed in the codebase:
+- API patterns (REST, GraphQL)
+- State management patterns
+- Error handling patterns
+- Testing patterns
+
+### Conventions
+Project-specific conventions:
+- Naming conventions
+- File organization
+- Import ordering
+- Code style preferences
+
+### Structure
+Directory structure overview:
+- Source directories
+- Test directories
+- Configuration files
+- Key entry points
+
+### Dependencies
+Major dependencies and their versions to ensure compatibility.
+
+## Environment
+
+Requires `STEERDEV_API_KEY` environment variable to be set.
+
+**Optional:**
+- `STEERDEV_API_ENDPOINT`: Override the API base URL (default: https://steerdev.com/api/v1)
+- `STEERDEV_PROJECT_ID`: Default project ID for all commands

steerdev_agent/setup/templates/skills/git-workflow/SKILL.md

@@ -0,0 +1,218 @@
+# Git Workflow Skill
+
+This skill provides Git workflow commands with steerdev conventions for branch management and pull requests.
+
+## When to Use
+
+- **Starting a task**: Create a properly named task branch
+- **Completing work**: Create a pull request with proper format
+- **Checking status**: See current branch and task context
+
+## Available Commands
+
+### Create Task Branch
+
+```bash
+steerdev git branch TASK_ID [--name NAME]
+```
+
+Create a task branch with steerdev naming convention: `task/<task-id-short>`.
+
+**Arguments:**
+- `TASK_ID`: Task ID to create branch for (uses first 8 characters)
+
+**Options:**
+- `--name`, `-n`: Custom branch name suffix
+
+**Examples:**
+```bash
+# Create branch for task
+steerdev git branch abc12345-def6-7890-...
+# Creates: task/abc12345
+
+# Create branch with descriptive suffix
+steerdev git branch abc12345-def6-7890-... --name auth-flow
+# Creates: task/abc12345-auth-flow
+```
+
+**Behavior:**
+- If branch already exists, switches to it
+- If branch doesn't exist, creates and switches to it
+
+### Create Pull Request
+
+```bash
+steerdev git pr --title "TITLE" [--body "BODY"] [--task-id ID] [--draft]
+```
+
+Create a pull request using GitHub CLI with steerdev conventions.
+
+**Options:**
+- `--title`, `-t`: PR title (required)
+- `--body`, `-b`: PR body/description
+- `--task-id`: Task ID to reference in PR
+- `--draft`, `-d`: Create as draft PR
+
+**Examples:**
+```bash
+# Simple PR
+steerdev git pr --title "Add user authentication"
+
+# PR with description
+steerdev git pr \
+  --title "Add user authentication" \
+  --body "## Summary
+Implements JWT-based authentication.
+
+## Changes
+- Login endpoint
+- Logout endpoint
+- Auth middleware"
+
+# PR linked to task
+steerdev git pr \
+  --title "Add user authentication" \
+  --task-id abc12345...
+
+# Draft PR
+steerdev git pr \
+  --title "WIP: Add user authentication" \
+  --draft
+```
+
+**Note:** Requires GitHub CLI (`gh`) to be installed and authenticated.
+
+### Check Git Status
+
+```bash
+steerdev git status
+```
+
+Show current branch and task context.
+
+**Returns:**
+- Current branch name
+- Task ID (if branch follows `task/<id>` convention)
+- Number of uncommitted changes
+- Remote tracking status
+- Ahead/behind status
+
+**Example Output:**
+```
+Git Status
+Branch: task/abc12345
+Task ID: abc12345
+Uncommitted changes: 3 file(s)
+Tracking: origin/task/abc12345
+Status: 2 ahead, 0 behind
+```
+
+## Complete Workflow Example
+
+```bash
+# 1. Get next task
+steerdev tasks next
+
+# 2. Create task branch
+steerdev git branch abc12345-def6-7890-...
+
+# 3. Check status
+steerdev git status
+
+# 4. Mark task as started
+steerdev tasks update abc12345... --status started
+
+# 5. Create progress log
+TIMESTAMP=$(date -u +%Y%m%d_%H%M%S)
+DOC_FILE="docs/${TIMESTAMP}_add_user_auth.md"
+cat > "$DOC_FILE" << 'EOF'
+# Task: Add User Authentication
+**Task ID**: abc12345
+**Started**: 2026-02-03T14:30:22Z
+**Status**: in-progress
+## Progress
+EOF
+echo '{"timestamp":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","task_id":"abc12345","event":"started","message":"Beginning auth implementation","doc_file":"'"$DOC_FILE"'"}' >> docs/progress.jsonl
+
+# 6. Implement the task...
+# (make commits as you work)
+git add .
+git commit -m "feat: add login endpoint"
+
+# Log progress
+echo '{"timestamp":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","task_id":"abc12345","event":"progress","message":"Login endpoint complete"}' >> docs/progress.jsonl
+
+git add .
+git commit -m "feat: add logout endpoint"
+
+# 7. Check status before PR
+steerdev git status
+
+# 8. Push and create PR
+git push -u origin HEAD
+steerdev git pr \
+  --title "Add user authentication" \
+  --task-id abc12345... \
+  --body "## Summary
+Implements JWT authentication as specified.
+
+## Changes
+- Login endpoint with JWT generation
+- Logout endpoint with token invalidation
+- Auth middleware for protected routes
+
+## Testing
+- Run \`pytest tests/auth/\`
+- Manual test via /api/docs"
+# Returns: https://github.com/org/repo/pull/42
+
+# 9. Log completion
+echo '{"timestamp":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","task_id":"abc12345","event":"completed","message":"Auth implementation complete","pr_url":"https://github.com/org/repo/pull/42","doc_file":"'"$DOC_FILE"'"}' >> docs/progress.jsonl
+
+# 10. Mark task complete with PR URL
+steerdev tasks update abc12345... \
+  --status completed \
+  --result "Implemented auth. PR: https://github.com/org/repo/pull/42"
+```
+
+## Branch Naming Convention
+
+Branches follow the pattern: `task/<short-task-id>[-optional-suffix]`
+
+- `task/abc12345` - Basic task branch
+- `task/abc12345-auth` - With descriptive suffix
+- `task/abc12345-fix-login` - More detailed suffix
+
+The short task ID is the first 8 characters of the full UUID.
+
+## PR Conventions
+
+Pull requests created via this skill include:
+
+1. **Title**: Descriptive title of changes
+2. **Body**: Optional description with:
+   - Summary of changes
+   - Task reference (if --task-id provided)
+3. **Footer**: Link to steerdev.com
+
+## Important Rules
+
+1. **Always create a branch** before starting work
+2. **Commit frequently** with descriptive messages
+3. **Create PR before marking task complete**
+4. **Include PR URL** in task completion result
+5. **Log progress** to `docs/progress.jsonl` (see Progress Logging skill)
+6. **Log completion** with PR URL before marking task done
+
+## Prerequisites
+
+- **Git**: Must be installed and repository initialized
+- **GitHub CLI**: Required for `git pr` command
+  - Install: https://cli.github.com
+  - Authenticate: `gh auth login`
+
+## Environment
+
+No additional environment variables required for git commands.
+
+Uses local git configuration for author information.