4,858 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
Maintainer-only. Use when re-vendoring vendor-skills/BMAD/ against a newer BMAD-METHOD commit — "update BMAD", "re-vendor BMAD", "bump the BMAD pin". Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.
日本語の概要は準備中です。原文の説明を表示しています。
Maintainer-only. Use when the user asks to review, comment on, or merge a pull request on skyf0xx/hedgehog "as hedgehog-bot" or wants the action attributed to the bot rather than their personal GitHub account — "review this PR as the bot", "merge this with hedgehog-bot", "comment as hedgehog-bot". Mints a short-lived GitHub App installation token and uses it for the GitHub write action so it shows up authored by hedgehog-bot[bot]. Not part of the Hedgehog discipline a consuming project copies; this only applies to the Hedgehog repo itself.
日本語の概要は準備中です。原文の説明を表示しています。
Updates a project changelog with entries for changes since the branch diverged from main. Use when about to open a PR, cutting a release, or when the user asks about changelog, release notes, or migration notes.
日本語の概要は準備中です。原文の説明を表示しています。
Meta-skill for creating new stitch-kit skills. Enforces naming conventions, SKILL.md structure, examples format, and the Design-First SOP. Use when adding new framework support, a new domain-specific prompt architect, or any new capability to the stitch-kit plugin.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews code implementations for correctness, security, maintainability with confidence-scored findings (converted from agent)
日本語の概要は準備中です。原文の説明を表示しています。
Tracks infrastructure asset performance with maintenance planning, capital expenditure optimization, and end-of-life valuation. Use when managing infrastructure portfolios, planning capex, or evaluating asset condition.
日本語の概要は準備中です。原文の説明を表示しています。
Structures investor portal organization with document hierarchy, access permissions, and communication archive management. Use when managing investor portals, organizing LP documentation, or maintaining investor communication records.
日本語の概要は準備中です。原文の説明を表示しています。
Implement features, fix bugs, and keep the codebase healthy and maintainable. Works from a defined PBI, issue, or task description.
日本語の概要は準備中です。原文の説明を表示しています。
Writes and maintains user-facing documentation for the SDD plugin. Proactively detects when docs are out of sync with plugin capabilities.
日本語の概要は準備中です。原文の説明を表示しています。
Set up nightly monitoring of subdomain changes, JS file diffs, new endpoints, and CVE matches against in-scope assets, with Discord/Slack/Telegram notifications. Use when the user has an active engagement and wants to be alerted to new attack surface without manual re-recon.
日本語の概要は準備中です。原文の説明を表示しています。
Use when EZ_math_model model selection is unclear after the modeling decision tree, the problem spans multiple domains, or modeler needs several candidate approaches before writing modeling_plan.md.
日本語の概要は準備中です。原文の説明を表示しています。
Use when EZ_math_model multi or hybrid mode needs several domain-specialist subagents to gather outside knowledge, industry context, model theory, or sensitivity-analysis references in parallel.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Step 4 of the PaperOrchestra pipeline (arXiv:2604.05018). ONE single multimodal LLM call that drafts the remaining paper sections (Abstract, Methodology, Experiments, Conclusion), extracts numeric values from experimental_log.md into LaTeX booktabs tables, splices the generated figures from Step 2, and merges everything into the template that already contains Intro + Related Work from Step 3. TRIGGER when the orchestrator delegates Step 4 or when the user asks to "write the methodology and experiments sections" or "fill in the rest of the paper".
日本語の概要は準備中です。原文の説明を表示しています。
Phase 5 of 5 — triage-first review orchestrator; dispatches up to 17 domain checks in parallel and compiles one report. Use only when the user asks to run Phase 5 or review a PR, branch, or set of changes — never trigger automatically after writing code.
日本語の概要は準備中です。原文の説明を表示しています。
After /start-task: park the current clean, pushed feature branch in its own issue-numbered nested worktree (.worktrees/<issue#>) and return the primary checkout to current main, so the next parallel lane can start. Use when the user says to move the branch or task to a worktree or open a parallel lane.
日本語の概要は準備中です。原文の説明を表示しています。
Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)
日本語の概要は準備中です。原文の説明を表示しています。
Maintain skills wiki health - check links, naming, cross-references, and coverage
日本語の概要は準備中です。原文の説明を表示しています。
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants measurable accessibility, performance, responsive, theming, or anti-pattern findings—not when they mainly want an overall UX critique or final visual/detail polish.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate an interface from a UX perspective, assessing hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring and actionable feedback. Use when the user wants an overall design or UX review—not when the main need is measurable accessibility/performance diagnosis, or final micro-detail polish.
日本語の概要は準備中です。原文の説明を表示しています。
Add moments of joy, personality, and surprise through success states, empty states, loading moments, hover details, and celebratory polish once the fundamentals already work. Use when the user wants delight, charm, personality, or memorable micro-interactions—not when the main need is baseline cleanup or stronger visual impact.
日本語の概要は準備中です。原文の説明を表示しています。
Research-backed template refresh workflow for updating existing templates with placeholder verification and rendering validation.
日本語の概要は準備中です。原文の説明を表示しています。
Research-backed JSON Schema refresh workflow for updating existing schemas with validation checkpoints and cross-reference verification.
日本語の概要は準備中です。原文の説明を表示しています。