メニュー
Run this repository's quality and validation workflow. Use when the user asks for quality checks, pre-commit, linting, formatting, type checking, test validation, or before reporting code changes as done.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Rewrite a candidate's resume tailored to one specific JD using a hiring-recon report, emit it as a rendercv YAML, then render to PDF. Reorders jobs/bullets and adjusts language to incorporate JD keywords without inventing experience. Outputs one YAML (source of truth, user-editable) plus a .pdf published alongside it.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Stage current changes and create a Conventional Commits-style commit matching this repo's history. Use when the user says "commit", "commit this", or asks for a commit message. Pre-commit hooks will run automatically.
Fetch current documentation before answering library, framework, SDK, API, CLI, cloud-service, version-migration, setup, or configuration questions. Use when the user asks about external technical docs, package APIs, framework behavior, or dependency upgrades; do not use for pure repo refactors, business-logic debugging, or general programming concepts.
Upgrade Python backend dependencies to their latest compatible versions. Resolves the lockfile with `uv lock --upgrade`, syncs the venv, bumps the matching `>=` pins in `backend/pyproject.toml` and `ruff-pre-commit` rev in `.pre-commit-config.yaml`, runs the backend unit tests, rebuilds the backend Docker image if requested, opens a PR with the change (watching CI for upgrade fallout), and reports what moved vs. what stayed pinned by transitive constraints. Use when the user says "upgrade backend libs", "bump backend deps", "update Python dependencies", or after they've manually run `uv lock --upgrade` and want the pyproject/config files reconciled.
Upgrade the Next.js frontend's pnpm dependencies to their latest versions in verified waves. Inventories with `pnpm outdated`, removes verified-unused deps, batches safe minor/patch bumps, handles the @langchain/react + langgraph-sdk lockstep pair, takes majors one commit at a time with registry peer-dep checks, gates every wave on type-check + lint + unit tests + build + an agent-browser check against baseline screenshots, then dedupes, audits for duplicate versions, and opens a PR. Use when the user says "upgrade frontend libs", "bump frontend deps", "update npm/pnpm packages", or `pnpm outdated` shows a backlog. Backend deps are a separate flow (`upgrade-backend-deps`).
| name | quality |
| description | Run this repository's quality and validation workflow. Use when the user asks for quality checks, pre-commit, linting, formatting, type checking, test validation, or before reporting code changes as done. |
Run validation the way CLAUDE.md defines it for this repo.
After code edits, validate all modified and untracked files once at the end:
pre-commit run --files $(git ls-files --modified --others --exclude-standard)
If hooks auto-fix a file, re-read that file before summarizing the result.
When the user asks for a full quality pass or broad repository validation, run:
pre-commit run --all-files
cd backend && uv run pytestcd backend && uv run pytest tests/path/test_file.pycd backend && uv run pytest -m integrationcd frontend && pnpm testcd frontend && pnpm type-checkcd frontend && pnpm qualityUse targeted checks before the changed-file pre-commit run when they give faster, more relevant feedback.
If integration tests or visual checks need services and docker ps shows the stack is not running, remind the user to run docker compose up -d. Do not silently start the stack yourself.