drydock-cli 2.3.1__tar.gz → 2.3.2__tar.gz

{drydock_cli-2.3.1 → drydock_cli-2.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: drydock-cli
-Version: 2.3.1
+Version: 2.3.2
 Summary: Drydock — nautical CLI coding agent
 Project-URL: Homepage, https://github.com/fbobe321/drydock
 Project-URL: Repository, https://github.com/fbobe321/drydock

drydock_cli-2.3.2/drydock/skills/api-design/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: api-design
+description: Design and review REST/GraphQL APIs. Schema validation, endpoint design, error handling patterns.
+allowed-tools: read_file grep glob write_file bash
+user-invocable: true
+---
+
+# API Design Review
+
+Analyze or design an API ($ARGUMENTS).
+
+## For existing APIs:
+1. Find route/endpoint definitions
+2. Check for consistency in naming, HTTP methods, status codes
+3. Verify error handling and validation
+4. Check authentication/authorization
+5. Review request/response schemas
+
+## For new APIs:
+1. Define resources and relationships
+2. Design endpoints following REST conventions
+3. Define request/response schemas
+4. Plan error codes and messages
+5. Generate OpenAPI/Swagger spec if requested
+
+## Best Practices
+- Use plural nouns for resources (/users, not /user)
+- Use HTTP methods correctly (GET=read, POST=create, PUT=update, DELETE=delete)
+- Return appropriate status codes (201 for create, 204 for delete)
+- Use consistent error format: `{"error": {"code": "...", "message": "..."}}`
+- Version the API (/v1/, /v2/)
+- Paginate list endpoints

drydock_cli-2.3.2/drydock/skills/commit-code/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: commit-code
+description: Create a git commit with a well-crafted message. Stages changes, reviews diff, writes conventional commit.
+allowed-tools: bash read_file grep
+user-invocable: true
+---
+
+# Commit Workflow
+
+1. Run `git status` and `git diff --stat` to see what changed
+2. Run `git diff` to read the actual changes (limit to 200 lines)
+3. Write a commit message following conventional commits:
+   - `fix:` for bug fixes
+   - `feat:` for new features
+   - `refactor:` for refactoring
+   - `docs:` for documentation
+   - `test:` for test changes
+   - `chore:` for maintenance
+4. Stage relevant files with `git add` (specific files, not -A)
+5. Create the commit with `git commit -m "message"`
+6. Show `git log --oneline -3` to confirm
+
+Rules:
+- NEVER commit .env, credentials, or secrets
+- Keep the first line under 72 characters
+- Add a body if the change is complex
+- If $ARGUMENTS is provided, use it as context for the commit message

drydock_cli-2.3.2/drydock/skills/context-summary/SKILL.md

@@ -0,0 +1,19 @@
+---
+name: context-summary
+description: Summarize the current session context. What files were read, edited, what's the current state.
+allowed-tools: bash read_file
+user-invocable: true
+---
+
+# Context Summary
+
+Produce a summary of the current working state:
+
+1. **Git status**: `git status --short`
+2. **Recent changes**: `git diff --stat`
+3. **Recent commits**: `git log --oneline -5`
+4. **Modified files**: List files changed in this session
+5. **Current task**: What was the user's original request?
+6. **Progress**: What's been done, what remains?
+
+Output as a clean summary the user can quickly scan.

drydock_cli-2.3.2/drydock/skills/deploy/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: deploy
+description: Deployment workflow. Build, test, tag, push, deploy. Supports PyPI, Docker, GitHub releases.
+allowed-tools: bash read_file grep
+user-invocable: true
+---
+
+# Deployment Workflow
+
+## Steps
+1. Run tests: `python -m pytest -x -q`
+2. Check version in pyproject.toml or setup.py
+3. Build: `python -m build` or `docker build .`
+4. Deploy based on target ($ARGUMENTS):
+   - **pypi**: `twine upload dist/*`
+   - **docker**: `docker push`
+   - **github**: `gh release create`
+   - **server**: `rsync` or `ssh` deploy
+5. Tag: `git tag vX.Y.Z && git push --tags`
+6. Notify: output deployment summary
+
+## Rules
+- ALWAYS run tests before deploying
+- NEVER deploy with uncommitted changes
+- Check that version was bumped
+- Verify the deployment succeeded

drydock_cli-2.3.2/drydock/skills/diff-review/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: diff-review
+description: Show and analyze uncommitted changes. Summarize what changed and why.
+allowed-tools: bash read_file
+user-invocable: true
+---
+
+# Diff Review
+
+1. Show uncommitted changes: `git diff --stat`
+2. Show the full diff: `git diff`
+3. For each changed file, analyze:
+   - What was the intent of the change?
+   - Is the change correct and complete?
+   - Any issues or improvements?
+4. Provide a summary suitable for a commit message

drydock_cli-2.3.2/drydock/skills/doc-gen/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: doc-gen
+description: Generate documentation for code. Docstrings, README, API docs, usage examples.
+allowed-tools: read_file grep glob search_replace write_file
+user-invocable: true
+---
+
+# Documentation Generator
+
+Generate documentation for the specified code ($ARGUMENTS or current project).
+
+## Modes
+1. **Docstrings**: Add/update docstrings for functions, classes, methods
+2. **README**: Generate or update README.md with usage, installation, API
+3. **API docs**: Generate API reference documentation
+4. **Examples**: Create usage examples
+
+## Workflow
+1. Read the source files to document
+2. Understand the public API (exported functions, classes)
+3. Generate documentation in the appropriate format
+4. Write the documentation files
+
+## Rules
+- Follow Google-style or NumPy-style docstrings (match existing style)
+- Include type hints in docstrings if not in code
+- Document parameters, return values, exceptions
+- Add usage examples for non-obvious functions

drydock_cli-2.3.2/drydock/skills/explain-code/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: explain-code
+description: Explain code in detail. What it does, how it works, why it's written that way.
+allowed-tools: read_file grep glob
+user-invocable: true
+---
+
+# Code Explanation
+
+Explain the code specified in $ARGUMENTS (file path, function name, or concept).
+
+## Approach
+1. Find and read the relevant code
+2. Explain at three levels:
+   - **What**: One sentence summary of what this code does
+   - **How**: Step-by-step walkthrough of the logic
+   - **Why**: Design decisions, tradeoffs, alternatives
+3. Call out any:
+   - Non-obvious patterns or idioms
+   - Potential gotchas or edge cases
+   - Performance characteristics
+   - Dependencies on other parts of the codebase
+
+## Format
+Keep explanations clear and concise. Use code snippets to reference specific lines.
+Adjust detail level to the complexity — simple code gets a brief explanation,
+complex algorithms get detailed walkthroughs.

drydock_cli-2.3.2/drydock/skills/explore-code/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: explore-code
+description: Structured codebase exploration. Map architecture, find entry points, understand dependencies.
+allowed-tools: bash read_file grep glob
+context: fork
+agent: explore
+user-invocable: true
+---
+
+# Codebase Exploration
+
+1. **Structure**: List top-level directories and key files
+   - `find . -maxdepth 2 -type f -name "*.py" | head -30`
+   - Look for: README, setup.py/pyproject.toml, main entry points
+
+2. **Entry points**: Find how the code starts
+   - Look for __main__.py, cli.py, app.py, manage.py
+   - Read the main entry point (first 50 lines)
+
+3. **Architecture**: Map the module structure
+   - List packages (directories with __init__.py)
+   - Identify the core modules vs utilities vs tests
+
+4. **Dependencies**: Check what's imported
+   - `grep -r "^import\|^from" --include="*.py" | sort -u | head -30`
+   - Check requirements.txt or pyproject.toml dependencies
+
+5. **Tests**: Find the test structure
+   - `find . -name "test_*.py" -o -name "*_test.py" | head -20`
+
+6. **Report**: Summarize findings in this format:
+   ```
+   PROJECT: name
+   LANGUAGE: Python X.Y
+   STRUCTURE: package/module layout
+   ENTRY POINTS: main files
+   KEY MODULES: core functionality
+   TEST FRAMEWORK: pytest/unittest/etc
+   DEPENDENCIES: key external deps
+   ```
+
+If $ARGUMENTS is provided, focus exploration on that specific area.

drydock_cli-2.3.2/drydock/skills/fix-issue/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: fix-issue
+description: Structured bug fix workflow. Locate, hypothesize, fix, verify. Designed for SWE-bench style tasks.
+allowed-tools: bash read_file grep glob search_replace write_file
+user-invocable: true
+---
+
+# Fix Issue Workflow
+
+## Phase 1: Locate
+1. Grep for the class/function/error mentioned in the bug description
+2. Read the relevant source file (use offset/limit, 50-100 lines)
+3. Identify the root cause — which line(s) need to change
+
+## Phase 2: Hypothesize
+4. Form a hypothesis: "The bug is caused by X because Y"
+5. Identify the minimal fix — usually 1-5 lines in 1 file
+
+## Phase 3: Fix
+6. Apply the fix with search_replace (exact text match)
+7. If search_replace fails, re-read the file first, then retry with EXACT text
+8. Read back the changed lines to verify the edit applied
+
+## Phase 4: Verify
+9. Run relevant tests if available: `python -m pytest <test_file> -x -q`
+10. If tests pass, done. If tests fail, read the failure and iterate.
+
+## Rules
+- NEVER edit test files — the bug is in source code
+- Keep changes minimal — no refactoring
+- A wrong fix attempt is better than no fix
+- Maximum 3 fix attempts before trying a different approach
+- If $ARGUMENTS provided, treat it as the bug description

drydock_cli-2.3.2/drydock/skills/git-ops/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: git-ops
+description: Git operations helper. Branching, merging, rebasing, conflict resolution, history analysis.
+allowed-tools: bash read_file
+user-invocable: true
+---
+
+# Git Operations
+
+Handle git tasks based on $ARGUMENTS:
+
+## Common Operations
+- **branch**: `git checkout -b feature/$0`
+- **merge**: `git merge $0` with conflict resolution
+- **rebase**: `git rebase $0` — fix conflicts if any
+- **stash**: `git stash` / `git stash pop`
+- **cherry-pick**: `git cherry-pick $0`
+- **log**: `git log --oneline --graph -20`
+- **blame**: `git blame $0`
+- **bisect**: Binary search for the commit that introduced a bug
+- **clean**: `git clean -fd` (with confirmation)
+
+## Conflict Resolution
+1. Show conflicted files: `git diff --name-only --diff-filter=U`
+2. For each conflict, read the file and resolve
+3. Stage resolved files: `git add <file>`
+4. Continue: `git rebase --continue` or `git merge --continue`
+
+## Rules
+- NEVER force push to main/master
+- Always stash before destructive operations
+- Show the user what will happen before doing it

drydock_cli-2.3.2/drydock/skills/init-project/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: init-project
+description: Initialize a new project with standard structure, README, tests, CI config.
+allowed-tools: bash write_file read_file
+user-invocable: true
+---
+
+# Project Initialization
+
+Create a new project with standard Python structure.
+
+1. Create directory structure:
+   ```
+   $0/
+   ├── $0/
+   │   ├── __init__.py
+   │   ├── __main__.py
+   │   └── cli.py
+   ├── tests/
+   │   ├── __init__.py
+   │   └── test_$0.py
+   ├── pyproject.toml
+   ├── README.md
+   └── .gitignore
+   ```
+2. Write pyproject.toml with project metadata
+3. Write a basic README.md
+4. Write __init__.py with version
+5. Write __main__.py entry point
+6. Write a sample test
+7. Initialize git: `git init && git add -A && git commit -m "Initial commit"`
+
+If $ARGUMENTS specifies a framework (flask, fastapi, django), adapt the structure.

drydock_cli-2.3.2/drydock/skills/loop/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: loop
+description: Run a prompt repeatedly on an interval. Useful for monitoring, polling, or iterative tasks.
+allowed-tools: bash read_file grep glob search_replace write_file
+user-invocable: true
+---
+
+# Loop Execution
+
+Run the given task repeatedly. Usage: `/loop [interval_seconds] <task>`
+
+Default interval: 60 seconds.
+
+1. Parse interval from $0 (if numeric), otherwise default to 60
+2. Execute the task: $ARGUMENTS
+3. Wait for the interval
+4. Repeat until interrupted or task reports completion
+
+## Common uses:
+- `/loop 30 check if the build passed` — poll CI every 30s
+- `/loop 60 run tests and fix failures` — continuous test-fix loop
+- `/loop 120 check PR comments and respond` — monitor PR

drydock_cli-2.3.2/drydock/skills/migrate/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: migrate
+description: Help with code migrations. Python version upgrades, framework migrations, dependency updates.
+allowed-tools: bash read_file grep glob search_replace write_file
+user-invocable: true
+---
+
+# Migration Helper
+
+Assist with migrating code ($ARGUMENTS describes the migration).
+
+## Common Migrations
+- **Python 2→3**: Fix print statements, dict methods, string handling
+- **Django version**: Update deprecated APIs, new settings
+- **Flask→FastAPI**: Convert routes, add async, update schemas
+- **unittest→pytest**: Convert test classes, assertions, fixtures
+- **requirements.txt→pyproject.toml**: Convert dependency format
+- **JavaScript→TypeScript**: Add types, rename files
+
+## Workflow
+1. Identify what needs to change (grep for deprecated patterns)
+2. Plan the migration order (dependencies first)
+3. Apply changes file by file
+4. Run tests after each file
+5. Fix any breakage

drydock_cli-2.3.2/drydock/skills/perf-analyze/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: perf-analyze
+description: Performance analysis. Profile code, find bottlenecks, suggest optimizations.
+allowed-tools: bash read_file grep glob
+user-invocable: true
+---
+
+# Performance Analysis
+
+Analyze code performance for $ARGUMENTS (or recent changes).
+
+## Steps
+1. Identify hot paths — which functions are called most?
+2. Look for common performance issues:
+   - N+1 queries (loops with database calls)
+   - Unnecessary list copies/conversions
+   - Missing caching for repeated computations
+   - Blocking I/O in async code
+   - Large memory allocations in loops
+   - String concatenation in loops (use join)
+3. Profile if possible: `python -m cProfile -s cumtime script.py 2>&1 | head -30`
+4. Suggest specific optimizations with before/after examples
+
+## Output
+### Bottlenecks Found
+- [file:line] Description — estimated impact
+
+### Recommended Optimizations
+1. [Change] — expected improvement

drydock_cli-2.3.2/drydock/skills/plan-impl/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: plan-impl
+description: Create a detailed implementation plan before coding. Identifies files, dependencies, order of changes.
+allowed-tools: read_file grep glob
+context: fork
+agent: planner
+user-invocable: true
+---
+
+# Implementation Planning
+
+Given a task description ($ARGUMENTS), create a comprehensive plan.
+
+## Steps
+1. Analyze the requirements
+2. Explore the existing codebase to understand constraints
+3. Identify all files that need to be created or modified
+4. Determine the order of changes (dependencies first)
+5. Estimate complexity per file
+
+## Output Format
+```
+# Implementation Plan: [title]
+
+## Overview
+[1-2 sentence summary]
+
+## Files to Change
+1. `path/to/file.py` — [what changes] (complexity: low/med/high)
+2. `path/to/other.py` — [what changes] (complexity: low/med/high)
+
+## New Files
+1. `path/to/new.py` — [purpose]
+
+## Order of Implementation
+1. [first thing to do and why]
+2. [second thing]
+3. [etc]
+
+## Risks & Considerations
+- [potential issues]
+
+## Testing Strategy
+- [how to verify the changes work]
+```

drydock_cli-2.3.2/drydock/skills/pr-review/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: pr-review
+description: Review a pull request. Fetches diff, analyzes changes, checks for bugs, security issues, and style.
+allowed-tools: bash read_file grep glob
+user-invocable: true
+---
+
+# PR Review Workflow
+
+1. Get the PR diff: `git diff main...HEAD` (or `!`git diff main...HEAD``)
+2. List changed files: `git diff --name-only main...HEAD`
+3. For each changed file:
+   a. Read the full diff for that file
+   b. Check for: bugs, security issues, performance problems, missing error handling
+   c. Check for: style consistency, naming conventions, dead code
+4. Produce a structured review:
+
+## Review Output Format
+### Critical Issues (must fix)
+- [file:line] Description of issue
+
+### Suggestions (should fix)
+- [file:line] Description of improvement
+
+### Nits (optional)
+- [file:line] Minor style/preference items
+
+### Summary
+- Overall assessment: APPROVE / REQUEST_CHANGES / COMMENT
+- One paragraph summary of the changes
+
+If $0 is a PR number, fetch it with: `gh pr diff $0`

drydock_cli-2.3.2/drydock/skills/refactor/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: refactor
+description: Structured code refactoring. Identify patterns, plan changes, apply safely, verify.
+allowed-tools: bash read_file grep glob search_replace write_file
+user-invocable: true
+---
+
+# Refactoring Workflow
+
+## Phase 1: Understand
+1. Read the code to refactor (specified in $ARGUMENTS or recent changes)
+2. Identify the refactoring type:
+   - Extract function/method
+   - Rename variable/function/class
+   - Simplify conditionals
+   - Remove duplication
+   - Split large function
+   - Move code to better location
+
+## Phase 2: Plan
+3. List every file that will change
+4. For each file, describe the specific change
+5. Identify risks: what could break?
+
+## Phase 3: Apply
+6. Make changes one file at a time with search_replace
+7. After each change, verify syntax: `python -c "import ast; ast.parse(open('file').read())"`
+
+## Phase 4: Verify
+8. Run tests if available
+9. Check imports still resolve
+10. Verify no functionality changed (refactor = same behavior, better structure)
+
+## Rules
+- One refactoring at a time — don't combine multiple refactors
+- Preserve all existing behavior
+- Run tests after each change

drydock_cli-2.3.2/drydock/skills/regex-help/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: regex-help
+description: Build, explain, and test regular expressions. Supports Python re module syntax.
+allowed-tools: bash
+user-invocable: true
+---
+
+# Regex Helper
+
+Help with regular expressions based on $ARGUMENTS.
+
+## Modes
+- **Build**: "match email addresses" → provide the regex
+- **Explain**: Given a regex, explain what it matches
+- **Test**: Test a regex against sample strings
+- **Debug**: Fix a regex that's not matching correctly
+
+## Testing
+```python
+python3 -c "
+import re
+pattern = r'YOUR_REGEX'
+tests = ['test1', 'test2', 'test3']
+for t in tests:
+    m = re.search(pattern, t)
+    print(f'{t!r}: {\"MATCH\" if m else \"no match\"}  {m.groups() if m else \"\"}'  )
+"
+```
+
+Always provide the regex in Python `re` module syntax with raw strings (r'...').

drydock_cli-2.3.2/drydock/skills/security-review/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: security-review
+description: Security audit of code changes. Checks OWASP Top 10, secrets, injection, auth issues.
+allowed-tools: bash read_file grep glob
+user-invocable: true
+---
+
+# Security Review
+
+Analyze the current changes (or specified files) for security vulnerabilities.
+
+## Checks
+1. **Secrets/Credentials**: grep for API keys, passwords, tokens, private keys
+   - `grep -rn "password\|secret\|api_key\|token\|private_key\|AWS_" --include="*.py" | head -20`
+2. **SQL Injection**: Look for string formatting in SQL queries
+   - `grep -rn "f\".*SELECT\|\.format.*SELECT\|%.*SELECT" --include="*.py"`
+3. **Command Injection**: Look for shell=True, os.system, subprocess with user input
+   - `grep -rn "shell=True\|os\.system\|subprocess.*shell" --include="*.py"`
+4. **XSS**: Look for unescaped user input in HTML/templates
+5. **Path Traversal**: Look for user-controlled file paths without sanitization
+6. **Auth/AuthZ**: Check for missing authentication or authorization checks
+7. **Sensitive Data**: Check logging for PII, credentials in error messages
+8. **Dependencies**: Check for known vulnerable packages
+
+## Output Format
+### CRITICAL (immediate fix required)
+### HIGH (fix before merge)
+### MEDIUM (fix soon)
+### LOW (informational)
+
+Each finding: [SEVERITY] file:line — description + recommended fix

drydock_cli-2.3.2/drydock/skills/test-verify/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: test-verify
+description: Run tests, parse failures, fix failing tests. Structured test-driven debugging.
+allowed-tools: bash read_file grep search_replace
+user-invocable: true
+---
+
+# Test Verification Workflow
+
+1. Discover test framework: look for pytest.ini, setup.cfg, tox.ini, or pyproject.toml
+2. Run tests: `python -m pytest $ARGUMENTS -x -q --tb=short 2>&1 | head -50`
+3. Parse the output:
+   - Count: passed, failed, errors, skipped
+   - For each failure: extract test name, file, line, assertion message
+4. For each failing test:
+   a. Read the test code to understand what it expects
+   b. Read the source code it tests
+   c. Identify the mismatch
+   d. Fix the source (not the test) with search_replace
+5. Re-run the failing test to verify: `python -m pytest <test_file>::<test_name> -x -q`
+6. Report results
+
+## Rules
+- Fix source code, not tests (unless the test itself is wrong)
+- Run only the specific failing test when verifying, not the full suite
+- If a test fails due to environment issues (missing deps), report it instead of fixing
+- Maximum 3 iterations per failing test

{drydock_cli-2.3.1 → drydock_cli-2.3.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "drydock-cli"
-version = "2.3.1"
+version = "2.3.2"
 description = "Drydock — nautical CLI coding agent"
 readme = "README.md"
 requires-python = ">=3.12"