「pre-commit」の検索結果

Pre-commit review: security scan, quality gates, auto-fix.

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

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.

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

Automate doc generation with JSDoc/TSDoc, linters, and pre-commit hooks. Use when setting up markdownlint, configuring doc linting pipelines, integrating JSDoc/TSDoc, or building automated documentation workflows.

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

Pre-commit review: security scan, quality gates, auto-fix.

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

GitHub workflow for ToolUniverse - push code safely by moving temp files, activating pre-commit hooks, running tests, and cleaning staged files. Use when pushing to GitHub, fixing CI failures, or cleaning up before commits.

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

MCP Agent Mail - Mail-like coordination layer for multi-agent workflows. Identities, inbox/outbox, file reservations, contact policies, threaded messaging, pre-commit guard, Human Overseer, static exports, disaster recovery. Git+SQLite backed. Python/FastMCP.

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

Security-Scanner Agent fuer fabrikIQ und andere Projekte. Fuehrt umfassende Sicherheitspruefungen durch. Trigger bei: (1) Pre-commit Validation, (2) PR-Creation, (3) Weekly Security Audits, (4) Nach Dependency-Updates, (5) Vor Production Deployments. <example> Context: User moechte vor einem Commit sicherstellen, dass keine Secrets committed werden. user: "Ich will gleich committen. Pruefe mal auf Secrets." assistant: "Ich starte den security-scanner Agent, um den Code auf API Keys, Tokens und andere Secrets zu pruefen." <Task tool call to security-scanner agent> </example> <example> Context: Weekly Security Audit des fabrikIQ-Projekts. user: "Fuehre den woechentlichen Security-Scan durch." assistant: "Ich fuehre einen vollstaendigen Security-Scan durch: Secret Detection, Dependency Audit, OWASP Patterns, Security Headers und Rate Limiting." <Task tool call to security-scanner agent> </example> <example> Context: User hat Dependencies aktualisiert und will Vulnerabilities pruefen. user: "Ich habe npm update und pip install -U gemacht. Gibt es Sicherheitsprobleme?" assistant: "Ich scanne die aktualisierten Dependencies auf bekannte Vulnerabilities mit dem security-scanner Agent." <Task tool call to security-scanner agent> </example> <example> Context: PR-Review mit Security-Fokus. user: "Review den PR #42 auf Security-Probleme." assistant: "Ich analysiere die geaenderten Dateien im PR auf Security-Patterns: SQL Injection, XSS, Hardcoded Credentials und fehlende Input-Validation." <Task tool call to security-scanner agent> </example>

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

Establish and enforce coding standards, best practices, and architectural patterns across the codebase using linters, formatters, and code review processes. Use when setting up ESLint/Prettier, configuring linting rules, creating code style guides, implementing pre-commit hooks, establishing naming conventions, enforcing TypeScript strict mode, maintaining consistency, conducting architecture reviews, or defining team coding standards.

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

快速編碼防災工作流。USE FOR：任何會修改 .md / .json / .ts / .js / .ps1 等文字檔的工作。目標是在每次編輯後立即檢查 touched files 是否出現 UTF-8 BOM、U+FFFD 或 mojibake，並在收工前再檢查一次，避免中文檔被整檔寫壞後才在 pre-commit 才發現。

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

Write a rigorous, decision-grade experiment spec — falsifiable hypothesis, primary metric, guardrails, randomisation unit, exposure definition, method (A/B, holdout, switchback, quasi-experiment, MAB), MDE/duration plan, peek policy, validity threats, and pre-committed decision rule. Platform-agnostic. Load when the user has a candidate experiment and needs to spec it before launch, or says "spec this experiment", "write the test plan", "design this A/B test", "what's the hypothesis", "how big a sample do we need", "how long should we run this", "define the metrics for this test", or when the experimentation orchestrator routes here.

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

Structure git work with atomic commits, conventional messages, short-lived branches, and pre-commit hygiene. Load when committing, branching, resolving merge conflicts, organizing parallel work, or reviewing git history. Also triggers on "git workflow", "commit message", "conventional commits", "atomic commit", "branch strategy", "git worktree", "how should I commit this". Does not replace project-specific hook policies — complements them.

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

Pre-commitment attack on a plan by an agent that did not write it. Use when presenting a feature-deep-dive plan, assigning vision-to-fleet briefs, moving a register to build mode, ratifying a scope list, or coding a new contract or table. NOT for built work or DONE reports (use subagent-dispatch).

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

Improve test value and feedback cost when auditing slow, flaky, redundant or brittle tests; choosing tests during implementation; or reviewing test changes before a commit or PR. Keep ordinary implementation and pre-commit use scoped to the affected behavior, not a repository-wide audit.

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

Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR.

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

End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI. Covers all four build backends (setuptools+setuptools_scm, hatchling, flit, poetry), PEP 440 versioning, semantic versioning, dynamic git-tag versioning, OOP/SOLID design, type hints (PEP 484/526/544/561), Trusted Publishing (OIDC), and the full PyPA packaging flow. Use for: creating Python packages, pip-installable SDKs, CLI tools, framework plugins, pyproject.toml setup, py.typed, setuptools_scm, semver, mypy, pre-commit, GitHub Actions CI/CD, or PyPI publishing.

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

Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.

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

Detects leaked API keys, tokens, passwords, and credentials in code with pre-commit hooks, CI checks, scanning rules, and remediation procedures. Use for "secret scanning", "credential detection", "API key leaks", or "secret management".

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

Use when automating research session rituals in Claude Code with hooks, such as session-start context injection, daily research logging, session-end persistence, or pre-commit guards that block secrets and unverified citations.

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

Design and audit a pricing function for variable-cost agent labor. Choose among per-seat, metered, credits, hybrid, and outcome pricing; name buyer value and cost metrics separately; calculate a reproducible cost floor; require pre-commitment guardrails; and stress-test declared personas. Use for offline pricing-design evidence, not billing implementation or runtime control. NOT for production billing, payment collection, or runtime spend enforcement.

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