メニュー
This skill MUST be invoked when the user says "commit tarihlerini değiştir", "redate commits", "spread commits", "backdate" or any variation requesting git commit date rewriting across a date range. Rewrites both author and committer dates using git filter-branch, distributing commits realistically across the specified period.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill MUST be invoked when the user says "check-golang", "govulncheck", "gosec", "cve tara", "cve raporu", "güvenlik açığı tara", "zafiyet tara", "vulnerability scan", "vuln scan", "scan for CVEs", "check vulnerabilities", "güvenlik taraması", "security scan", "static security analysis", "lint tara", "golangci-lint", "modernize", "modernizer", "lint check", "kod kalitesi tara" or any variation requesting a Go security or code-quality scan of the whole project. Runs FOUR tools by default — govulncheck (CVEs), gosec (security static analysis), golangci-lint (lint), and the gopls modernize analyzer — installs any that are missing, scans every package with ./..., classifies each finding, and produces a ranked combined report with fix guidance.
This skill MUST be invoked when the user says "version update skill oluştur", "create version update skill", "versiyon skill'i oluştur", "update-version skill", "version-update skill yap" or any variation requesting creation of a project-local version update skill. SHOULD also invoke when user mentions "versiyon güncelleme skill'i kur", "setup version bumping", or asks to automate version management for the current project. Scans the project for version files, build commands, and changelog, then generates a tailored version-update skill in .claude/skills/.
Use `/bug-report` for full audit, `/bug-report <subcommand>` for focused audits, `/bug-report security-sweep` for security-only scans with a rolling 2-worker pool.
This skill MUST be invoked when the user says "commit", "commitle", "commit at", "commit yap", "push" or any variation requesting a git commit. SHOULD also invoke when user mentions "stage", "staged", "değişiklikleri commitle", or asks to push code changes. Creates well-formatted commits with conventional commit messages. Auto-detects git state, stages changes intelligently, and creates atomic commits with proper type/scope/description format.
Use `/bug-report` for full audit, `/bug-report <subcommand>` for focused audits, `/bug-report security-sweep` for security-only scans with a rolling 2-worker pool.
This skill MUST be invoked when the user says "git flow", "git-flow", "branch aç", "feature başlat", "feature start", "bugfix", "hotfix", "release branch", "branch oluştur", "create branch" or any variation requesting git branch workflow management. SHOULD also invoke when user mentions "finish branch", "merge feature", "complete hotfix", or asks to follow git-flow branching strategy. Manages git branches following a structured workflow with automatic base branch detection and strict validation rules.
| name | redate-commits |
| description | This skill MUST be invoked when the user says "commit tarihlerini değiştir", "redate commits", "spread commits", "backdate" or any variation requesting git commit date rewriting across a date range. Rewrites both author and committer dates using git filter-branch, distributing commits realistically across the specified period. |
| argument-hint | <start-date> <end-date> [--weekdays-only | --include-weekends | --weighted-weekdays] |
Rewrites git commit dates to distribute them across a specified date range, making the history appear as if development occurred over that period.
/redate-commits 2026-02-01 2026-03-31 # Default: weighted weekdays
/redate-commits 2026-01-01 2026-06-30 --weekdays-only
/redate-commits 2026-02-01 2026-03-31 --include-weekends
Before doing anything, gather the commit history:
git log --oneline --format="%H %ai %s" | head -20 # Recent commits with dates
git log --oneline | wc -l # Total commit count
git log --reverse --format="%H %s" | head -5 # Oldest commits
git log --reverse --format="%H %s" | tail -5 # Newest commits
| Parameter | Description | Default |
|---|---|---|
start-date | First date (YYYY-MM-DD) | Required |
end-date | Last date (YYYY-MM-DD) | Required |
--weekdays-only | Mon-Fri only | No |
--include-weekends | All 7 days equally | No |
--weighted-weekdays | Heavy weekdays, light weekends | Yes (default) |
Commits should be grouped by feature/topic, not randomly scattered. Related commits (same feature branch, same module) should land on the same day or consecutive days.
Analyze commit messages to identify logical groups:
feat(T001-T005) → same feature, same day or 2 daysMerge feature/F001 → day after the feature commitschore:, docs: → standalone, can fill gapsfix: → day after the related feat:git log --reverse --format="%H %s"
Create a Python script that:
FILTER_BRANCH_SQUELCH_WARNING=1 git filter-branch -f \
--env-filter "$(cat /tmp/git_date_filter.sh)" \
-- --all
The filter script format:
if [ "$GIT_COMMIT" = "<hash>" ]; then
export GIT_AUTHOR_DATE="<date>"
export GIT_COMMITTER_DATE="<date>"
fi
git reflog expire --expire=now --all
git gc --prune=now --aggressive
git push --force
filter-branch fails, the original refs are preserved in refs/original/declare -A not supportedUse Python for the date mapping script, not bash associative arrays. macOS default shell (zsh) has issues with declare -A in heredocs.
If Docker was built from the repo, stale image layers can cause snapshot errors. Run:
docker compose build --no-cache
# Check first and last commit dates
git log --format="%ai %s" | tail -1 # Should be start-date
git log --format="%ai %s" | head -1 # Should be end-date
# Check weekend distribution
git log --format="%ad" --date=format:"%u %Y-%m-%d" | sort | uniq -c
# Column 1 = count, Column 2 = day-of-week (1=Mon, 7=Sun)