pre-commit — for Claude Code pre-commit, caliday, community, for Claude Code, ide skills, refactor, Perform, following, before, commit

v1.0.0

关于此技能

适用场景: Ideal for AI agents that need pre-commit workflow. 本地化技能摘要: # Pre-Commit Workflow Perform the following steps in order before every commit. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

功能特性

Pre-Commit Workflow
Perform the following steps in order before every commit.
Step 1 — Update history in DEV NOTES.md
Add an entry to the "Change History" section (internal docs/DEV NOTES.md).
YYYY-MM-DD — <short description

# 核心主题

pupptmstr pupptmstr
[0]
[0]
更新于: 4/9/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
43
Canonical Locale
en
Detected Body Locale
en

适用场景: Ideal for AI agents that need pre-commit workflow. 本地化技能摘要: # Pre-Commit Workflow Perform the following steps in order before every commit. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

核心价值

推荐说明: pre-commit helps agents pre-commit workflow. Pre-Commit Workflow Perform the following steps in order before every commit. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

适用 Agent 类型

适用场景: Ideal for AI agents that need pre-commit workflow.

赋予的主要能力 · pre-commit

适用任务: Applying Pre-Commit Workflow
适用任务: Applying Perform the following steps in order before every commit
适用任务: Applying Step 1 — Update history in DEV NOTES.md

! 使用限制与门槛

  • 限制说明: Issues and solutions are the most valuable part: record only non-trivial, non-obvious ones
  • 限制说明: Skip if changes are UI-only (texts, styles) with no architectural implications.
  • 限制说明: Keep only the entry in "Change History" (what was done, problems)

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

评审后的下一步

先决定动作,再继续看上游仓库材料

Killer-Skills 的主价值不应该停在“帮你打开仓库说明”,而是先帮你判断这项技能是否值得安装、是否应该回到可信集合复核,以及是否已经进入工作流落地阶段。

实验室 Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

常见问题与安装步骤

以下问题与步骤与页面结构化数据保持一致,便于搜索引擎理解页面内容。

? FAQ

pre-commit 是什么?

适用场景: Ideal for AI agents that need pre-commit workflow. 本地化技能摘要: # Pre-Commit Workflow Perform the following steps in order before every commit. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

如何安装 pre-commit?

运行命令:npx killer-skills add pupptmstr/caliday/pre-commit。支持 Cursor、Windsurf、VS Code、Claude Code 等 19+ IDE/Agent。

pre-commit 适用于哪些场景?

典型场景包括:适用任务: Applying Pre-Commit Workflow、适用任务: Applying Perform the following steps in order before every commit、适用任务: Applying Step 1 — Update history in DEV NOTES.md。

pre-commit 支持哪些 IDE 或 Agent?

该技能兼容 Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer。可使用 Killer-Skills CLI 一条命令通用安装。

pre-commit 有哪些限制?

限制说明: Issues and solutions are the most valuable part: record only non-trivial, non-obvious ones;限制说明: Skip if changes are UI-only (texts, styles) with no architectural implications.;限制说明: Keep only the entry in "Change History" (what was done, problems)。

安装步骤

  1. 1. 打开终端

    在你的项目目录中打开终端或命令行。

  2. 2. 执行安装命令

    运行:npx killer-skills add pupptmstr/caliday/pre-commit。CLI 会自动识别 IDE 或 AI Agent 并完成配置。

  3. 3. 开始使用技能

    pre-commit 已启用,可立即在当前项目中调用。

! 参考页模式

此页面仍可作为安装与查阅参考,但 Killer-Skills 不再把它视为主要可索引落地页。请优先阅读上方评审结论,再决定是否继续查看上游仓库说明。

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

pre-commit

# Pre-Commit Workflow Perform the following steps in order before every commit. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Pre-Commit Workflow

Perform the following steps in order before every commit.

Step 1 — Update history in DEV_NOTES.md

Add an entry to the "Change History" section (internal_docs/DEV_NOTES.md).

Entry format:

### YYYY-MM-DD — <short description>

**What was done:** [1-2 sentences]

**New files:**
- `path/file.dart` — purpose

**Modified files:**
- `path/file.dart` — what changed

**Key issues and solutions:** [if there were non-trivial technical decisions]

Rules:

  • Place new entry at the top of "Change History" (newest first)
  • For small fixes, merge with a previous entry from the same day
  • Issues and solutions are the most valuable part: record only non-trivial, non-obvious ones

Step 2 — Update ARCHITECTURE.md (if needed)

Update internal_docs/ARCHITECTURE.md if the changes affect:

  • Architectural decisions or patterns
  • Hive models or typeIds (critical!)
  • Service or repository APIs
  • Navigation (routes, flows)
  • Design system (Goro, colors, icons)
  • Feature backlog (implemented feature status → ✅)
  • Android/iOS specifics
  • Dependencies (pubspec.yaml)

Skip if changes are UI-only (texts, styles) with no architectural implications.

Step 3 — Clean up implemented specs in DEV_NOTES (if needed)

If a feature is fully implemented and DEV_NOTES has a detailed spec for it:

  • Remove the spec from "Active Specs"
  • Keep only the entry in "Change History" (what was done, problems)
  • Final decisions should already be captured in ARCHITECTURE.md

Step 4 — Update MEMORY.md

Update auto-memory (.claude/projects/.../memory/MEMORY.md and memory files) if there are:

  • New architectural patterns or key decisions
  • Critical technical constraints (especially Android/iOS specifics)
  • New HiveField numbers or typeIds
  • Backlog changes (what was implemented)

Do not duplicate what is already in ARCHITECTURE.md — memory is for quick access to the most important things.

Step 5 — Create the commit

Only after updating documentation, create the commit:

  • Message in English
  • Format: feat: / fix: / refactor: / docs: / chore: + short description

相关技能

寻找 pre-commit 的替代方案 (Alternative) 或可搭配使用的同类 community Skill?探索以下相关开源技能。

查看全部

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

为prompts.chat的信息反馈系统生成可定制的插件小部件

149.6k
0
AI

flags

Logo of vercel
vercel

React 框架

138.4k
0
浏览器

pr-review

Logo of pytorch
pytorch

Python中具有强大GPU加速的张量和动态神经网络

98.6k
0
开发者工具