Menu
Make a commit in Git with an appropriate commit message for the currently staged changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
This skill should be used when adding new ActivityPub/JSON-LD vocabulary types to the @fedify/vocab package, defining new YAML vocabulary schema files, or updating existing vocabulary definitions in Fedify. Applies when implementing FEPs, extending ActivityStreams vocabulary, or adding third-party vocab types such as Mastodon extensions, Litepub types, or other fediverse vocabularies.
This skill is utilized when creating a web framework integration package. After examining the given framework, a feasibility assessment is conducted regarding the creation of an integration package. If implementation is feasible, the package is generated; if it is not possible, the rationale is provided to the user.
This skill is utilized when fetching reviews from GitHub pull requests. Get the reviews, organize, and help to resolve them.
This skill is used to create an example application for a web framework integration package and to test it with `mise test:examples`.
Look up a Fediverse Enhancement Proposal (FEP) and explain how to implement it with Fedify. Use when the user asks about a specific FEP by ID (e.g., FEP-8fcf, FEP-1b12) or wants to implement a fediverse standard in their Fedify application.
Help the user migrate Fedify code between versions. Use when the user needs to upgrade their Fedify version, fix breaking-change errors, or update deprecated API usage.
| name | commit |
| description | Make a commit in Git with an appropriate commit message for the currently staged changes. |
| allowed-tools | Bash(git *) |
Please make a commit with an appropriate commit message for the currently staged changes.
Don't touch the staged changes, just create the commit.
The first line of the commit message should be a concise summary of the changes (50 characters or less). You shouldn't follow the conventional commits, in other words, just write a normal commit message without any special prefixes.
The second line of the commit message should be blank.
The rest of the commit message should provide more detailed explanations about the changes, wrapped at 72 characters.
If you have some references like issues or pull requests, you can add them in the body of the commit message, usually after a blank line. Issues and pull requests should be referenced as full URLs instead of #numbers, and you can put some verbs like “Fixes” or “Closes” before the URLs. For just references without any verbs, you can just put the URLs in the body.
When running git commit, pass the commit message via a HEREDOC to
preserve newlines correctly. Never use literal \n escape sequences
inside a quoted string, as they will appear as literal characters in
the commit message. For example:
git commit -m "$(cat <<'EOF'
Summary line here
Detailed explanation here.
EOF
)"
Don't put Generated with [Claude Code](https://claude.ai/code), or
Co-authored-by trailers at the end of the commit message. Instead,
use the Assisted-by trailer to indicate that the commit was generated by
an AI assistant, if necessary. The format of the Assisted-by trailer should
be:
Assisted-by: AGENT_NAME:MODEL_VERSION
For example:
Assisted-by: OpenCode:qwen3.6-plus
Assisted-by: Claude Code:claude-sonnet-4-6
Assisted-by: Gemini CLI:gemini-3.1-pro-preview
Assisted-by: Codex:gpt-5.4