2,302 件 ・ 関連度順
概要と使いどころ
Investment Committee memo drafting for China-focused PE/IB deals. Adapted from the original ic-memo skill for Chinese market context, terminology, and decision frameworks. Triggers on "A股投委会", "IC Memo", "investment memo China", "投委会材料", "IC memo A-share", or "committee memo [company]".
日本語の概要は準備中です。原文の説明を表示しています。
Commit changes, push to GitHub, and open a PR. Includes quality checks (security, patterns, simplification). Use --quick to skip checks.
日本語の概要は準備中です。原文の説明を表示しています。
TrailSnap 需求规格、Agent 编码交付、提交与 PR 工作流。Use when implementing TrailSnap requirements, managing platform requirements and acceptance criteria, preparing commits, pushing branches, creating pull requests, or monitoring PR CI in this repository.
日本語の概要は準備中です。原文の説明を表示しています。
Detect exposed secrets, API keys, credentials, and tokens in code. Use before commits, on file saves, or when security is mentioned. Prevents accidental secret exposure. Triggers on file changes, git commits, security checks, .env file modifications.
日本語の概要は準備中です。原文の説明を表示しています。
Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.
日本語の概要は準備中です。原文の説明を表示しています。
Catch hardcoded secrets, keys, and tokens before they get committed. Use before any commit and on any file with credentials.
日本語の概要は準備中です。原文の説明を表示しています。
Build and validate .arch/index.json — a committed map from each architectural component of this repository to the real directories and files that implement it, pinned to a git commit, with every path verified to exist. Also detects structural drift between that index and the current code. Use when asked to map a codebase, produce a component or code-ownership index, find which files implement a component, check whether architecture docs are stale, or detect architecture drift after a refactor. Triggers include 'map the codebase', 'component index', 'which files implement X', 'is the architecture still accurate', 'architecture drift', 'refresh the architecture index'.
日本語の概要は準備中です。原文の説明を表示しています。
Review uncommitted code changes to find unreasonable design, unfinished requirements, potential bugs, missed reuse opportunities, and optimization opportunities. Use when the user asks for a review of pending, uncommitted, or unpublished code changes and expects both findings and concrete improvements.
日本語の概要は準備中です。原文の説明を表示しています。
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
日本語の概要は準備中です。原文の説明を表示しています。
Enforce version control best practices for commits, branching, pull requests, and repository security. Use when writing commits, creating branches, merging, or opening pull requests.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-commit changes after a Spec Kit command completes
日本語の概要は準備中です。原文の説明を表示しています。
Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
日本語の概要は準備中です。原文の説明を表示しています。
Git Commit Rules
日本語の概要は準備中です。原文の説明を表示しています。
Create git commits with user approval and no Claude attribution
日本語の概要は準備中です。原文の説明を表示しています。
Commit mesajlarina yapilandirilmis karar trailer'lari ekle. Constraint, Rejected, Confidence, Scope-risk, Not-tested trailer'lari ile karar baglamini koru.
日本語の概要は準備中です。原文の説明を表示しています。
Scan code changes for security vulnerabilities using Bug Hunter-native artifacts and STRIDE context. Use whenever the user asks for PR security review, commit-diff scanning, staged-change security checks, branch-comparison security review, or pre-merge security analysis of changed code.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Git branching strategies, commit conventions, and collaboration workflows. Use when choosing between trunk-based development, GitHub Flow, or GitFlow, implementing conventional commits for automated versioning, setting up Git hooks for quality gates, or organizing monorepos with clear ownership.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used as a mandatory final sanity check before git commit, PR creation, or declaring work done. Triggers on "commit", "push", "PR", "pull request", "done", "finished", "complete", "ship", "deploy", "ready to merge". Catches security vulnerabilities, logic errors, and business rule bugs that slip through despite passing tests.
日本語の概要は準備中です。原文の説明を表示しています。
Best practices for creating GitHub pull requests including conventional commits, PR formatting, and multi-language support (en/ja). Use when creating PRs, writing PR descriptions, or formatting commit messages.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.
日本語の概要は準備中です。原文の説明を表示しています。
Commit, push, and optionally create or update a PR for the current staged changes. Use when the user asks to "ship", "ship it", "ship changes", "commit push and PR", or "ship this".
日本語の概要は準備中です。原文の説明を表示しています。
Recall why a past change was made, drawing on Codex session history when available and falling back to commit diff and surrounding code. Use when the user asks to "recall the rationale", "find the rationale", "look up the rationale", "why did I do X", "why did we do X", "why was this changed", or "find the transcript for this commit".
日本語の概要は準備中です。原文の説明を表示しています。
Stage implementation changes for commit with precise file selection. Use when the user asks to "stage changes", "stage files", "add files to staging", or "prepare changes for commit".
日本語の概要は準備中です。原文の説明を表示しています。
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
日本語の概要は準備中です。原文の説明を表示しています。