「commit」の検索結果

Core technical, safety, and maintainability rules for codebase edits. Trigger when: - Writing code, refactoring, modifying files, or creating unit tests. - Proposing commits, reviewing git history, or auditing code quality. - Modifying files in any programming language (e.g. *.go, *.rs, *.py, *.ts, *.js, *.c, *.cpp). - Prompt contains keywords: refactor, build, compile, lint, test, git, commit, rule priority, type safety, error handling, defensive programming.

日本語の概要は準備中です。原文の説明を表示しています。

Goal-directed review of git history for change coherence. Trigger when: - Analyzing project history, reviewing diffs, or checking commit messages for alignment. - Prompt contains: /git-review, git history, commit log, change coherence.

日本語の概要は準備中です。原文の説明を表示しています。

Pre-commit i18n check. Scans changed files for untranslated strings, missing locale keys, and locale sync issues. Fast and focused — only checks what changed. Use before committing or as a review add-on.

日本語の概要は準備中です。原文の説明を表示しています。

Observe the harness itself — (WS1) measure context budget as a deterministic, trendable inventory (tokens per CLAUDE.md / skill / agent, lexical redundancy, per-CI cold-write totals; committed history.jsonl), (WS2) reconstruct the real invocation trace (which skills/agents/tools fired and how they nested) from session transcripts, and (WS-A) roll the per-run CI traces up into a committed weekly usage record (per-skill invocation counts; usage.jsonl) — the usage side of the dead-weight join. Use for "context budget", "how big is CLAUDE.md / our skills", "is the harness bloating", "how do our agent loops actually run", "which skills actually get used", "trace this session", "loop station".

日本語の概要は準備中です。原文の説明を表示しています。

Stress-test plans before committing by imagining they've already failed. Three modes. Diagnostic mode runs a full pre-mortem session — vivid failure scene-setting, six failure categories, the monkey test, and concrete plan adjustments. Review mode checks previous findings monthly for changed probabilities and new failure modes. Alert Triggers mode defines and monitors early warning signals across four trigger categories. Use before any major commitment — strategy, investment, product launch, partnership — or regularly to keep assumptions honest. The planning fallacy is real. The spreadsheet looked great so everyone stopped thinking. This is the antidote. Based on practice by Eterdis (eterdis.com).

日本語の概要は準備中です。原文の説明を表示しています。

Pre-share leak scanner for Claude Code skills (or any folder). Scans BEFORE you publish for secrets (API keys, tokens, private keys, .env values, high-entropy strings), PII (emails/phones), local machine paths (C:\Users\<name>, /home/<name>, /Users/<name>, UNC, internal hostnames), and client/proper-noun names from a LOCAL private dictionary; also flags service-specific code (jira/github/gitlab/slack/salesforce/notion/linear/ stripe/aws/google) that should be split into a dedicated service plugin. Use when the user says "sanitize this skill", "before sharing a skill", "check for leaks", "is this skill clean", "is this safe to commit/publish/ open-source", "scrub secrets", "redact before commit", or "pre-push leak check". Cross-platform, stdlib-only Python, fail-closed.

日本語の概要は準備中です。原文の説明を表示しています。

Use when committing or pushing completed work; automates gate-aware conventional commits with optional signing and CI/CD checks.

日本語の概要は準備中です。原文の説明を表示しています。

Auto-commit changes after a Spec Kit command completes

日本語の概要は準備中です。原文の説明を表示しています。

Run the Tamanu release-branch CUTOFF checks when preparing to cut a new release/X.YY branch: confirm the previous release's hotfixes are merged to main, reconcile the commits since the previous release against the "Merged to main" card list from Linear, and scan for data/reporting/schema changes. Use when the user is cutting a Tamanu release and wants to verify the codebase is ready, wants to check main against the previous release branch, or wants to reconcile commits with a Linear "Merged to main" column (they should paste the card list). Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for verifying an existing release branch's hotfix integrity (see pre-release-checks) or for deciding which tests to run (see scope-tamanu-release-tests).

日本語の概要は準備中です。原文の説明を表示しています。

- Mine GitHub, GitLab and git history for identities, infrastructure and leaked credentials using commit author emails, GitHub code search, the commit… Use when investigating a developer or organisation on GitHub, finding leaked API keys, AWS keys or tokens in code, enumerating org members and their personal repos, or recovering secrets deleted from HEAD but still present in history or forks

日本語の概要は準備中です。原文の説明を表示しています。

Download and verify the seven platform FFmpeg archives produced for one rust-ffmpeg-splitter commit by GitHub Actions and CircleCI. Use when handing completed splitter CI binaries to rust-ffmpeg-sys without mixing commits or incomplete CI runs.

日本語の概要は準備中です。原文の説明を表示しています。

Hardcoded-secret detection — AWS keys, GitHub PATs, Slack tokens, Stripe keys, generic high-entropy strings. Pre-commit (`--staged-only`), explicit paths, or full repo. Use when guarding `git commit`, auditing a repo for leaked credentials, validating no secrets entered the diff before push, or producing a rotation list for an exposed-secret incident.

日本語の概要は準備中です。原文の説明を表示しています。

Git 運用の規律 (branch / worktree 運用、commit / push / pull / rebase / conflict 解決、remote 同期、完了時の統合) を一元的に担う skill。コード変更を伴う依頼・セッション開始・Git 操作の話題のいずれかに該当したら、他より先に必ず最初に使う。ファイルを 1 行でも書き換える依頼なら Git に無関係に見えても発火し、セッション開始・作業再開 (「前回の続き」「何から始めよう」等) でも必ず発火する。発火しないのはコードを読むだけの質問、Git の概念学習質問、doc のサマリ依頼。project 固有ルールでの部分上書きに対応する。

Prepares a DRAFT leadership-meeting briefing pack from the reports, meeting notes, emails and dashboard exports the user provides: one headline, metrics exactly as stated with period and source, decisions the meeting must take, risks as reported, talking points with anticipated questions, a source reference on every line and UNKNOWN where the material is silent. Use when the user asks to "brief the leadership team", "prepare the exec pack", "pull together a briefing for the steering committee", "summarise these reports for the CEO", "what do I tell the board on Monday" or "build the pre-read for the management meeting". Do not use for a formal board or committee paper seeking a resolution, use board-paper-skeleton instead; for a personal one-page prep drawn from the user's own calendar and inbox, use meeting-prep-onepager. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Perform root cause analysis on a bug fix. Use when the user says 'run RCA on [commit/PR]', 'root cause analysis', or 'analyze what caused this bug'. Accepts a commit SHA, PR number, issue, or description of a fix.

日本語の概要は準備中です。原文の説明を表示しています。

Write a clear, conventional commit message from the staged diff.

日本語の概要は準備中です。原文の説明を表示しています。

dotfiles本体を中央 engine で保全commit、no-rebase merge、adapter再生成、submodule整合、pushまで同期する。最上位の親がdotfiles管理下のファイルを変更した作業では、完了時に自動起動する。委譲された担当は起動しない。

dotfiles本体を中央 engine で保全commit、no-rebase merge、adapter再生成、submodule整合、pushまで同期する。最上位のセッションがdotfiles管理下のファイル（グローバルの CLAUDE.md・AGENTS.md・Skill・設定など）を変更した作業では、完了時に自動起動する。自然言語トリガー例: 「dotfilesを同期して」／「dotfilesの変更を保全して」／「adapterを再生成して同期して」／「dotfilesをpushして」。スキル・プラグインのupstream更新確認は check-updates を使い、このスキルはdotfiles本体を扱う。

Use for Self-Rewriting Core: AST analyze, patch, commit.

日本語の概要は準備中です。原文の説明を表示しています。

Incrementally studies git history across tagged or pattern-matched intervals (e.g., creation of planning artifacts like EXECUTION_PLAN_N.md, release tags, or milestone commits). Extracts commit diffs, file churn, and subsystem shifts to track feature evolution and architectural convergence, providing structured feeds for ADR distillation.

日本語の概要は準備中です。原文の説明を表示しています。

Fetch the latest upstream branch and merge it into the current branch, in the pitwall repo — feature branches (`dev-<feature>`) sync from `dev`, and `dev` itself syncs from `master`. Stages the merge, walks through any conflicts interactively, then creates the merge commit directly (signed when the user signs commits). Use whenever the user says "sync", "pull dev", "pull master", "update branch", "merge dev", "merge master", "get latest", or anything about bringing upstream changes into their working branch — even if they don't say the word "skill".

日本語の概要は準備中です。原文の説明を表示しています。

Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

日本語の概要は準備中です。原文の説明を表示しています。

Enforce immediate execution of any commitment made in a reply. Use this skill before finalizing ANY reply that contains a promise to act — phrases like "אדווח", "אעדכן", "אשלח", "אחזור אליך", "I'll send", "I'll report", "I'll follow up", "I'll update". Prevents the agent from saying it will do something and then not doing it.

日本語の概要は準備中です。原文の説明を表示しています。

Configure GitHub secret scanning and push protection, triage secret alerts, and run local pre-commit secret audits. Use when enabling secret scanning, handling blocked pushes, defining custom patterns, or checking a repo for accidental credentials before commit.

日本語の概要は準備中です。原文の説明を表示しています。