7,011 件 ・ 関連度順
概要と使いどころ
Maintainer-only. Use when triaging inbound GitHub issues and pull requests on skyf0xx/hedgehog — "triage the issues", "check the PRs", "review inbound", "what's in the queue". Reads each item read-only, judges it for security and for whether it is real, then fixes and closes or comments and closes. Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.
日本語の概要は準備中です。原文の説明を表示しています。
Use at the start of any session on a project with a build graph (`.hedgehog/hedgehog.db`), and again at every claim/dispatch/verify cycle within it. Owns consuming the build graph — claiming task packets, delegating each to the layer's agent, running `hedgehog verify` to gate the commit, recording debt and decisions, the intent check at an intent's last layer, and when to clear context. Not for a build agent handed an already-claimed packet — that agent never claims, dispatches, or verifies; this skill is the orchestrating session's own.
日本語の概要は準備中です。原文の説明を表示しています。
Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit — this skill matters most when a Correction Protocol fast-forward touches several steps at once and those fixes need splitting back into per-step commits.
日本語の概要は準備中です。原文の説明を表示しています。
当用户因失去(或即将失去)某样东西而做出不成比例的激烈反应,或在损失后急于"扳平"、无法止损时调用。典型触发信号:沉没成本陷阱、赌徒式加注、拍卖中的非理性竞价、无法放弃已投入大量资源的失败项目。不适用于一般的投资估值(用 value-assessment)或从众行为(用 misjudgment-checklist)。
日本語の概要は準備中です。原文の説明を表示しています。
Master entry point for all Stitch design workflows. Routes from user request → design spec → prompt assembly → screen generation → iteration (edit, variants, design systems) → design system extraction → framework conversion (Next.js, Svelte, HTML, React Native, or SwiftUI) → optional quality pass.
日本語の概要は準備中です。原文の説明を表示しています。
Adds a purposeful animation layer to Stitch-generated components — CSS transitions, Framer Motion (React/Next.js), or Svelte transitions. Always respects prefers-reduced-motion.
日本語の概要は準備中です。原文の説明を表示しています。
Reference for string algorithm patterns — KMP, Z-function, Rabin-Karp, Manacher's, string hashing, suffix arrays, and Aho-Corasick. Covers recognition signals, core ideas, Python templates, edge cases, and common mistakes for each technique.
日本語の概要は準備中です。原文の説明を表示しています。
Provides language-specific patterns for TypeScript, Python, and React including idioms, best practices, and common patterns. Use when implementing features in these languages.
日本語の概要は準備中です。原文の説明を表示しています。
Reference patterns for graph algorithm problems including BFS, DFS, Dijkstra, topological sort, union-find, MST, Bellman-Ford, and bipartite checking. Provides recognition signals, Python templates, edge cases, and common mistakes for each technique. Use when solving problems involving graphs, trees, shortest paths, connectivity, or dependency ordering.
日本語の概要は準備中です。原文の説明を表示しています。
Hunt authentication and authorization bypasses — forced browsing, path traversal in auth, header injection, JWT downgrade, OAuth state confusion, role manipulation. Use when an endpoint returns 401/403 but appears reachable.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous AI Sales Development Rep for B2B export — handles lead discovery, BANT qualification, multi-channel outreach (WhatsApp/Email/Telegram), CRM management, and deal pipeline tracking. Built for cross-border trade.
日本語の概要は準備中です。原文の説明を表示しています。
MVVM architecture standards for React/TypeScript frontends with TanStack ecosystem, TailwindCSS, and Shadcn UI.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffolds React/TypeScript frontend components with MVVM architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Step 5 of the PaperOrchestra pipeline (arXiv:2604.05018). Iteratively refine drafts/paper.tex by simulating peer review and applying targeted revisions, with strict accept/revert halt rules. Maintains a worklog and snapshots each iteration so revert is real, not symbolic. TRIGGER when the orchestrator delegates Step 5 or when the user asks to "refine the draft", "iterate on the paper", or "run peer review on this paper".
日本語の概要は準備中です。原文の説明を表示しています。
Executes a QA specification (specs/qa/QA-<N>-<slug>.md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact QA-RESULTS-<N>-<slug>.md. Use only when the user asks to run or execute a QA plan — never trigger automatically.
日本語の概要は準備中です。原文の説明を表示しています。
Run the open-pr e2e fixture through a real review in a fresh subagent, grade it against e2e/checklist.md with a second independent subagent, diagnose each failure to the prompt file that owns it, fix, and repeat until clean or the round budget runs out. Use when changing anything under src/ and you want evidence the review still behaves, not just green unit tests.
日本語の概要は準備中です。原文の説明を表示しています。
Remove the git worktrees open-pr review checked PR code out into, each a full checkout on disk. Use when reclaiming disk space after reviews. Asks first; takes no URL.
日本語の概要は準備中です。原文の説明を表示しています。
Act on the findings a review left on a PR or MR: take or decline each by severity, edit the code, one commit, reply. Use when handed a PR or MR URL that has already been reviewed. Edits real code.
日本語の概要は準備中です。原文の説明を表示しています。
Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks
日本語の概要は準備中です。原文の説明を表示しています。
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
日本語の概要は準備中です。原文の説明を表示しています。
Each routine does one thing and does it well - extract when routines have multiple responsibilities
日本語の概要は準備中です。原文の説明を表示しています。
Design onboarding and activation flows that help users reach value quickly. Use when the user mentions onboarding, getting started, first-time users, activation, aha moments, or new user flows—not when the work is only the empty-state surface itself.
日本語の概要は準備中です。原文の説明を表示しています。
Design security-conscious interfaces that protect users without frustrating them. Use when the user asks about MFA, password UX, breach notifications, trust indicators, secure forms, account recovery, or making security feel safe rather than scary.
日本語の概要は準備中です。原文の説明を表示しています。
Living catalogue of 7 known hazard entries (SE-01 through SE-07) specific to agent-studio: Windows backslash paths, prototype pollution, hook exit codes, async swallowing, ReDoS in glob-to-regex, DST arithmetic, array mutation during iteration. Each entry: symptom, root cause, fix, test assertion.
日本語の概要は準備中です。原文の説明を表示しています。