「rev」の検索結果

依存関係更新のローカル差分やPRをレビューする。人間・エージェントによる更新、Dependabot・Renovateの更新PRを対象に、upstreamの変更と利用箇所を照合し、根拠付きの判定を返す。

Use when arranging the project quality-check or investigating a concrete unresolved code concern

日本語の概要は準備中です。原文の説明を表示しています。

Use before implementing any feature, behavior change, or refactor - settles requirements and design, then gets the design independently reviewed and approved by the user before code is written

日本語の概要は準備中です。原文の説明を表示しています。

ローカルでニュースを生成しブラウザで動作確認する。fetch_news.py実行→http.server起動→index.html/archivesを確認→生成物の差分を戻す。「ローカルで確認」「プレビューして」「動作確認」と言われたら使う。UI変更時は必須。

Research a specific company before applying or interviewing by gathering facts from primary and official sources, recording the source and date behind every claim, and keeping anonymous or unverifiable material clearly separated from confirmed fact. Use when a user asks what a company actually does, how it makes money, what its published conditions are, whether a posting matches the company's own disclosures, or what to verify before an interview; do not use to predict hiring outcomes, to repeat review-site content as fact, or to bulk-crawl sites that prohibit automated access.

日本語の概要は準備中です。原文の説明を表示しています。

Help job seekers use Otameshi Tenshoku to prepare profiles and applications, clarify trial conditions, plan learning visits or paid trial work, and reflect on the experience. Use when a candidate wants to apply for, prepare for, negotiate the scope of, or review an otameshi work experience; do not use to predict whether they will be hired or to judge their aptitude, to state fees, contract terms, or service conditions from memory, or to submit an application, update a profile, or send a message on their behalf. Employer-side requests belong to the employer skills (trial-work-design, trial-listing-draft, applicant-reply and others).

日本語の概要は準備中です。原文の説明を表示しています。

Help a user talk through whether to change jobs, stay, or change something in their current work, starting from uncertainty, distress, a vague sense of stagnation, an offer in hand, a counter-offer from the current employer, or pressure from family or colleagues. Clarify what matters, separate deadlines that order the next steps from the decision itself, compare conditional options, and agree on a small next step and a time to revisit it. Use when someone asks whether they should quit, wonders whether leaving is just running away, has second thoughts after receiving an offer or being asked to stay, feels stuck because others say it would be a waste, wants to leave soon after joining, or wants advice before deciding to start a job search; do not make the final stay-or-leave decision, evaluate offer terms, plan the resignation, or predict hiring outcomes.

日本語の概要は準備中です。原文の説明を表示しています。

Lay out how a job search will actually run alongside a current job: the hours available each week and what they go to, how weekday daytime slots for interviews will be found, which routes to use (direct applications, job boards, scout sites, agents, referrals, public employment services) and what each one discloses to whom, how to keep the search from reaching the current employer through public profiles or workplace equipment, a single tracker of every application's stage, next action, and deadline, and a date and conditions for reviewing, reducing, or pausing the search. Use when someone has decided to start looking, or to gather information while employed, and asks how to fit it in, which routes to use, whether the applications they are running fit the time they have, or how to keep track of them; do not use to decide whether to change jobs, to pick or rate employers or job postings, to predict outcomes, or to send applications, publish profiles, or contact agents on the user's behalf.

日本語の概要は準備中です。原文の説明を表示しています。

Debrief a finished Otameshi Tenshoku trial from the employer's side: set the observed facts against the completion criteria agreed before the start, keep expectations added afterwards, second-hand or off-the-job observations and the company's own late or missing support apart, settle the hours actually worked separately from any evaluation, and draft feedback to the candidate that states facts, support gaps and what happens next without promising a hire or continuation the company has not decided. Use when a hiring manager, recruiter or small-business owner wants to review a trial, decide what to tell the candidate, or work out the settlement after a shortfall; do not use to judge the candidate's aptitude or predict a hire, to cut pay or demand unpaid rework because of dissatisfaction, to compare candidates, or to send the feedback, pay, or update records on the user's behalf.

日本語の概要は準備中です。原文の説明を表示しています。

Go through an interview that has just finished and sort out what happened: the questions asked and how fully they were answered, which of them were prepared for and which came from the submitted documents, the reverse questions still unanswered, what the employer said about conditions and whether any of it was in writing, and when a result was promised. Use when a user has just come out of an interview and wants to record it while it is fresh or to work out what to fix before the next round; do not use to judge how it went, to estimate whether they will pass, or to read anything into the interviewer's manner.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare for a Japanese job interview by working from the documents already submitted: find where an interviewer will dig in (claims the applicant cannot back up, work described in the first person plural, outcomes with no measure, gaps or overlaps in the employment history, must-have requirements the documents never answer), and turn them into questions to prepare evidence for. Use when a user has an interview scheduled and wants to know what will be asked and what to have ready, or wants to prepare reverse questions from earlier company research; do not use to predict whether they will pass, to write answers containing experience they did not report, or to schedule or contact anyone.

日本語の概要は準備中です。原文の説明を表示しています。

Assemble a Japanese shokumu-keirekisho (career history document) from an experience inventory, choosing between reverse-chronological, chronological, and skills-based layouts, mapping the target posting's requirements to the experiences that can support them, and drafting the summary, work history, skills, and self-PR so that each sentence stays within what its evidence supports and confidential details are abstracted. Use when a user wants to write or rebuild a whole shokumu-keirekisho for a specific posting or as a general version, or wants to decide which experiences to include and in what order; do not use to invent experience, numbers, titles, or qualifications, to predict whether it will pass screening, to fill in a rirekisho form, or to submit it anywhere.

日本語の概要は準備中です。原文の説明を表示しています。

Triage a single GitHub PR by PR number. Check out the PR's branch, detect conflicts with the target branch via `gh pr status` (and label the PR with `cc-resolve-conflict` if any are found), collect unresolved review comments and CI status and judge only whether each item must be fixed, then take action (add cc-fix-onetime label if fixes are needed; if release-ready, add cc-release-ready label for an Epic PR marked `cc-epic-issue` instead of merging, otherwise merge the PR).

日本語の概要は準備中です。原文の説明を表示しています。

GitHub PRの未解決レビューコメント・会話コメント・CIステータスを確認し、修正プランを作成します。

Update an existing GitHub Issue's description based on the issue number. Reads all issue comments and reflects any items not yet captured in the description. After refreshing the description, reviews it for remaining ambiguities or unclear requirements and posts any open questions as a follow-up 確認事項 comment.

日本語の概要は準備中です。原文の説明を表示しています。

Keep GPT-5.6 and other coding-agent work proportional to the request by locking scope, choosing the smallest sufficient implementation, matching verification to risk, and stopping when success is proven. Use for implementations, bug fixes, refactors, reviews, or maintenance where scope creep, speculative abstractions, unrelated cleanup, repeated test runs, unnecessary dependencies, or polishing beyond the request are risks.

日本語の概要は準備中です。原文の説明を表示しています。

Shakes your mental models with critical rigor, challenges assumptions, exposes blind spots, and provides multi-perspective insights as a strict thinking mentor. Deliberately breaks format conventions to stimulate genuine cognitive discomfort. Use when you want to stress-test an idea, shake your mental model, ask to challenge my assumptions, find blind spots, deepen my thinking, or request critical review with phrases like yusaburi or what do you think of this plan.

日本語の概要は準備中です。原文の説明を表示しています。

Survey related literature for a research topic or paper draft. Finds relevant papers, identifies citation gaps, and suggests key references. Use for "find related work", "survey papers on X", "what papers should I cite". 旧名 survey-literature。

日本語の概要は準備中です。原文の説明を表示しています。

研究概要・中間発表予稿の「研究としての筋」を、論理の鎖(L1背景→L2関連研究と限界→L3課題(差分)→L4仮説→L5評価→L6位置づけ)として1リンクずつ採点し、さらに端点間の整合(掲げた構成概念=旗と評価指標=物差しのズレ=construct validity)を照合するスキル。各文の綺麗さ(→articulation-check)でも汎用の弱点(→weakness-analyze)でもなく「リンク間が繋がっているか／旗と物差しが一致しているか」を見る。骨子・位置づけ・仮説・課題設定・研究の一貫性を見てほしい、research framing を見て、と言われたとき。旧名 research-framing-check。

論文・研究概要の体裁・形式を自動チェック。LaTeX(.tex)・Word(.docx)・PDF(.pdf)に対応。表記ゆれ・参考文献体裁・相互参照整合性・未記入セクション等を検出。1〜2ページの概要・梗概・アブストラクト（固定尺）は --fixed（またはページ数で自動判定）で紙面配分（参考文献が本文を圧迫していないか等）も診断する。提出直前の最終確認に使用。卒論・研究論文・学会投稿論文・研究概要すべてに対応。旧 abstract-format-check を統合。

Detect articulation gaps in documents using 5W analysis and provide concrete improvement suggestions. Identifies what's missing in explanation, not what's wrong. Default runs detection + improvement; use --check-only for detection only. 旧名 check-articulation。

日本語の概要は準備中です。原文の説明を表示しています。

Trading strategy patterns for the HoneyComb job position exchange. Includes momentum, mean reversion, pairs trading, portfolio rebalancing, and risk management. Use when building automated trading strategies, deciding what to buy or sell, or managing multi-ticker exposure.

日本語の概要は準備中です。原文の説明を表示しています。

Use OpenAI Codex CLI as a peer collaboration partner — same standing as Claude, not a one-shot tool. Bring Codex in EARLY (ideation, framing decisions, stuck moments), not only for late peer-review. Hand it strategic context (target, research, draft, reasoning), iterate conversationally over ~3-8 turns, converge before surfacing to the human. Invoke when the user says "check / iterate / ideate with Codex" or "ask Codex" — and proactively when stuck between two reasonable framings, pressure-testing a load-bearing claim or structure, or about to ask the human to pick between options two agents could resolve.

日本語の概要は準備中です。原文の説明を表示しています。

Designs pegRNAs and nicking guides for prime editing (PE) -- choosing the nick/strand, tuning the primer-binding site (PBS) and reverse-transcription template (RTT) as a per-locus panel, selecting the PE system (PE2/PE3/PE3b/PE4/PE5/PEmax/PE7), adding MMR-evading and PAM-disrupting silent edits, appending epegRNA 3' motifs (tevopreQ1/mpknot), and ranking with PRIDICT/DeepPrime. Covers twinPE/PASTE for large insertions and the prime-vs-base-editing decision. Use when designing a scarless point mutation, small insertion/deletion, or any of the 12 base conversions without a double-strand break, when efficiency is low and MMR inhibition or pegRNA stabilization is needed, or when routing a large insertion to an integrase method. Generic guide scoring and base editing are separate skills.

日本語の概要は準備中です。原文の説明を表示しています。