skills.rest
elihunter173
elihunter173COMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Verify, stage, commit, and push Rust code changes with Jira ticket IDs.

4|1|Updated Dec 8, 2018
Search Tags:#automation#git#commit#verification#push#ci
One-click install
npx skills add https://github.com/elihunter173/dotfiles --skill commit-elihunter173
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/elihunter173/dotfiles/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/elihunter173/dotfiles --skill commit-elihunter173

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of verifying, staging, committing, and pushing code changes, reducing manual errors and saving development time.

Core Features & Use Cases

  • Code Verification: Runs cargo check and clippy to ensure code compiles and is lint-free before commit.
  • Selective Staging: Assists in staging only affected files explicitly mentioned, avoiding accidental inclusion of unrelated files.
  • Commit Automation: Formats commit messages using Jira ticket IDs and appends co-author information, streamlining team collaboration.
  • Push Management: Handles pushing to remote branches, including setting upstream links for new branches, fulfilling typical CI/CD workflows.
  • Use Case: A developer uses this Skill to validate Rust code, prepare commits with proper formatting, and push to a shared repository with minimal manual steps.

Quick Start

Use the commit skill to verify the current code changes, create a properly formatted commit, and push the updates to the remote repository.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commit and push workflows for Rust projects?▼

Automating git commit and push for Rust projects involves running cargo check and clippy, staging affected files, formatting messages with Jira IDs, and pushing to remote branches. This skill handles those steps sequentially to reduce manual errors.

How do I format commit messages using Jira ticket IDs automatically?▼

Formatting commit messages with Jira ticket IDs is handled by extracting the ticket identifier and appending co-author information automatically. This standardizes commit history for collaborative development without manual message typing.

Can I run cargo check and clippy before committing code changes?▼

Running cargo check and clippy before committing code changes ensures the Rust code compiles and is lint-free. This skill performs both verification checks automatically prior to staging and committing affected files.

What is the best way to stage only affected files and avoid committing unrelated changes?▼

Staging only affected files explicitly mentioned prevents accidental inclusion of unrelated changes. This skill assists in selective staging by targeting specific modified files rather than using blanket git add commands.

How do I push to a new remote branch and set upstream for CI/CD workflows?▼

Pushing to a new remote branch and setting upstream links fulfills typical CI/CD workflow requirements. This skill manages remote branch push operations automatically, including establishing upstream tracking for newly created branches.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
whilpwhilp
9

gh-workflow

Trigger and monitor GitHub Actions workflows via gh CLI.

Community
Advanced
himanshu231204himanshu231204
2

jira-integration

Manage Jira tickets via REST API v3 and MCP server.

Community
Intermediate
FutureAtomsFutureAtoms
1

git-github-git-hooks

Configure Git hooks for automated linting, formatting, and commit message validation.

Community
Advanced