メニュー
SkillsMP は BenjaminG/ai-skills から 43 件の skill を収集しています。skill を開くとソースと詳細を確認できます。
収集済み skill 43 件中 40 件を表示しています。
Triage a pull request — sort every unresolved review item and failing check into P1 / P2 / Nit with a disposition, for `pr-respond` to act on. Use when triaging a PR, asking what is blocking a PR, or given a bare PR number or URL.
原文の言語: 英語
This skill should be used after pr-feedback triage, when the user has picked which review items to act on and wants them applied and answered — apply the agreed code change per item, then post the reply, reaction, and (for inline threads) thread resolution in…
原文の言語: 英語
Drive every open PR to merge-ready on a self-paced loop, with no `/loop` wrapper. Each tick triages through `pr-feedback --auto confirmed`, which answers and folds through `pr-respond` and `fixup`, then waits for CI and new reviews and goes again until the PR…
原文の言語: 英語
Fold an uncommitted fix into the commit that introduced the code, so the branch reads as if the bug never existed. Finds the introducing commit, runs `--fixup` plus `--autosquash` (or `--amend` at the tip), then force-pushes with lease. Use for every fix on…
原文の言語: 英語
This skill should be used to run a reflective consolidation pass over persistent memory files — orienting on what already exists, gathering recent signal from session logs and transcripts, merging new facts into topic files rather than creating…
原文の言語: 英語
Watch a PR's CI hands-free after a push. A persistent Monitor streams each check as it lands; the skill auto-handles the mechanical (rebase a clean conflict, fix lint) and STOPs on any judgment (failing tests, a stack restack, going ready). Triggers on "watch…
原文の言語: 英語
Publish a pull request with automated type detection, Linear/Jira linking, PR templates, and Slack review message.
原文の言語: 英語
Execute a qa-plan interactively, autonomously driving Chrome via chrome-cdp by default. Each run is posted as its own sub-issue/file under the plan (--tracker linear|github|local), re-verifies every scenario, and surfaces prior runs' open findings. A…
原文の言語: 英語
Interact with a local Chrome browser session via Chrome DevTools Protocol (only on explicit user approval after being asked to inspect, debug, or interact with a page open in Chrome). Pass `--isolated` to drive a sandboxed Chrome with a dedicated profile…
原文の言語: 英語
Draft a manual QA test plan for a pull request, tailored for a PM or QA tester (not a developer). Auto-detects the current PR from the branch, or takes a PR number/URL. Produces steps that can be run with only a browser and the app's admin UI — no terminal,…
原文の言語: 英語
This skill should be used when reviewing someone else's pull request and you want to turn gate / gate-wf findings into posted GitHub comments — each comment drafted through humanizer and posted as a standalone inline comment at its file:line, after one…
原文の言語: 英語
Harness-portable quality gate for branch changes — spawns parallel reviewer subagents (Bug, SOLID, Security, Simplify+Slop, optionally React/a11y/i18n/migration) with tier-scaled adversarial verify, CLAUDE.md/ADR enforcement, and a stable PASS / PASS WITH…
原文の言語: 英語
Workflow-native quality gate for branch changes — parallel reviewers (Bug, SOLID, Security, Simplify+Slop, optionally React/a11y/i18n/migration) with tier-scaled adversarial verify, CLAUDE.md/ADR enforcement, and a stable PASS / PASS WITH NOTES / FAIL…
原文の言語: 英語
This skill should be used to rank evidence-backed product additions or capability changes and recommend one winner, across either the full product or an optional focus such as activation, retention, differentiation, AI, onboarding, or power users. Use…
原文の言語: 英語
This skill should be used when the user wants to find AI-generated code slop — unnecessary comments, defensive checks, `any` casts, and style inconsistencies — in a branch's changes. Produces suggestions only; does not apply edits.
原文の言語: 英語
This skill should be used when the user wants to write their end-of-day / evening "build-in-public" update for a given Linear project — 2-3 impact-focused bullets plus a Next line synthesized from the project's Linear activity and the repo's git/PR shipping…
原文の言語: 英語
Draft Benjamin's daily Slack update for the Naboo team from Linear. Pulls his issues closed since the previous work day (DONE), currently started (IN PROGRESS), and optionally blocked (BLOCKERS), formats them in the team's Slack style, and iterates in chat…
原文の言語: 英語
Specialist for TypeScript backend development including Node.js servers, NestJS applications, APIs, databases (PostgreSQL, MongoDB, Redis), authentication, testing, deployment, server-side code, microservices, database queries, migrations, controllers,…
原文の言語: 英語
Specialist for modern React applications, TypeScript frontend code, UI development, TanStack Query, component creation, CSS styling, responsive design, accessibility, form validation, state management, routing, and performance optimization. Use for ANY work…
原文の言語: 英語
Create and manage Claude Code hooks for automating workflows, validating inputs, and customizing behavior. Use when users request to create hooks, set up automation for tool usage (PreToolUse, PostToolUse), add session context (SessionStart), validate prompts…
原文の言語: 英語
Run parallel quality reviews (React, SOLID, Security, Simplification, Slop) on branch changes and auto-fix issues
原文の言語: 英語
Investigate a High/Urgent bug on Linear and post a structured root-cause comment in the team's format (Root cause → Timeline of PRs → Category → what the fix does → follow-up). Drafts in chat first; posts to Linear only on explicit approval. This skill should…
原文の言語: 英語
Audit and refactor CLAUDE.md, AGENTS.md, and .claude/rules/ files to follow progressive-disclosure principles. This skill should be used when the user wants to reorganize, clean up, or optimize their instruction files and rules by splitting monolithic files…
原文の言語: 英語
Reflect on the work done on the current branch vs main — mine devsql history, git log, and session transcripts for back-and-forths, rollbacks, and wasted time, then interview the user to distill durable lessons into a local-ignored CLAUDE.local.md.
原文の言語: 英語
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
原文の言語: 英語
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a…
原文の言語: 英語
Re-explain a technical concept, code path, or review finding you just produced in plain language, for a reader who is not in that domain. Use when the user says it's "charabia"/gibberish, asks you to "explique simplement", "traduis en clair", "je comprends…
原文の言語: 英語
Build or harden a reliable browser-automation skill through a self-improving loop, with no Anthropic API key. Each iteration runs a headless `claude -p` inner agent that drives a local isolated Chrome via chrome-cdp, reads the run trace, adds one heuristic to…
原文の言語: 英語
Remove signs of AI-generated writing from text and progressively learn the user's personal writing style. Use when editing or reviewing text to make it sound natural and human-written, or when the user says "humanizer init" / "humanizer update: ..." to…
原文の言語: 英語
Extract and reproduce a specific person's coding style from a git repository. Use this skill whenever the user wants to analyze how a teammate codes, build a reusable style profile from someone's commits or PRs, make code generation match a particular…
原文の言語: 英語
Announce that a feature is ready for manual QA on its ephemeral environment by creating a "[PRODUCT QA]" sub-issue on Linear with the QA label applied at creation, so the team's product_bot auto-posts the ephemeral-env links to the #product-qa Slack channel.…
原文の言語: 英語
Investigate a task or conversation from an issue tracker (Linear or Jira) or Slack. Fetch context from the tracker ticket, Slack threads, previous work, and the codebase to understand an issue and plan next steps. This skill should be used when asked to…
原文の言語: 英語
Use Atlassian CLI (acli) to manage Jira work items, projects, and workflows from the command line. Ideal for bulk operations, automation, scripting, and when users request CLI-based Jira interactions. Trigger on requests like "use Jira CLI", "create Jira…
原文の言語: 英語
This skill should be used when implementing code that requires SOLID principles and clean code practices. It provides detailed guidance on Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion principles with…
原文の言語: 英語
Use OpenAI Codex CLI in non-interactive mode for automated code analysis, review, and programmatic task execution. Trigger on requests like "use Codex to analyze", "run codex exec", "codex code review", or when users want AI-powered code analysis without…
原文の言語: 英語
Stage and commit pending changes with an automatically generated concise message. This skill should be used when the user asks to "commit", "stage and commit", "make a commit", or "save changes to git". Does not push or create PRs.
原文の言語: 英語
Use confluence-cli (NPM package) to manage Confluence content, pages, and spaces from the command line. Ideal for documentation workflows, bulk content operations, page migration, and when users request CLI-based Confluence interactions. Trigger on requests…
原文の言語: 英語
Run a structured prompt N times and consolidate via deterministic vote (self-consistency, Wang et al. 2022). Use when output stability matters more than latency — code review, finding extraction, classification, triage. Triggers on "self-consistency",…
原文の言語: 英語
This skill should be used when the user wants a ranked list of the highest-leverage technical or architectural improvements to make to their project, presented as a ranking matrix. The technical counterpart to `innovate`. Triggers on requests like "elevate",…
原文の言語: 英語
Interview user to clarify any topic - exploring codebase, investigating issues, planning features, understanding requirements, or drilling into plans. Socratic questioning to uncover details.
原文の言語: 英語