Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/CodySwannGT/lisa --skill ops-run-localコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか?SkillsMP が現在取得できるファイルをダウンロードできます。
This skill should be used for any non-trivial request — features, bugs, stories, epics, spikes, or multi-step tasks. It accepts a ticket URL (Jira, Linear, GitHub), a file path containing a spec, or a plain-text prompt. It assembles an agent team, breaks the work into structured tasks, and manages the full lifecycle from research through implementation, code review, deploy, and empirical verification.
any non-trivial request —…
This skill should be used for any non-trivial request — features, bugs, stories, epics, spikes, or multi-step tasks. It accepts a ticket URL (Jira, Linear, GitHub), a file path containing a spec, or a plain-text prompt. It assembles an agent team, breaks the work into structured tasks, and manages the full lifecycle from research through implementation, code review, deploy, and empirical verification.
SOC 職業分類に基づく
SKILL.md を表示中
| name | ops-run-local |
| description | Manage the local development… |
| allowed-tools | ["Bash","Read"] |
Manage the local development environment.
Argument: $ARGUMENTS — start, stop, restart, status, start-frontend, start-backend (default: start)
.)${BACKEND_DIR:-../backend-v2} — set BACKEND_DIR in .claude/settings.local.json if your backend is elsewhereBACKEND_DIR="${BACKEND_DIR:-../backend-v2}"
test -d "$BACKEND_DIR" && echo "Backend dir OK: $BACKEND_DIR" || echo "ERROR: Backend dir not found at $BACKEND_DIR — set BACKEND_DIR"
lsof -i :8081 2>/dev/null | grep LISTEN
lsof -i :3000 2>/dev/null | grep LISTEN
which bun && bun --version
Read the frontend package.json to find available start scripts (e.g., start:local, start:dev, start:staging). Read the backend package.json to find backend start scripts (e.g., start:local, start:dev).
Start both backend and frontend for local development.
Start backend (background):
cd "${BACKEND_DIR:-../backend-v2}" && IS_OFFLINE=true bun run start:local
Run this in the background using the Bash tool with run_in_background: true.
Wait for backend (up to 30 seconds):
for i in $(seq 1 30); do
curl -sf http://localhost:3000/graphql -X POST \
-H "Content-Type: application/json" \
-d '{"query":"{ __typename }"}' > /dev/null 2>&1 && echo "Backend ready" && break
sleep 1
done
Start frontend (background):
bun run start:local
Run this in the background using the Bash tool with run_in_background: true.
Verify frontend (up to 60 seconds — Metro bundler can be slow):
for i in $(seq 1 60); do
curl -sf http://localhost:8081 > /dev/null 2>&1 && echo "Frontend ready" && break
sleep 1
done
Report status table.
Use when the backend is already deployed and you only need the frontend.
bun run start:dev
Run in background.
Verify:
for i in $(seq 1 60); do
curl -sf http://localhost:8081 > /dev/null 2>&1 && echo "Frontend ready" && break
sleep 1
done
Check AWS credentials (discover profile from backend package.json scripts or remote-routine
~/.aws/config):
aws sts get-caller-identity --profile {aws-profile} 2>/dev/null
If this is an interactive local session and credentials are expired, refresh the backend's local AWS signin flow. In headless sessions, rely on the configured environment-backed AWS profile and do not start an SSO browser/device flow.
Start:
cd "${BACKEND_DIR:-../backend-v2}" && IS_OFFLINE=true bun run start:local
Run in background.
Verify:
for i in $(seq 1 30); do
curl -sf http://localhost:3000/graphql -X POST \
-H "Content-Type: application/json" \
-d '{"query":"{ __typename }"}' > /dev/null 2>&1 && echo "Backend ready" && break
sleep 1
done
Kill all local services.
# Kill frontend (Metro bundler)
lsof -ti :8081 | xargs kill -9 2>/dev/null || echo "No frontend process on :8081"
# Kill backend (Serverless Offline)
lsof -ti :3000 | xargs kill -9 2>/dev/null || echo "No backend process on :3000"
# Stop Docker if running
cd "${BACKEND_DIR:-../backend-v2}" && docker compose down 2>/dev/null || true
sleep 2Check what is currently running and responsive.
echo "=== Port Check ==="
echo -n "Frontend :8081 — "; lsof -i :8081 2>/dev/null | grep LISTEN > /dev/null && echo "LISTENING" || echo "NOT LISTENING"
echo -n "Backend :3000 — "; lsof -i :3000 2>/dev/null | grep LISTEN > /dev/null && echo "LISTENING" || echo "NOT LISTENING"
echo ""
echo "=== Health Check ==="
echo -n "Frontend :8081 — "; curl -sf -o /dev/null -w "%{http_code}" http://localhost:8081 2>/dev/null || echo "UNREACHABLE"
echo -n "Backend :3000 — "; curl -sf -o /dev/null -w "%{http_code}" http://localhost:3000/graphql -X POST -H "Content-Type: application/json" -d '{"query":"{ __typename }"}' 2>/dev/null || echo "UNREACHABLE"
echo ""
echo "=== Docker ==="
docker compose -f "${BACKEND_DIR:-../backend-v2}/compose.yaml" ps 2>/dev/null || echo "No Docker services running"
Report results as a table:
| Service | Port | Listening | Responsive |
|---|---|---|---|
| Frontend (Metro) | 8081 | YES/NO | YES/NO |
| Backend (Serverless Offline) | 3000 | YES/NO | YES/NO |