admin/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-02-07 23:23:08 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
86b5a53e5d5362201ce8a991e4b5661f649fd642
everything-claude-code/rules/common/git-workflow.md
Hor1zonZzz 86b5a53e5d refactor(rules): restructure into common + language-specific directories 
* refactor(rules): restructure rules into common + language-specific directories

- Split 8 flat rule files into common/, typescript/, python/, golang/
- common/ contains language-agnostic principles (no code examples)
- typescript/ extracts TS/JS specifics (Zod, Playwright, Prettier hooks, etc.)
- python/ adds Python rules (PEP 8, pytest, black/ruff, bandit)
- golang/ adds Go rules (gofmt, table-driven tests, gosec, functional options)
- Replace deprecated ultrathink with extended thinking documentation
- Add README.md with installation guide and new-language template

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* Fix installation commands for rules

Updated installation instructions to copy all rules to a single directory.

* docs: update README.md to reflect new rules directory structure

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: Hor1zonZzz <Hor1zonZzz@users.noreply.github.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-05 05:58:06 -08:00

1.0 KiB
Raw Blame History

Git Workflow

Commit Message Format

<type>: <description>

<optional body>

Types: feat, fix, refactor, docs, test, chore, perf, ci

Note: Attribution disabled globally via ~/.claude/settings.json.

Pull Request Workflow

When creating PRs:

  1. Analyze full commit history (not just latest commit)
  2. Use git diff [base-branch]...HEAD to see all changes
  3. Draft comprehensive PR summary
  4. Include test plan with TODOs
  5. Push with -u flag if new branch

Feature Implementation Workflow

  1. Plan First

    • Use planner agent to create implementation plan
    • Identify dependencies and risks
    • Break down into phases

  2. TDD Approach

    • Use tdd-guide agent
    • Write tests first (RED)
    • Implement to pass tests (GREEN)
    • Refactor (IMPROVE)
    • Verify 80%+ coverage

  3. Code Review

    • Use code-reviewer agent immediately after writing code
    • Address CRITICAL and HIGH issues
    • Fix MEDIUM issues when possible

  4. Commit & Push

    • Detailed commit messages
    • Follow conventional commits format
Reference in New Issue View Git Blame Copy Permalink