generate

sorify

Trigger

Invoked from the generate command with natural language or structured arguments.

---

Step 1: Understand the input and determine mode

The input may be plain arguments, structured text, or natural language in any language. Read the entire input and extract:

What	How to identify
target_url	Any https:// or http:// URL that is clearly the service being tested (NOT a GHE/GitHub repo URL)
source	A GHE/GitHub URL, or a local filesystem path (/, ~/, ./ prefix) — optional

Examples:

https://stg.example.com/
  → target_url = https://stg.example.com/, source = none

https://stg.example.com/ https://github.com/your-org/your-repo
  → target_url = https://stg.example.com/, source = ghe (order does not matter)

https://github.com/your-org/your-repo https://stg.example.com/
  → same result

このサービスのテストを作成して。URL: https://stg.example.com/ リポジトリ: https://github.com/your-org/your-repo
  → target_url = https://stg.example.com/, source = ghe

/Users/hiro/projects/myapp https://stg.example.com/
  → target_url = https://stg.example.com/, source = /Users/hiro/projects/myapp

If target_url cannot be identified → abort with error:

Error: No target URL found. Please provide the URL of the service to test.

Determine mode:

source absent or empty  → DOM Mode
source is GHE/GitHub URL (contains 'ghe.' / 'github.com' / 'your-ghe-domain')  → GHE Source Mode
source is local path (starts with '/', '~/', './')  → Local Source Mode

---

Step 2: Determine the Sorify base URL

The Sorify MCP server (configured in this plugin's .mcp.json) already handles authentication transparently — no login step is needed here. Read SORIFY_URL from ~/.sorify only for building the human-readable run link in the final summary:

if [ ! -f ~/.sorify ]; then
  echo "Error: ~/.sorify not found. Please create it with your Sorify credentials."
  echo "See the plugin README for the required format."
  exit 1
fi

SORIFY_BASE_URL=$(grep "^SORIFY_URL" ~/.sorify | cut -d= -f2)
UPLOADED_BY=$(grep "^SORIFY_USERNAME" ~/.sorify | cut -d= -f2)