Skip to content
cccskills
FreePublished on GitHub

commit

Atomic, semantic-boundary git commit workflow

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1020 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

/commit — Atomic Commit Workflow

When to use

When the user runs /commit or asks to commit changes.

Steps

  1. Run git status and git diff --staged to understand what's changed
  2. If nothing is staged, identify logical change groups and stage them separately
  3. Write a commit message following Conventional Commits:
    • feat: new feature
    • fix: bug fix
    • refactor: code restructuring
    • docs: documentation
    • test: tests
    • chore: tooling/build
  4. Use the imperative mood in the subject line
  5. Keep subject under 72 characters
  6. Add body with "why" not "what" if the change isn't self-evident
  7. Create the commit using a heredoc for the message
  8. Run git status to verify

Rules

  • NEVER use --no-verify or --amend unless explicitly asked
  • NEVER stage .env, credentials, or secret files
  • Prefer multiple small commits over one large commit
  • Each commit should compile and pass tests independently

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Prepares Go applications to work effectively with AI coding agents. Use when setting up a new Go project or retrofitting an existing one to ensure: structured JSON logging (slog/Zap/ZeroLog/Logrus), machine-readable command output, thorough golangci-lint configuration, non-interactive CLI design with --yes flags, structured error handling with meaningful exit codes, proper context.Context propagation, graceful shutdown, health check endpoints, and a standardized Makefile. Triggers when a user asks to make their Go app "agent-ready," "AI-friendly," wants to improve agent tooling/observability in a Go project, or needs to audit an existing Go project against agent-readiness best practices.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness20Updated May 31, 2026

Use when creating or updating AGENTS.md files, .github/copilot-instructions.md, or other AI agent rule files, onboarding AI agents to a project, standardizing agent documentation, or when anyone mentions AGENTS.md, agent rules, project onboarding, or codebase documentation for AI agents.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness20Updated May 31, 2026

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness20Updated May 31, 2026

Use when building CLI tools, implementing argument parsing, or adding interactive prompts. Invoke for parsing flags and subcommands, displaying progress bars and spinners, generating bash/zsh/fish completion scripts, CLI design, shell completions, and cross-platform terminal applications using commander, click, typer, or cobra.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness20Updated May 31, 2026

Convert an AWS CloudFormation stack or template to Pulumi. This skill MUST be loaded whenever a user requests migration or conversion of CloudFormation to Pulumi.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness20Updated May 31, 2026

Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass.

The English summary is being prepared. Showing the original description.

dirien/yet-another-agent-harness20Updated May 31, 2026

See all skills by dirien

Report a problem with this skill