CtrlK
BlogDocsLog inGet started
Tessl Logo

git-workflows

Reusable git delivery workflows derived from local slash commands (commit, push, PR, release notes, and GitHub Actions failure triage with worktree-based fixes).

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/git-workflows/SKILL.md
SKILL.md
Quality
Evals
Security

Git Workflows (from local commands)

This skill turns the repo's former local command templates into reusable git delivery workflows.

When to use this skill

Use this skill when the user asks to:

  • run a commit workflow (conventional-changelog style)
  • push changes with safe branching and open a PR
  • generate release notes from git history / GitHub context
  • publish a version from main (including bilingual README Recent updates on minor bumps)
  • analyze the latest failed GitHub Actions workflow, attempt a fix in an isolated worktree, and submit a PR
  • check IDE icon configuration consistency across document components and source files

Source of truth

All detailed steps and constraints live in:

  • references/source-commands.md

This skill describes how to apply them consistently across agents/editors without duplicating implementation details.

Execution rules

  1. Read the requested command template from references/source-commands.md.
  2. Follow it as workflow steps, not as a loose summary.
  3. Keep actions safe by default:
    • avoid destructive git operations unless explicitly requested
    • avoid committing secrets
    • keep changes minimal and localized
  4. If a workflow implies external side effects (push/PR/release), request explicit confirmation right before performing the side effect.

Command mapping

See references/command-catalog.md.

Repository
TencentCloudBase/CloudBase-AI-Toolkit
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.