skills.rest
jsnbuchanan
jsnbuchananCOMMUNITY
Explore all skills by this author →
Website𝕏@jsnbuchananGitHub

push-spec

Commit changes, push branches, and open PRs from vault specs.

Updated Mar 28, 2026
Search Tags:#automation#git#push#pr#conventional-commit#spec-workflow#vault-spec
One-click install
npx skills add https://github.com/jsnbuchanan/claude-code-spec-skills-example --skill push-spec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: push-spec
Source: https://github.com/jsnbuchanan/claude-code-spec-skills-example/tree/main/.claude/skills/push-spec
Command: npx skills add https://github.com/jsnbuchanan/claude-code-spec-skills-example --skill push-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end Git workflow for spec-driven changes by committing, pushing branches, and opening PRs with bodies derived from vault specs.

Core Features & Use Cases

  • Commit changes with conventional commits to reflect the change type.
  • Push branches and create PRs whose titles and bodies summarize the Why/How/What from vault specs.
  • Progress the spec lifecycle by advancing vault specs upon PR actions and ensuring traceability.

Quick Start

Run the push-spec skill after editing the spec to automatically commit, push the branch, and open a PR with a body derived from the vault spec.

Frequently Asked Questions about push-spec

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

FAQPage Schema
How do I automate opening a GitHub PR from a spec-driven development workflow?▼

You can automate the spec-driven Git workflow by committing changes with conventional-commit messages, pushing branches, and opening a PR with a body derived from vault specs. The PR titles and descriptions summarize the Why, How, and What from the spec metadata.

What is conventional-commit enforcement for spec lifecycle progression?▼

Conventional-commit enforcement for spec lifecycle progression ensures that Git commit messages follow a standardized format. This automation uses vault metadata to derive PR titles and bodies, progressing vault specs from draft or ready to implemented upon PR actions.

How do I create a PR with a body derived from a vault spec?▼

To create a PR derived from a vault spec, run the automation after editing the spec. It commits changes using conventional commits, pushes the branch, and opens a PR with the body summarizing the spec's Why, How, and What, ensuring traceability.

Does the push-spec workflow require the GitHub CLI to open pull requests?▼

Yes, the workflow integrates with the GitHub CLI to open pull requests and progress the spec lifecycle. It uses the GitHub CLI alongside Git to push branches and create PRs that reflect changes from vault specs in code repositories.

Can I use vault specs to progress from draft to implemented in a code repository?▼

Yes, vault specs can be progressed from draft or ready to implemented. The automation moves vault specs through their lifecycle by committing changes, pushing branches, and opening PRs that reflect the implemented changes in the code repository.

Related Skills

Explore More Software Engineering Skills→
CHENyiru3CHENyiru3

github-pr-workflow

Automate GitHub PR workflows including branch creation, CI monitoring, and merges.

Community
Advanced
SimpleEveSimpleEve
30

eo-archive

Merge approved Spec Deltas into a module's spec.md and archive the change.

Community
Advanced
GeneralJerelGeneralJerel
6

create-pr-description

Generate structured PR descriptions from staged git changes and PR conventions.

Community
Intermediate
FlatbreadLabsFlatbreadLabs
64

mergify-stack

Automate stacked Git branch and dependent pull request management.

Official
Advanced