prjct-cli 0.20.0 → 0.20.1

package/templates/permissions/strict.jsonc

@@ -0,0 +1,62 @@
+{
+  // Strict permissions preset for prjct-cli
+  // Maximum safety - requires approval for most operations
+
+  "bash": {
+    // Only read-only commands allowed
+    "git status": "allow",
+    "git log*": "allow",
+    "git diff*": "allow",
+    "ls*": "allow",
+    "pwd": "allow",
+    "cat*": "allow",
+    "head*": "allow",
+    "tail*": "allow",
+    "which*": "allow",
+
+    // Everything else requires approval
+    "git*": "ask",
+    "npm*": "ask",
+    "bun*": "ask",
+    "node*": "ask",
+    "rm*": "ask",
+    "mv*": "ask",
+    "cp*": "ask",
+    "mkdir*": "ask",
+
+    // Always denied
+    "rm -rf*": "deny",
+    "sudo*": "deny",
+    "chmod 777*": "deny"
+  },
+
+  "files": {
+    "read": {
+      "**/*": "allow",
+      "**/.*": "ask",           // Hidden files need approval
+      "**/.env*": "deny"        // Never read env files
+    },
+    "write": {
+      "**/*": "ask"             // All writes need approval
+    },
+    "delete": {
+      "**/*": "deny"            // No deletions without explicit override
+    }
+  },
+
+  "web": {
+    "enabled": true,
+    "blockedDomains": [
+      "localhost",
+      "127.0.0.1",
+      "internal"
+    ]
+  },
+
+  "doomLoop": {
+    "enabled": true,
+    "maxRetries": 2
+  },
+
+  "externalDirectories": "deny"
+}

package/templates/skills/code-review.md

@@ -0,0 +1,47 @@
+---
+name: Code Review
+description: Review code changes for quality, security, and best practices
+agent: general
+tags: [review, quality, security]
+version: 1.0.0
+---
+
+# Code Review Skill
+
+Review the provided code changes with focus on:
+
+## Quality Checks
+- Code readability and clarity
+- Naming conventions
+- Function/method length
+- Code duplication
+- Error handling
+
+## Security Checks
+- Input validation
+- SQL injection risks
+- XSS vulnerabilities
+- Sensitive data exposure
+- Authentication/authorization issues
+
+## Best Practices
+- SOLID principles
+- DRY (Don't Repeat Yourself)
+- Single responsibility
+- Proper typing (TypeScript)
+- Documentation where needed
+
+## Output Format
+
+Provide feedback in this structure:
+
+### Summary
+Brief overview of the changes
+
+### Issues Found
+- 🔴 **Critical**: Must fix before merge
+- 🟡 **Warning**: Should fix, but not blocking
+- 🔵 **Suggestion**: Nice to have improvements
+
+### Recommendations
+Specific actionable items to improve the code

package/templates/skills/debug.md

@@ -0,0 +1,61 @@
+---
+name: Debug
+description: Systematic debugging to find and fix issues
+agent: general
+tags: [debug, fix, troubleshoot]
+version: 1.0.0
+---
+
+# Debug Skill
+
+Systematically debug the reported issue.
+
+## Process
+
+### Step 1: Understand the Problem
+- What is the expected behavior?
+- What is the actual behavior?
+- When did it start happening?
+- Can it be reproduced consistently?
+
+### Step 2: Gather Information
+- Read relevant error messages
+- Check logs
+- Review recent changes
+- Identify affected code paths
+
+### Step 3: Form Hypothesis
+- What could cause this behavior?
+- List possible causes in order of likelihood
+- Identify the most likely root cause
+
+### Step 4: Test Hypothesis
+- Add logging if needed
+- Isolate the problematic code
+- Verify the root cause
+
+### Step 5: Fix
+- Implement the minimal fix
+- Ensure no side effects
+- Add tests if applicable
+
+### Step 6: Verify
+- Confirm the issue is resolved
+- Check for regressions
+- Document the fix
+
+## Output Format
+
+```
+## Issue
+[Description of the problem]
+
+## Root Cause
+[What was causing the issue]
+
+## Fix
+[What was changed to fix it]
+
+## Prevention
+[How to prevent similar issues]
+```

package/templates/skills/refactor.md

@@ -0,0 +1,47 @@
+---
+name: Refactor
+description: Refactor code for better structure, readability, and maintainability
+agent: general
+tags: [refactor, cleanup, improvement]
+version: 1.0.0
+---
+
+# Refactor Skill
+
+Refactor the specified code with these goals:
+
+## Objectives
+1. **Improve Readability** - Clear naming, logical structure
+2. **Reduce Complexity** - Simplify nested logic, extract functions
+3. **Enhance Maintainability** - Make future changes easier
+4. **Preserve Behavior** - No functional changes unless requested
+
+## Approach
+
+### Step 1: Analyze Current Code
+- Identify pain points
+- Note code smells
+- Understand dependencies
+
+### Step 2: Plan Changes
+- List specific refactoring operations
+- Prioritize by impact
+- Consider breaking changes
+
+### Step 3: Execute
+- Make incremental changes
+- Test after each change
+- Document decisions
+
+## Common Refactorings
+- Extract function/method
+- Rename for clarity
+- Remove duplication
+- Simplify conditionals
+- Replace magic numbers with constants
+- Add type annotations
+
+## Output
+- Modified code
+- Brief explanation of changes
+- Any trade-offs made

package/templates/subagents/domain/devops.md

@@ -59,7 +59,7 @@ jobs:
         with:
           node-version: '20'
       - run: npm ci
-      - run: npm test
+      - run: npm test  # or pnpm test / yarn test / bun test depending on the repo
 ```
 
 ### docker-compose

package/templates/subagents/domain/testing.md

@@ -1,6 +1,6 @@
 ---
 name: testing
-description: Testing specialist for Jest, Vitest, Pytest, and testing libraries. Use PROACTIVELY when user works on tests, coverage, or test infrastructure.
+description: Testing specialist for Bun test, Jest, Pytest, and testing libraries. Use PROACTIVELY when user works on tests, coverage, or test infrastructure.
 tools: Read, Write, Bash
 model: sonnet
 ---
@@ -9,7 +9,7 @@ You are a testing specialist agent for this project.
 
 ## Your Expertise
 
-- **JS/TS**: Jest, Vitest, Mocha, Bun test
+- **JS/TS**: Bun test, Jest, Mocha
 - **React**: Testing Library, Enzyme
 - **Python**: Pytest, unittest
 - **Go**: testing package, testify
@@ -18,15 +18,15 @@ You are a testing specialist agent for this project.
 ## Project Context
 
 When invoked, analyze the project's testing setup:
-1. Check for test config (jest.config.js, vitest.config.ts, pytest.ini)
+1. Check for test config (bunfig.toml, jest.config.js, pytest.ini)
 2. Identify test file patterns
 3. Check for existing test utilities
 
 ## Code Patterns
 
-### Vitest/Jest (Unit)
+### Bun (Unit)
 ```typescript
-import { describe, it, expect, vi } from 'vitest'
+import { describe, it, expect, mock } from 'bun:test'
 import { calculateTotal } from './cart'
 
 describe('calculateTotal', () => {
@@ -48,7 +48,7 @@ import { Button } from './Button'
 
 describe('Button', () => {
   it('calls onClick when clicked', () => {
-    const onClick = vi.fn()
+    const onClick = mock(() => {})
     render(<Button onClick={onClick}>Click me</Button>)
 
     fireEvent.click(screen.getByRole('button'))
@@ -118,7 +118,6 @@ func TestCalculateTotal(t *testing.T) {
 # JavaScript
 npm test
 bun test
-vitest run
 
 # Python
 pytest
@@ -131,9 +130,6 @@ go test -cover ./...
 
 ### Coverage
 ```bash
-# Vitest
-vitest run --coverage
-
 # Jest
 jest --coverage
 

package/templates/subagents/workflow/prjct-shipper.md

@@ -30,13 +30,22 @@ Run in sequence, stop on failure:
 
 ```bash
 # 1. Lint (if configured)
-npm run lint || bun run lint
+# Use the project's own tooling (do not assume JS/Bun).
+# Examples:
+# - JS: pnpm run lint / yarn lint / npm run lint / bun run lint
+# - Python: ruff/flake8 (only if project already uses it)
 
-# 2. Type check (if TypeScript)
-npm run typecheck || tsc --noEmit
+# 2. Type check (if configured)
+# - TS: pnpm run typecheck / yarn typecheck / npm run typecheck / bun run typecheck
 
 # 3. Tests (if configured)
-npm test || bun test
+# Use the project's own test runner:
+# - JS: {packageManager} test (e.g. pnpm test, yarn test, npm test, bun test)
+# - Python: pytest
+# - Go: go test ./...
+# - Rust: cargo test
+# - .NET: dotnet test
+# - Java: mvn test / ./gradlew test
 ```
 
 If any fail:
@@ -125,12 +134,12 @@ Read from `.prjct/ship.config.json` if exists:
     "typecheck": true,
     "test": true
   },
-  "testCommand": "bun test",
-  "lintCommand": "bun run lint"
+  "testCommand": "pytest",
+  "lintCommand": "npm run lint"
 }
 ```
 
-If no config, auto-detect from package.json scripts.
+If no config, auto-detect from the repository (package.json scripts, pytest.ini, Cargo.toml, go.mod, etc.).
 
 ## Dry Run Mode
 

package/templates/tools/bash.txt

@@ -0,0 +1,22 @@
+Execute shell commands in a persistent bash session.
+
+Use this tool for terminal operations like git, npm, docker, build commands, and system utilities. NOT for file operations (use Read, Write, Edit instead).
+
+Capabilities:
+- Run any shell command
+- Persistent session (environment persists between calls)
+- Support for background execution
+- Configurable timeout (up to 10 minutes)
+
+Best practices:
+- Quote paths with spaces using double quotes
+- Use absolute paths to avoid cd
+- Chain dependent commands with &&
+- Run independent commands in parallel (multiple tool calls)
+- Never use for file reading (use Read tool)
+- Never use echo/printf to communicate (output text directly)
+
+Git operations:
+- Never update git config
+- Never use destructive commands without explicit request
+- Always use HEREDOC for commit messages

package/templates/tools/edit.txt

@@ -0,0 +1,18 @@
+Edit files using exact string replacement.
+
+Use this tool to make precise changes to existing files. Requires reading the file first to ensure accurate matching.
+
+Capabilities:
+- Replace exact string matches in files
+- Support for replace_all to change all occurrences
+- Preserves file formatting and indentation
+
+Requirements:
+- Must read the file first (tool will error otherwise)
+- old_string must be unique in the file (or use replace_all)
+- Preserve exact indentation from the original
+
+Best practices:
+- Include enough context to make old_string unique
+- Use replace_all for renaming variables/functions
+- Never include line numbers in old_string or new_string

package/templates/tools/glob.txt

@@ -0,0 +1,19 @@
+Find files by pattern matching.
+
+Use this tool to locate files using glob patterns. Fast and efficient for any codebase size.
+
+Capabilities:
+- Match files using glob patterns (e.g., "**/*.ts", "src/**/*.tsx")
+- Returns paths sorted by modification time
+- Works with any codebase size
+
+Pattern examples:
+- "**/*.ts" - all TypeScript files
+- "src/**/*.tsx" - React components in src
+- "**/test*.ts" - test files anywhere
+- "core/**/*" - all files in core directory
+
+Best practices:
+- Use specific patterns to narrow results
+- Prefer glob over bash find command
+- Run multiple patterns in parallel if needed

package/templates/tools/grep.txt

@@ -0,0 +1,21 @@
+Search file contents using regex patterns.
+
+Use this tool to search for code patterns, function definitions, imports, and text across the codebase. Built on ripgrep for speed.
+
+Capabilities:
+- Full regex syntax support
+- Filter by file type or glob pattern
+- Multiple output modes: files_with_matches, content, count
+- Context lines before/after matches (-A, -B, -C)
+- Multiline matching support
+
+Output modes:
+- files_with_matches (default): just file paths
+- content: matching lines with context
+- count: match counts per file
+
+Best practices:
+- Use specific patterns to reduce noise
+- Filter by file type when possible (type: "ts")
+- Use content mode with context for understanding matches
+- Never use bash grep/rg directly (use this tool)

package/templates/tools/read.txt

@@ -0,0 +1,14 @@
+Read files from the filesystem.
+
+Use this tool to read file contents before making edits. Always read a file before attempting to modify it to understand the current state and structure.
+
+Capabilities:
+- Read any text file by absolute path
+- Supports line offset and limit for large files
+- Returns content with line numbers for easy reference
+- Can read images, PDFs, and Jupyter notebooks
+
+Best practices:
+- Always read before editing
+- Use offset/limit for files > 2000 lines
+- Read multiple related files in parallel when exploring

package/templates/tools/task.txt

@@ -0,0 +1,20 @@
+Launch specialized agents for complex tasks.
+
+Use this tool to delegate multi-step tasks to autonomous agents. Each agent type has specific capabilities and tools.
+
+Agent types:
+- Explore: Fast codebase exploration, file search, pattern finding
+- Plan: Software architecture, implementation planning
+- general-purpose: Research, code search, multi-step tasks
+
+When to use:
+- Complex multi-step tasks
+- Open-ended exploration
+- When multiple search rounds may be needed
+- Tasks matching agent descriptions
+
+Best practices:
+- Provide clear, detailed prompts
+- Launch multiple agents in parallel when independent
+- Use Explore for codebase questions
+- Use Plan for implementation design

package/templates/tools/webfetch.txt

@@ -0,0 +1,16 @@
+Fetch and analyze web content.
+
+Use this tool to retrieve content from URLs and process it with AI. Useful for documentation, API references, and external resources.
+
+Capabilities:
+- Fetch any URL content
+- Automatic HTML to markdown conversion
+- AI-powered content extraction based on prompt
+- 15-minute cache for repeated requests
+- Automatic HTTP to HTTPS upgrade
+
+Best practices:
+- Provide specific prompts for extraction
+- Handle redirects by following the provided URL
+- Use for documentation and reference lookup
+- Results may be summarized for large content

package/templates/tools/websearch.txt

@@ -0,0 +1,18 @@
+Search the web for current information.
+
+Use this tool to find up-to-date information beyond the knowledge cutoff. Returns search results with links.
+
+Capabilities:
+- Real-time web search
+- Domain filtering (allow/block specific sites)
+- Returns formatted results with URLs
+
+Requirements:
+- MUST include Sources section with URLs after answering
+- Use current year in queries for recent info
+
+Best practices:
+- Be specific in search queries
+- Include year for time-sensitive searches
+- Always cite sources in response
+- Filter domains when targeting specific sites

package/templates/tools/write.txt

@@ -0,0 +1,17 @@
+Write or create files on the filesystem.
+
+Use this tool to create new files or completely overwrite existing ones. For modifications to existing files, prefer the Edit tool instead.
+
+Capabilities:
+- Create new files with specified content
+- Overwrite existing files completely
+- Create parent directories automatically
+
+Requirements:
+- Must read existing file first before overwriting
+- Use absolute paths only
+
+Best practices:
+- Prefer Edit for modifications to existing files
+- Only create new files when truly necessary
+- Never create documentation files unless explicitly requested