Skip to content
TrustedSkillsbeta
Back to all skills

Git Storytelling Commit Strategy

Checked
thebushidocollective·vlatest·backend

Crafts compelling commit messages & branching strategies based on project context, enhancing collaboration and code history clarity.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add thebushidocollective/han --skill git-storytelling-commit-strategy -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

thebushidocollective

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned thebushidocollective/han at 19caa51d5f.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
19caa51d5f
Manifest
plugins/patterns/git-storytelling/skills/commit-strategy/SKILL.md
Scanned
1 file, 481 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps you craft clear and descriptive commit messages for your Git repositories. It leverages a structured approach to commit message creation, ensuring that changes are easily understandable and traceable over time. The goal is to transform your commit history into a narrative of project evolution.

When to use it

  • Large Projects: When working on complex projects with multiple contributors where clear commit histories are crucial for collaboration.
  • Code Reviews: To facilitate easier code reviews by providing context and rationale behind each change.
  • Debugging & Auditing: When needing to quickly understand the history of a bug or feature implementation.
  • Documentation Generation: To potentially generate release notes or project documentation directly from commit messages.

Key capabilities

  • Structured Commit Message Formatting
  • Narrative-Driven Commit History
  • Improved Code Review Process
  • Enhanced Project Traceability

Example prompts

  • "Generate a commit message for refactoring the user authentication module."
  • "Write a commit message explaining the addition of a new feature to handle image uploads."
  • "Create a descriptive commit message detailing bug fix #123 related to data validation."

Tips & gotchas

The quality of the generated commit messages depends on the clarity and detail provided in your initial request. Consider providing context about the changes made for more effective results.