336건 · 관련도순
Sort incoming issues and pull requests, verify their claims, and assign clear triage states. Record missing information, decisions needed, and actionable handoff notes so maintainers can see which items are ready for work.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Capture ideas for videos, articles, businesses, and small projects in separate files, with entry numbers and source details. The skill commits and pushes the additions to a Git repository for later review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Assess one selected GitHub issue from user needs, security, and relevant design or documentation perspectives. Produce an advisory recommendation, a proposed scope brief, and a suggested reply for a human maintainer to consider.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Gather news from Chinese industry media, filter it by topic or creator focus, and produce a structured daily briefing with summaries, context, and practical ideas for articles or videos.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Backfill labels across oh-my-hermes issues and pull requests. Run manually to sweep everything currently unlabeled, or pass a number to triage one item. Use when issues and PRs have accumulated without labels, after adding a new label to .github/labels.yml, or before a release when the backlog needs to be readable by area.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review oh-my-hermes pull requests that have not been reviewed at their current head commit. Run manually to sweep the open backlog, or pass a number to review one PR. Applies the repository's REVIEW.md policy and posts findings as a GitHub review with inline comments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Mine Claude Code session logs for skill idea candidates. Use when running the weekly skill generation pipeline to extract, score, and backlog new skill ideas from recent coding sessions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Record and analyze post-trade outcomes for signals generated by edge pipeline and other skills. Track false positives, missed opportunities, and regime mismatches. Feed results back to edge-signal-aggregator weights and skill improvement backlog.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided journey from a live website that underperforms to a prioritized, evidence-backed backlog of conversion, usability, message, and speed fixes - each shipped as a testable experiment. Orchestrates eight skills phase by phase - cro-methodology, ux-heuristics, refactoring-ui, web-typography, storybrand-messaging, high-perf-browser, made-to-stick, design-everyday-things - asking the user questions at every decision point and recording results in the project docs/ folder (WEBSITE.md, DESIGN.md, IMPROVE-WEBSITE-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a landing page that isn't converting, diagnose why visitors leave, audit for clarity and usability, or says 'the homepage feels off but a redesign didn't help'. No site yet, create-website; converts but needs traffic, grow-website; if the friction is in a product app, not the marketing site, improve-app; if one specific flow leaks, conversion-optimization. For one framework in isolation, invoke that skill directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Summarizes open pull requests into a blockers-first standup digest. Activates when the user asks to summarize open PRs, find blocked pull requests, generate a PR standup, or triage review backlog from a PR export.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a visual novel: a branching script, character and background display, a text box with choices, save/load, backlog, and skip/auto. Use for a VN, dating sim, or branching story game.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scrum-inspired paper review, revision, and R&R workflow. Handles docx/tex/md/PDF in English or Chinese. Auto-detects manuscript stage, estimates sprint count, runs multi-lens review (Contribution/Rigor/Writing/Editor), generates prioritized revision backlog, exports MD/DOCX/PDF/HTML reports. Use when asked to review a paper, revise based on reviewer comments, handle R&R, respond to peer review, plan paper revision sprints, or when user types /ps or /papersprint.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Classify XQUIC GitHub issues with an evidence-backed L1-L4 resolution-complexity label while keeping validity, priority, severity, and disposition separate and skipping uniquely labeled issues unless the user explicitly forces a recheck. Use when triaging one issue or a batch of issues, creating an issue-complexity backlog, or applying or correcting L1-L4 GitHub labels.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
On-demand RAI planner reference pack covering Phase 1 capture, Phase 2 risk classification and the optional Mural board bootstrap, Phase 5 impact assessment, and Phase 6 review and backlog handoff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Security planning and plan-drift analysis for STRIDE, standards, controls, backlog handoff, current findings, and TM7 generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Software supply chain security reference for OpenSSF Scorecard, SLSA, Sigstore, SBOM, and posture/backlog taxonomies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drafts or opens a GitHub pull request, runs changed-area preflight checks, and commits validated preflight repairs, and routes Azure DevOps repositories to the backlog-management pull request protocol. Use when a user asks to prepare, create, or update a pull request on GitHub or Azure DevOps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performance, load, and reliability (SLO/SRE) planning for production readiness. Use when defining service level objectives, load characterization, capacity, latency budgets, stress/soak/spike test plans, false-positive baselines, and reliability targets. USE FOR: SLO/SLA definition, load testing plan, performance budget, capacity planning, reliability/SRE backlog, latency targets, error-budget policy. DO NOT USE FOR: executing load tests (use Azure Load Testing tooling), security threat modeling, RAI assessment, privacy/compliance planning, or authoring/restating PRD requirements (cite the PRD's existing NFR/FR ids instead).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage a raw bug report into something a team can act on — clean repro steps, a defensible severity/priority, environment, likely area/owner, and duplicate check. Use when asked to triage this bug, set severity and priority, is this a P1, or clean up this bug report for the backlog. Produces the normalized repro, a severity and priority with the reasoning (impact × frequency × workaround), the environment/metadata, a suspected component and owner queue, and a duplicate/related-issue check — flagging when info is missing rather than guessing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit and prioritize performance work through bounded-work and forward-progress checks. Use when asked to find performance issues, investigate freezes/500s/OOMs, review retries or polling for no-progress loops, rank a performance backlog, or implement the next simple performance fixes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refine an existing Agiflow task into an unambiguous, testable specification without expanding its intended outcome. Use when a task is vague, lacks acceptance criteria, has unclear scope or dependencies, or is not ready for backlog grooming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose stalled, blocked, overloaded, or unhealthy Agiflow projects and recommend specific corrective actions. Use for project health checks, blocked work, conflicting priorities, obsolete tasks, overloaded assignees, or an unmanageable backlog.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.