50 件 ・ 関連度順
概要と使いどころ
Audits, preserves and recovers local Git state before cleanup: unpushed or wrong-branch commits, dirty worktrees, duplicate clones, stashes, dangling commits, squash-merge uncertainty. Use when the user fears lost work, wants to recover a commit, asks if a branch is actually merged, asks whether a branch, worktree or clone is safe to delete, or wants one clean main (误删分支 / 还有没有丢的东西). Not for GitHub PR operations.
日本語の概要は準備中です。原文の説明を表示しています。
使用 GitHub CLI (`gh`) 执行非交互式 GitHub 协作与自动化任务（PR、Issue、Actions、Release、API 查询/修改）。当用户要求“用 gh 命令完成任务”、需要结构化 JSON 输出（`--json`/`--jq`）、批量处理 PR/Issue（如“批量 review 多个 PR”）、按策略合并（如“检查通过后自动 squash 合并”）时使用此 skill。
日本語の概要は準備中です。原文の説明を表示しています。
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
日本語の概要は準備中です。原文の説明を表示しています。
Use when animating characters or objects in Blender through Python, a bouncing ball, walk or run cycle, jump, acting shot, lip sync, eye darts or facial animation, blocking in stepped keys, splining, polish, timing and spacing, arcs, overlap, squash and stretch, graph editor handles, slotted actions or NLA layers, staging a playblast, or when animation looks floaty, stiff, slides, pops, chatters, the subject is too small in frame, or a knee pops and needs an expert review.
日本語の概要は準備中です。原文の説明を表示しています。
Rebase, squash, or rewrite history without losing work or breaking shared branches. Use before any history rewrite.
日本語の概要は準備中です。原文の説明を表示しています。
固件 / IoT 渗透链。从拿到一坨 .bin / .img 开始，闭环走完逆向 → 提取 → 模拟 → 利用。 方法论遵循 OWASP FSTM 九阶段；工具链以 binwalk v3、unblob、EMBA、Firmadyne、AFL++ 为主。 适用场景：路由器/摄像头/智能家居固件审计、固件升级包逆向、IoT CVE 复现、嵌入式 0day 挖掘。 触发关键词：固件、firmware、IoT、binwalk、unblob、UART、JTAG、squashfs、UBI、JFFS2、Firmadyne、QEMU 全系统仿真、EMBA、固件渗透、路由器固件、嵌入式漏洞利用、bootloader、NVRAM、FAT、firmware analysis toolkit。
日本語の概要は準備中です。原文の説明を表示しています。
Cartoon art direction for Blender with squash-stretch readable shapes, bold colors, and graphic silhouettes for games and animation.
日本語の概要は準備中です。原文の説明を表示しています。
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
日本語の概要は準備中です。原文の説明を表示しています。
Modern Git workflows, best practices, and commands. Use when the user asks about Git branch management (git switch vs checkout), file restoration (git restore), fixup commits, autosquash rebasing, git worktrees, rerere, force-with-lease, repository cleanup (git clean, stale branches, bloat analysis), history navigation (revision syntax, range notation, pickaxe search), recommended global git config, or GitButler and the but CLI.
日本語の概要は準備中です。原文の説明を表示しています。
Set up, reshape, title, publish, version or land an Anabasis pull request the way the operator wants it: where it goes on the stack, when to regroup a back-and-forth history into a few finished commits, how the body reads, who pushes, and when a version tag is attached. Use when asked to set up or append to a PR, regroup or squash its commits, rewrite its title or body, push it, cut a release for it, or merge a stack.
日本語の概要は準備中です。原文の説明を表示しています。
Merge a Git source branch, including its still uncommitted changes, into a target branch through a regular merge, a rebase with fast-forward, or a squash merge, resolving merge conflicts semantically, check that the source branch landed, and emit a MERGED, CONFLICT, or FAILED verdict. Use when the user calls to "merge", "integrate", or "land" a branch.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a feature branch is complete and its history must be cleaned up before merging back to dev — as the final step before creating or merging a PR, or when the user says "prepare for merge", "squash the branch", "clean up branch history", or "/prepare-merge".
日本語の概要は準備中です。原文の説明を表示しています。
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
日本語の概要は準備中です。原文の説明を表示しています。
After an issue's PR has squash-merged on GitHub and its issue has closed: fast-forward the default branch, remove the issue-numbered nested worktree (.worktrees/<issue#>), and delete the local feature branch. Use when the user says to finish, tear down, or clean up a lane or worktree for a merged issue.
日本語の概要は準備中です。原文の説明を表示しています。
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding, reviewing, squashing, deploying, or rolling back Pharos D1 migrations or schema cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Phase 3 of the feature-pipeline suite. Use this after /fp-plan has received explicit user approval and printed the M2-plan stop hook — when you need to translate an approved numbered plan into committed, pushed code. Triggers on: "implement the plan", "start coding", "commit the plan", "write the code", "fp-implement", "Phase 3", "plan is approved let's code", "next step after plan", "execute the plan", "apply the plan", "make the changes". Reads planApproved and branch from state; refuses to run if approval hasn't been recorded. Commits one atomic change per plan step, pushes after each commit, handles obstacles cleanly, and hands off to /fp-review when done. Never squashes or skips steps — the one-commit-per-step rule keeps the review history readable and rollback surgical.
日本語の概要は準備中です。原文の説明を表示しています。
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
日本語の概要は準備中です。原文の説明を表示しています。
Audits Google Cloud Filestore instances across projects for disaster recovery readiness (missing or stale backups), security access governance (overly permissive NFS export rules, 0.0.0.0/0 exposure, missing ROOT_SQUASH), and reliability compliance (Physical Zone Isolation PZI and Physical Zone Separation PZS). Use when assessing storage health posture, auditing NFS export permissions, identifying unprotected file shares, or validating zone failure domains. Don't use for Cloud Storage buckets, Persistent Disk, or NetApp Volumes.
日本語の概要は準備中です。原文の説明を表示しています。
GitHub patterns using gh CLI for pull requests, stacked PRs, code review, branching strategies, and repository automation. Use when working with GitHub PRs, merging strategies, or repository management tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Land a ready branch - push, PR, pinned CI watch, squash-merge, issue verification, cleanup. Use for every PR landing; encodes the run-ID pinning and cleanup discipline.
日本語の概要は準備中です。原文の説明を表示しています。
Use when morphir-scala work needs environment diagnostics or build/network/sandbox unblocking; reference repository management; branch lifecycle refresh after squash-merging a target branch into main; Morphir IR spec/schema sync or export; or task-tracking configuration and beads mode resolution.
日本語の概要は準備中です。原文の説明を表示しています。
Git branching strategies, conflict resolution, rebase workflows, monorepo patterns, and advanced operations like cherry-pick, bisect, and reflog recovery. Activate on "git", "branching strategy", "merge conflict", "rebase", "cherry-pick", "monorepo git", "git bisect", "git reflog", "squash commits". NOT for GitHub Actions CI/CD (use github-actions-pipeline-builder), GitHub API/webhooks, or PR review processes (use code-review-checklist).
日本語の概要は準備中です。原文の説明を表示しています。
When writing a commit message, branch name or squash title — measure the repo's own convention first, Conventional Commits as fallback — even on a bare 'commit this'.
日本語の概要は準備中です。原文の説明を表示しています。