commit

Stage git changes, write conventional commit messages, and post results to crosslink issues.

27|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/forecast-bio/ferray --skill commit-forecast-bio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/forecast-bio/ferray/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/forecast-bio/ferray --skill commit-forecast-bio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill streamlines committing work by ensuring changes are staged properly, a conventional commit is crafted, and the result is automatically documented on the active crosslink issue, reducing manual steps and audit gaps.

Core Features & Use Cases

  • Stages changes safely and writes a clear, conventional-style commit message.
  • Automatically posts a result comment on the active crosslink issue to close the audit trail.
  • Works with typical git workflows and crosslink-enabled repositories.

Quick Start

Stage your changes and run the commit workflow to create a commit and post the crosslink result.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commits and post results to a crosslink issue?

You can automate git commits and post results by running a workflow that stages changes, generates a conventional commit message, and comments the result on the active crosslink issue for traceability.

What is the best way to write conventional commit messages automatically?

Automated conventional commit messaging validates your staged changes and guides the formatting to ensure clear, standardized version-control records without manual writing effort.

Does this commit workflow require any dependencies or components?

No dependencies or components are required to run the commit workflow, making it straightforward to stage changes and document results in crosslink-enabled repositories.

How does crosslink-recording work with version control commits?

Crosslink-recording triggers after a successful commit to automatically post a result comment on the active crosslink issue, closing the audit trail between code changes and issue tracking.

Can I use this with my existing git workflows and crosslink-enabled repositories?

Yes, the commit automation works with typical git workflows and crosslink-enabled repositories, safely staging changes and documenting results without disrupting your established process.