Loading...
Loading...
Found 5 Skills
Cursor Cloud Agent 環境で Git hook 連鎖（特に commit-msg と Co-authored-by 付与・除去）を設計・実装・検証するときに参照する。Cursor 管理 hook の実行順、`commit-msg.cursor.co-author-strip` の命名規則、install スクリプト、lefthook 多層防御、テスト手順を定義する。
Create git commits using conventional commits with scopes. Use when the user asks to commit, make a commit, save changes, or any git commit operation. Never include Co-Authored-By lines, AI agent mentions, or any reference to Claude, AI, or automated tooling in commit messages.
The standard workflow from opening an Issue through branching, implementation, PR, and merge, along with the conventions for Git/GitHub operations. Covers the type(scope) commit message format, how to choose scope, handling of --author, verifying author and committer addresses, prohibiting Co-Authored-By and git add ., squash merging by philtz-organizer-bot through the merge label, checking ahead/behind, and how to write Issue comments and Releases. Use when committing, pushing, creating or switching branches, merging, rebasing, or creating Issues, PRs, comments, and Releases.
UNNC AIM team's repository and code standards. Covers repository naming (competition / aim- academic-year / reusable), branch and Conventional Commits rules, AI-agent git behavior (never commit / push unless the user explicitly asks in the current task; never call the gh CLI without explicit permission; never add an AI Co-Authored-By trailer; suggest a commit message at the end of a code-changing task), and formatting standards for Python (autopep8 / PEP 8), C++ (clang-format / clang-tidy), TypeScript (Prettier + ESLint, pnpm), Go (gofmt), CMake, and Markdown / YAML / JSON, with ready-to-copy canonical rule files. Use when creating or naming a repository, validating a ROS2 package.xml name, creating a branch, writing a git commit message, on any task that could involve committing, pushing, or calling gh, composing a competition workspace (git submodules under src/), or setting up Python, C++ (.clang-format / setup.cfg / .clang-tidy), TypeScript (Prettier / ESLint / pnpm) or Go (gofmt) tooling, styling a CMakeLists.txt or Markdown / YAML / JSON files, or applying the team's recommended git configuration.
Create a git commit following the team's Conventional Commit conventions. Use when the user asks to commit changes or create a commit.