Create conventional git commits with Linear ticket references.
npx skills add https://github.com/f4irline/bbqparty-ai --skill git-commit-f4irline
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/f4irline/bbqparty-ai/tree/main/packages/opencode/.opencode/skills/git-commit Command: npx skills add https://github.com/f4irline/bbqparty-ai --skill git-commit-f4irline
Inconsistent or poorly formatted commit messages and missing ticket references make it hard to track changes, attribute work, and automate release notes; this Skill produces clear, discoverable commits that follow a conventional format and link to Linear tickets.
Generate a conventional commit for ticket STU-15 describing a bug fix to the api, ensure changes are staged and tests pass, and commit with a message including Refs: STU-15.
High-intent search queries and answers about installing and using this skill.
To create conventional commits with Linear ticket references, you need a structured format that appends 'Refs: {ticket-id}' to the commit body. This ensures traceability for features, fixes, and refactors while enabling automated release notes and workflow tracking.
The best way to format git commit messages for automated release notes is using the Conventional Commits specification. This format uses standardized types and optional scopes, making changes discoverable and easily linked to project management tickets.
Yes, you can use an authenticated bot identity for git author and committer metadata. This is configured during the commit process after validating staged diffs, ensuring automated commits are properly attributed to the bot rather than a personal account.
Validating staged changes and running tests before creating a conventional commit involves checking the staged diff and recommending linters and test suites. This ensures code quality before generating the commit message with the required ticket reference.
Yes, conventional commit formatting works for backend, mobile, and infrastructure code repositories. It handles feature, fix, docs, test, chore, and ci commits, ensuring consistent messages and traceability across different project scopes.
Git commits need a 'Refs: {ticket-id}' line for Linear ticket tracking to ensure traceability. Appending this reference links the codebase changes directly to the ticket, making it easy to attribute work and automate workflow updates.
KibertumAnalyze diffs and generate conventional git commit messages with pre-commit checks.
zhangzhang-111-iGenerate changelog entries from Conventional Commits in markdown or JSON.
bradtaylorsfSynchronizes Linear ticket statuses with Git workflow events via API and gh CLI.
mhattingpeteStage, commit, and push code changes with conventional commit messages.
