Automated summary
This skill creates a commit with a message formatted according to the Conventional Commit convention.
Strengths
- Automates creation of well-formatted commits
- Ensures adherence to Conventional Commit standards
- Uses Git tools directly
Limitations
- Only works with staged changes
- Requires Git to be installed
- Does not handle merge conflict situations
Use this skill when you need to create a commit with a structured message following best practices.
Avoid using it for non-conventional commits or when you need human input for message drafting.
Security analysis
SafeThe file contains only example YAML skill definitions and explanatory text. No destructive commands are issued; the examples describe safe, conventional development tasks (commit, review, deploy) with appropriate tool restrictions. The file itself does not perform any actions.
No concerns found
How this analysis is madeExamples
Create a commit for the staged changes with a conventional commit message.タスク型スキルの例
例1: コミットスキル
---
name: commit
description: Create a conventional commit with proper message format
disable-model-invocation: true
allowed-tools: Bash(git:*)
---
# コミット作成
## 手順
1. `git diff --cached` でステージされた変更を確認
2. 変更内容を分析し、Conventional Commit 形式でメッセージを作成
3. コミットを実行
## メッセージ形式
\```
<type>(<scope>): <subject>
<body>
<footer>
\```
type: feat, fix, refactor, chore, docs, test, ci
例2: PR レビュースキル
---
name: review-pr
description: Review a pull request for code quality, security, and best practices
disable-model-invocation: true
argument-hint: "[PR番号またはURL]"
allowed-tools: Bash(gh:*), Read, Grep, Glob
---
# PR レビュー
## PR 情報の取得
$ARGUMENTS の PR を取得する:
1. `gh pr diff $ARGUMENTS` で差分を取得
2. `gh pr view $ARGUMENTS` で PR の概要を確認
## レビュー観点
- コードの正確性
- セキュリティ（OWASP Top 10）
- パフォーマンス
- テストカバレッジ
- 命名規約の遵守
## 出力形式
各ファイルについて:
- 問題の深刻度（Critical / Warning / Info）
- 該当箇所（ファイル名:行番号）
- 問題の説明と改善案
例3: デプロイスキル
---
name: deploy
description: Deploy the application to production
disable-model-invocation: true
argument-hint: "[staging|production]"
allowed-tools: Bash(npm:*, docker:*, git:*)
---
# デプロイ
対象環境: $ARGUMENTS
## 手順
1. テストスイートを実行
2. ビルド
3. デプロイターゲットにプッシュ
4. デプロイ後の動作確認
## 注意事項
- production デプロイ前に staging での検証を確認する
- ロールバック手順を把握しておく
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/task-based-skills-examples-mm78nnjf/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/task-based-skills-examples-mm78nnjf' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/task-based-skills-examples-mm78nnjf/download' --output '.skill-downloads/task-based-skills-examples-mm78nnjf/SKILL.md.part' && mv '.skill-downloads/task-based-skills-examples-mm78nnjf/SKILL.md.part' '.skill-downloads/task-based-skills-examples-mm78nnjf/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/task-based-skills-examples-mm78nnjf/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.