agentsclimarketplace

Git worklog guardrails

Skill jukrap/ai-agent-playbook/skills/delivery/git-worklog-guardrails

Reusable AI agent skills, project templates, and guardrails for safer software maintenance and delivery.

Install
npx -y skills add jukrap/ai-agent-playbook --skill git-worklog-guardrails

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when staging files, committing, pushing, preparing PR text, release notes, or worklogs in a repository with local-only files or careful branch policy.

SKILL.md

0.8 KB, 140 tokens by cl100k_base, as published. Nobody here has run it

Git Worklog Guardrails

Use this as the primary delivery skill for git, PR, and worklog safety.

Workflow

  1. Check branch, remote, upstream, dirty files, staged files, and local-only policy.
  2. Stage only task-related files.
  3. Verify with commands that the repository defines.
  4. Write commit, PR, and worklog text from actual diff and actual verification.
  5. Keep unrelated user changes untouched.

Compatibility

commit-worklog-guardrails is a compatibility trigger for this skill.

Reference

Read references/git-delivery-checklist.md before staging, committing, pushing, writing PR text, or recording a worklog.

Gives 0 of the 12 instructions most pr commit review skills give in 140 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

  • use conventional commits formatin 123 of 888, across 110 files
  • keep subject line under 72 charactersin 60 of 888, across 46 files
  • delete branches after mergein 50 of 888, across 37 files
  • use imperative mood in subject linein 50 of 888, across 41 files
  • use imperative mood in commit messagesin 45 of 888
  • generate a conventional commit messagein 42 of 888
  • make atomic commitsin 37 of 888, across 25 files
  • run tests before committingin 36 of 888, across 24 files
  • run project test suite to verify clean baselinein 35 of 888, across 7 files
  • run detected project setup commandsin 34 of 888, across 6 files
  • wrap commit body at 72 charactersin 32 of 888, across 25 files
  • split unrelated changes into separate commitsin 32 of 888, across 27 files

Said here and by no other author read

  • check branch remote upstream dirty and staged files
  • verify using repository-defined commands
  • keep unrelated user changes untouched
  • read the git delivery checklist before acting

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.