Skip to content
TrustedSkillsbeta
Back to all skills

Git Commits

Checked
parcadei·vlatest·backend·MIT

Automates Git commit creation and pushes based on task descriptions, streamlining backend development workflows.

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 parcadei/continuous-claude-v3 --skill git-commits -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

parcadei

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 parcadei/continuous-claude-v3 at d07ff4b06b.

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

Commit
d07ff4b06b
Manifest
.claude/skills/git-commits/SKILL.md
Scanned
1 file, 42 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

git-commits

What it does

This skill enables AI agents to interact directly with Git repositories, allowing them to read commit history, analyze changes, and manage version control workflows autonomously. It bridges the gap between code generation and deployment by giving agents full visibility into project evolution.

When to use it

  • Investigating the root cause of a bug by reviewing recent commits and diffing specific files.
  • Automating release notes generation by summarizing changes across multiple branches.
  • Assisting in code reviews by identifying potential issues introduced in the last few merges.
  • Tracking feature implementation progress by monitoring commit frequency and authors.

Key capabilities

  • Read and parse Git commit logs from local or remote repositories.
  • Analyze specific file histories to understand how code has evolved over time.
  • Identify patterns in developer activity and contribution timelines.
  • Extract metadata such as commit hashes, dates, and author information.

Example prompts

  • "Show me the last 10 commits that modified the auth.py file."
  • "Summarize the changes introduced in the most recent merge request for the frontend branch."
  • "Who made the last change to the database schema and when was it committed?"

Tips & gotchas

Ensure the AI agent has read access to the target repository before attempting to query commit history. Large repositories with extensive histories may require pagination or specific date ranges to avoid performance bottlenecks during analysis.