coding-workflow

Enforces code style rules, commit message format, and a staged git push workflow.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/johsquaree/claude-basic-docs --skill coding-workflow-johsquaree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-workflow
Source: https://github.com/johsquaree/claude-basic-docs/tree/main/.claude/skills/coding-workflow
Command: npx skills add https://github.com/johsquaree/claude-basic-docs --skill coding-workflow-johsquaree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent code style, messy commit histories, and risky push habits (like staging everything with git add .) slow down development and create avoidable conflicts. This Skill gives the AI a fixed set of personal coding conventions, a pre-commit checklist, and a disciplined commit-and-push procedure. ## Core Features & Use Cases - Code Style Enforcement: Applies camelCase for variables/functions, PascalCase for components/classes, kebab-case file names, single-responsibility components under 200 lines, and named constants instead of magic values. - Pre-Commit Checklist: Verifies the code compiles, removes unused imports and debug output, and suggests a manual test step before committing. - Structured Commit & Push Workflow: Proposes short hyphenated commit messages (max 30 characters), stages only relevant files, asks for confirmation, and recommends git pull --rebase before pushing. - Use Case: While building a mobile app feature, ask the AI to commit your changes — it will stage only the touched files, propose a message like add-biometric-login, wait for your approval, then rebase and push safely. ## Quick Start Review my current changes, propose a commit message following my workflow rules, and push after my confirmation.

Frequently Asked Questions about coding-workflow

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

FAQPage Schema
How do I enforce a consistent commit message format with AI?

Define the format rules in a workflow skill: maximum 30 characters, hyphen-separated words, and no type or scope prefixes. The AI then proposes messages like add-biometric-login or fix-avatar-upload-crash and waits for your approval before committing.

How to avoid staging all files with git add . when committing?

Run git status first to list changed files, then stage only the relevant ones with git add <file>. This workflow makes selective staging a mandatory step and explicitly forbids git add . to keep commits focused.

What should I check before committing code?

Verify the code compiles without syntax errors, remove unused imports and variables, and clean up debug output like console.log or print statements. If the change affects a user flow, run a short manual test before committing.

Should I pull before pushing to avoid git conflicts?

Yes, run git pull --rebase before pushing to synchronize with the remote branch. This workflow recommends the rebase step and warns you when there is a conflict risk so you can resolve it before the push.

What naming conventions does this coding workflow use?

Variables and functions use camelCase, components and classes use PascalCase, and file names use kebab-case such as login-screen.tsx or auth-service.ts. Files over 200 lines should be split into single-responsibility components.