pixiv-cli-commit-message

A guide for creating a one-line Conventional Commits message, a standard format for describing a code change, from staged Git changes.

In plain words
What is it for?
Use it to inspect staged changes and recent commits, then choose a suitable type such as feat, fix, docs, refactor, test, or chore.
Why use it?
It keeps commit messages consistent and based on the changes actually prepared for commit. It also avoids guessing when nothing is staged.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/flanchanxwo/pixiv-cli/pixiv-cli-commit-message
Any agent
npx skills add FlanChanXwO/pixiv-cli --skill pixiv-cli-commit-message
Clone the repo
git clone --depth 1 https://github.com/FlanChanXwO/pixiv-cli

Made for: Claude Code, Codex.

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 230 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.00230
Opus 5 $0.00012 $0.00115
Sonnet 5 $0.00005 $0.00046
Haiku 4.5 $0.00002 $0.00023

Measured 3d ago against content hash a72606445e1c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pixiv-cli-commit-message scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/pixiv-cli-commit-message/SKILL.md · 24 lines

What it actually says

pixiv-cli Commit Message

根据暂存区生成一行提交信息。默认只看 staged changes;暂存区为空时直接说明,不编造。

读取

git status --short
git diff --cached
git log --oneline -10

风格

  • 一行输出,不加解释、项目符号或代码块。
  • Conventional Commits,贴近仓库近期风格:feat / fix / docs / refactor / test / chore
  • subject 英文、小写开头,约 72 字符;不写 miscupdate fileswip
  • type 判断:行为修复 fix;包边界或内部结构 refactor;文档和 agent 文件 docs;测试补充 test;构建/脚本/依赖 chore
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 24 lines · 23 tokens per session scan A a72606445e1c

Subscribe to this mod's changes

pixiv-cli-commit-message is a skill published in the GitHub repository FlanChanXwO/pixiv-cli (108 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 230 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

zapier-sdk

Zapier SDK for TypeScript. Programmatic access to 9,000+ apps on a user's behalf via Zapier's OAuth and audit layer. Use when writing code that needs to run actions in third-party apps (send an email, upsert a CRM record, look up a spreadsheet row, post to a chat) without managing per-app OAuth or vendor SDKs.…

zapier/sdk · 151 tokens

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…

addyosmani/agent-skills · 74 tokens

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

git-commit

Generate well-formatted git commit messages following conventional commit standards.

ThinkInAIXYZ/deepchat · 15 tokens

git-workflow

This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…

Galaxy-Dawn/claude-scholar · 64 tokens

contributing

How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…

HugoRCD/evlog · 68 tokens