commit ebcddadc7faf72d4735132ba1fcaa8c043622935 parent fe2550bb392768a76c538545af4a29d9d75faf5b Author: Anders Hedman <anders.hedman01@gmail.com> Date: Fri, 28 Aug 2026 22:21:37 +0200 opencode(skills): obsolete git-commiter Diffstat:
| D | .config/opencode/skills/git-commiter/SKILL.md | | | 40 | ---------------------------------------- |
1 file changed, 0 insertions(+), 40 deletions(-)
diff --git a/.config/opencode/skills/git-commiter/SKILL.md b/.config/opencode/skills/git-commiter/SKILL.md @@ -1,40 +0,0 @@ ---- -name: git-commiter -description: Write descriptive but managable git commit messages ---- - -## Commit Message Guidelines - -- The subject line must be **≤ 50 characters** (includes whitespace). -- Include a descriptive body -- Write in imperative mood and start with a capital letter. -- Do not end the subject with a period. -- Separate subject and body with a blank line. - -## Body Rules - -- Each body line ≤ 72 characters. -- Use `-m` for each paragraph when committing from CLI. - Example: - ``` - git commit -m "Subject" -m "Body paragraph 1" -m "Body paragraph 2" - ``` - -## Useful commands - -- Use `git commit --amend` to modify the most recent commit. - ``` - git commit --amend -m "New subject" -m "New body" - ``` -- To view the last commit verbatim, run: - ``` - git log -1 --pretty=full - ``` - -## Remember - -- Avoid using `git commit -a` unless you know what you’re committing. -- Keep messages focused; explain *what* was done and *why* it matters. -- Show the plan first. -- Do not commit until the user confirms. -