Dbeaver-creds ci

Commit

install

source · Clone the upstream repo

git clone https://github.com/Tatsh/dbeaver-creds

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/Tatsh/dbeaver-creds "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/ci" ~/.claude/skills/tatsh-dbeaver-creds-ci && rm -rf "$T"

manifest: .claude/skills/ci/SKILL.md

source content

Commit

Create high-quality Git commits for all pending changes.

Gathering context

Run these in parallel:

```
git diff
```
- unstaged changes.
```
git diff --cached
```
- staged changes.
```
git status
```
- untracked files and overall state.

git log --no-merges --format='%s%n%b---' -20 | grep -v '^bump:' | grep -iv dependabot

- recent commit message style examples.

Running agents

After gathering context but before committing, determine which agents to run based on the changed files. Launch each agent sequentially using the Agent tool with subagent_type

general-purpose

, telling it to follow the corresponding

.claude/agents/<name>.md

file. Scope each agent to only the changed files, not the entire project.

When user-facing changes are being committed

changelog - update
```
CHANGELOG.md
```
with entries for the changes. After it completes, check if
```
CHANGELOG.md
```
was modified (
```
git diff CHANGELOG.md
```
). If it was, it will be staged together with the relevant commit. Only run when changes affect users: files under
```
dbeaver_creds/
```
, or dependency/version changes. Skip for: workflows, CI config,
```
.claude/
```
,
```
.cursor/
```
,
```
.github/instructions/
```
, documentation-only changes, and other non-user-facing files.

Analysing changes

Group changed files by component. Determine if one commit or multiple logical commits are needed.

Incidental files

The following files do not count when determining the component prefix, unless they are the only file in a commit:

```
CHANGELOG.md
```
```
.vscode/dictionary.txt
```

For example, if a commit contains

dbeaver_creds/main

, and

CHANGELOG.md

, the component is determined by the source files only.

CHANGELOG.md

is simply staged alongside them.

CHANGELOG.md

is the only file being committed, use the

changelog:

prefix. If

.vscode/dictionary.txt

is the only file, use

dictionary:

prefix.

When to split into multiple commits

Changes span unrelated components.
A refactor and a bug fix in the same file should be separate commits.
New tests for existing code should be separate from the code changes they test only if the code changes are themselves separate.
Dictionary updates (
```
.vscode/dictionary.txt
```
) should be committed first with message
```
dictionary: update
```
.

Cruft updates

When all changes are from re-running Wiswa (the project generator) and no hand-written code changed, this is a cruft update. Indicators:

Only Wiswa-managed files changed (workflows,

package.json

.pre-commit-config.yaml

.claude/agents/

.cursor/rules/

.github/instructions/

CITATION.cff

.vscode/dictionary.txt

.wiswa.jsonnet

, etc.).

No files under the primary module or source directories changed.

Commit everything in a single commit with the subject

cruft: update

. Include a body summarising what changed (e.g. new/updated workflows, updated agent files, dependency version bumps, new managed files). Do not run any agents. Do not split into multiple commits. Do not update the changelog.

When a single commit is fine

All changes serve the same purpose within a closely related set of files.
A bug fix and its test.

Commit message format

component.name: short description

Optional longer description explaining the why, not the what. Wrap at 72
characters.

Signed-off-by: Author Name <email>
Closes: #123

Subject line rules

Format:
```
component.name: short description
```
. Component name must be lowercase and must skip the first period if present (
```
vscode
```
not
```
.vscode
```
,
```
README.md
```
->
```
readme
```
not
```
README
```
), and must omit the period with extension.
Lowercase after the colon (unless a proper noun).
No period at the end.
Maximum 72 characters.
Use imperative mood: 'add', 'fix', 'update', 'remove', not 'added', 'fixes', 'updated'.

Component prefix rules

Workflow file
```
.github/workflows/qa.yml
```
→
```
workflows/qa:
```
.
Multiple workflows →
```
workflows/*:
```
.
Agent files
```
.claude/agents/*.md
```
→
```
.claude:
```
or specific agent name.
Instruction files across all 3 locations →
```
project:
```
(since they span Copilot/Cursor/Claude).
Dictionary
```
.vscode/dictionary.txt
```
→
```
dictionary:
```
(only when committed alone).
Top-level config (
```
package.json
```
,
```
package.json
```
) →
```
project:
```
.
If changes span many unrelated areas →
```
project:
```
.
CHANGELOG.md →
```
changelog:
```
(only when committed alone).
CONTRIBUTING.md →
```
contributing:
```
.

Trailers

```
Closes: #N
```
- when a commit closes an issue. If it is another project, use the full URI.
```
Fixes: #N
```
- when a commit fixes a bug reported in an issue. If it is another project, use the full URI.
```
Related: #N
```
- when a commit is related to an issue but does not fully close or fix it. If it is another project, use the full URI.
```
Reviewed-by:
```
- if applicable.
```
Co-authored-by:
```
- if applicable.
```
Reported-by:
```
: - if applicable. Could get this information from a bug report that led to the fix if the issue ID/URL is known.
```
Signed-off-by:
```
- always included on every commit. This will be added with
```
-s
```
.

Making commits

Stage files for each logical commit using
```
git add
```
with specific file paths.
If
```
CHANGELOG.md
```
was updated by the changelog agent, stage it with the relevant commit.
Create a unique temp file with
```
mktemp /tmp/commit-msg-XXXXXXXX
```
, write the commit message there using the Write tool (not Bash
```
cat
```
), then commit with
```
git commit -S -s -F <tempfile>
```
. Multiple Claude instances may run concurrently, so never use a fixed path.
If a pre-commit hook fails, fix the issue, re-stage (use appropriate agent if there is one), and try to commit again.
After all commits, run
```
git status
```
to verify clean state.

Rules

Never use
```
--no-verify
```
or
```
--no-gpg-sign
```
.
Amend the previous commit when the new change is logically part of it (e.g. same file, same topic, fixing something just committed). Create a new commit when the change is distinct.
Never push unless explicitly asked.
Always use
```
-S
```
for GPG signing and
```
-s
```
for sign-off.
If there are no changes, do nothing.
Stage specific files, never use
```
git add -A
```
or
```
git add .
```
.