ci

Commit staged Git changes after passing lint checks.

1|Updated Jan 8, 2026

Search Tags:#automation #git #workflow #devops #commit #lint

Ready to run

npx skills add https://github.com/darknight/cc-deck --skill ci-darknight

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci
Source: https://github.com/darknight/cc-deck/tree/main/plugins/deck/skills/ci
Command: npx skills add https://github.com/darknight/cc-deck --skill ci-darknight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streams the commit process by ensuring only lint-passed, staged changes are committed to Git, reducing broken builds from partial changes.

Core Features & Use Cases

Staged change validation: checks for lint errors and untracked files before committing.
Deterministic commits: enforces concise, descriptive messages and avoids pushing to remotes.
Local workflow automation: coordinates git add, git status, and git commit to streamline developer iterations.

Quick Start

Commit staged changes in your repo by invoking the AI command to finalize and record a clean, descriptive commit.

Frequently Asked Questions about ci

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

FAQPage Schema

How do I automate git commit only after lint checks pass?▼

To automate a git commit after lint checks pass, the Skill validates staged changes for lint errors and untracked files before executing the commit. It coordinates git add, git status, and git commit to ensure only lint-passed code is recorded locally.

What is the best way to prevent broken builds from partial git commits?▼

Preventing broken builds from partial git commits requires validating staged changes before finalizing. This Skill enforces lint checks on staged files, ensuring incomplete or untracked code is not committed to the local repository, reducing build failures.

Can I use this workflow to push commits to a remote repository?▼

No, you cannot use this workflow to push commits to a remote repository. The Skill is designed for local workflow automation and strictly avoids pushing to remotes, focusing entirely on safe, local git commit iterations.

How do I enforce a descriptive commit message in my devops automation?▼

To enforce a descriptive commit message in devops automation, the Skill requires a short, descriptive message for every git commit. It finalizes the commit with deterministic constraints to streamline developer iterations and maintain code history.

Does this git commit workflow handle untracked files automatically?▼

Yes, the git commit workflow handles untracked files by validating staged changes and checking for untracked files before committing. It identifies staged changes in the Git repository and ensures only lint-passed code is committed locally.