config/agents/skills/git/SKILL.md
Use when the task is primarily about Git operations or Git workflow, such as writing commit messages, creating or switching branches, understanding rebase or cherry-pick flow, inspecting history, or deciding how to structure commits. Do NOT use for GitHub-specific actions like PR comments or issue updates; use the github skill for those. Trigger especially when the user mentions commit, branch, rebase, cherry-pick, stash, merge, or Conventional Commits.
npx skillsauth add kumewata/dotfiles gitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guide for Git operations. For mandatory rules and permissions,
see rules/git-github.md.
<type>: <brief description> (#<Issue number>)
<detailed description>
## Summary
- Same as detailed description is OK
## Background
- Briefly explain the background and purpose
## Changes
- Specific change 1
- Specific change 2
## Technical Details
- Technical implementation details
- Reasons for design decisions
- Focus on "why" throughout
## Verification
- Describe verification if performed
## Related URLs
- <Related Issue>
- <External URL>
- Others if applicable
| Type | Description | | -------- | ---------------------------- | | feat | New feature | | fix | Bug fix | | docs | Documentation only | | style | Formatting, no code change | | refactor | Code change without fix/feat | | test | Adding/updating tests | | chore | Maintenance, dependencies |
| Resource | Purpose | | ---------------- | ------------------------------- | | rules/git-github | Mandatory rules and permissions | | skills/github | GitHub-specific operations |
tools
Use when creating a new skill or making a substantial change to an existing skill and you also need to design, update, or review Waza-based executable evaluations. This includes deciding whether Waza is warranted, mapping `evals.json` cases into Waza tasks, choosing fixtures and graders, selecting a valid model with `waza models --json`, and running a local-first `waza run` workflow. Do NOT use for installing the Waza CLI itself or for general skill-authoring advice that does not involve Waza; use `skill-creator` for skill design and this skill for the Waza execution layer. Trigger especially when the user mentions Waza, `waza run`, `waza models`, executable evals, compare, graders, fixtures, or wants to validate a skill change with model-backed evaluation.
tools
Use when the user wants Codex to ask Claude Code for a second opinion or review on code, docs, diffs, PR changes, or design notes without modifying files. This delegates bounded review-only analysis through the Claude Code CLI (`claude -p`). Do NOT use for implementation or file edits; keep this skill review-only. Trigger especially when the user says ask Claude, ask Claude Code, cc-delegate, Claude review, second opinion from Claude, compare Codex and Claude, or review this diff/document with Claude Code.
tools
Airflow DAG development skill for writing, reviewing, testing, and debugging Apache Airflow workflows. Use whenever the user mentions Airflow, DAGs, tasks, operators, sensors, schedules, retries, catchup, DAG import errors, DAG parse performance, or workflow orchestration in Python. Also use for Amazon MWAA / Managed Workflows for Apache Airflow work, including MWAA DAG deployment, requirements.txt, plugins.zip, aws-mwaa-docker-images, S3 DAG folders, CloudWatch logs, and MWAA-specific dependency or IAM issues.
development
Use when the user asks for help drafting a GitHub PR description, a PR review comment, or a Slack post in their own tone (i.e., their personal writing voice). The skill detects the context (formal for PR / review, casual for Slack) and target_type (pr_description, pr_review, slack), drafts the body with an explicit reflection step that avoids verbose, mechanical phrasing, and stages the draft to `~/.local/state/tone/drafts/` via `tone-stage-draft.sh`. The user later runs `/tone-capture <url>` after posting, which pairs the staged draft with the final body to build a corpus for future tone tuning. Trigger especially when the user mentions PR description, PR review comment, Slack post, または「文を書いて」「文面を作って」「自分らしく」「トーン」「tone」.