skills.rest
buildertrend
buildertrendOFFICIAL
Explore all skills by this author →
Website𝕏@buildertrendGitHub

save

Commits staged Git changes with a ticket-prefixed message for non-technical users.

Updated Mar 24, 2026
Search Tags:#git#version control#frontend#commit#azure devops#non-technical#save changes
One-click install
npx skills add https://github.com/buildertrend/product-toolkit --skill save-buildertrend
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: save
Source: https://github.com/buildertrend/product-toolkit/tree/main/frontend-setup/skills/save
Command: npx skills add https://github.com/buildertrend/product-toolkit --skill save-buildertrend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designers and PMs working in the Buildertrend frontend codebase need to save their work in Git but don't know commit conventions, ticket numbering, or command-line syntax. This Skill handles the entire save flow in plain English. ## Core Features & Use Cases - Automatic change staging: Runs git add and summarizes what changed in plain language, with no technical jargon. - Ticket number detection: Reads the current branch name to extract the Azure DevOps ticket number, or asks the user if one cannot be found. - Standardized commit messages: Formats every save as "ado-<number> <present-tense description>" under 72 characters. - Use Case: A designer updates the header color on a branch named 231499-update-header-color, asks to save their work, and the Skill commits it as "ado-231499 Update header color to match new brand palette". ## Quick Start Ask Claude to save your changes in the Buildertrend frontend project and it will stage, summarize, and commit them with the correct ticket number.

Frequently Asked Questions about save

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save my changes in Git without knowing Git commands?▼

Ask the assistant to save your work and it runs git add, reviews what changed, and creates the commit for you. All output uses plain English instead of terms like commit, stage, or branch.

How to write a commit message with an Azure DevOps ticket number?▼

The message format is ado-<number> followed by a short present-tense description, kept under 72 characters. The ticket number is detected automatically from a branch name that starts with digits.

What happens if my branch name has no ticket number?▼

The Skill asks you for a ticket number in the ado- format. If you cannot provide one, it stops and explains that a ticket number from Azure DevOps is required before saving.

Why does the save skill say there is nothing to save?▼

After running git add and git status, the Skill checks whether any files were added, changed, or removed. If the working tree is clean, it reports that your work is already up to date and stops.

Can I keep working after saving my changes?▼

Yes. Saving creates a single commit, and the Skill tells you that you can continue making changes or proceed to send your work for review as the next step.

Related Skills

Explore More Software Engineering Skills→
tankygranny05tankygranny05
2

clone-worktree-port-bump

Clone a repository into ~/temp and bump *_PORT values in .env by 100 * N.

Community
Advanced
andrewcodesitandrewcodesit

git-publish

Commits, pushes, and opens a draft merge or pull request on the connected git host.

Community
Intermediate
neon-law-foundationneon-law-foundation

web-preview

Run a local web app in Chrome and capture screenshots for verification.

Official
Advanced
J-StaR-Films-StudiosJ-StaR-Films-Studios
23

git-commit-generation

Generate conventional git commit messages from staged changes.

Official
Intermediate