@kurokeita/add-skill 1.17.0 → 1.17.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -46,9 +46,9 @@ The branch structure follows a categorized format:
|
|
|
46
46
|
|
|
47
47
|
### Workflow
|
|
48
48
|
|
|
49
|
-
1. Start from the
|
|
50
|
-
2. Ensure the local branch is up-to-date: `git pull origin
|
|
51
|
-
3. Create the new branch: `git checkout -b <type>/<description>`.
|
|
49
|
+
1. Start from the default branch.
|
|
50
|
+
2. Ensure the local branch is up-to-date: `git pull origin $(git branch --show-current)`.
|
|
51
|
+
3. Create the new branch without tracking: `git checkout --no-track -b <type>/<description>`.
|
|
52
52
|
|
|
53
53
|
## Additional Resources
|
|
54
54
|
|
|
@@ -37,8 +37,9 @@ This repo uses **squash merge** for all PRs. The resulting commit on `main` foll
|
|
|
37
37
|
- **Commit title:** `<conventional-commit-title> (#<pr-number>)`
|
|
38
38
|
- Example: `feat(cli): implement live search filtering for item selection (#24)`
|
|
39
39
|
- **Extended description:** A concise summary paragraph followed by bullet-point details of key changes.
|
|
40
|
-
-
|
|
41
|
-
-
|
|
40
|
+
- **CRITICAL:** `gh pr merge --squash` without `--body` auto-generates the commit body by concatenating all branch commit messages — producing cluttered, redundant git history.
|
|
41
|
+
- **ALWAYS** pass an explicit `--body` flag with a curated commit message: `gh pr merge --squash --body "<message>"`.
|
|
42
|
+
- Write the body so it reads well as a git log entry — focus on **what** changed and **why**, not **how**.
|
|
42
43
|
- Use bullet points for listing specific file-level or feature-level changes.
|
|
43
44
|
- Avoid checklist boilerplate in the final description; it clutters the git history.
|
|
44
45
|
|