telos-git-core

Enforce corporate Git workflows with branch, PR, and SemVer checks.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/jllopis/ingenieria-del-proposito --skill telos-git-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: telos-git-core
Source: https://github.com/jllopis/ingenieria-del-proposito/tree/main/plugins/telos/skills/git-core
Command: npx skills add https://github.com/jllopis/ingenieria-del-proposito --skill telos-git-core

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill enforces a corporate Git workflow, standardizing branches, PR reviews, and release tagging to reduce chaos and ensure compliance.

Core Features & Use Cases

  • Branch naming aligned with Jira IDs and conventional commits.
  • PR-based reviews, protected branches, and a lifecycle from feature to release.
  • SemVer tagging and synchronized merging back to develop to keep trunk healthy.
  • Applies to dev-team, dev-solo, and documental modes across feature, bugfix, release, and hotfix scenarios.

Quick Start

Create a feature branch from develop, open a PR with a reviewer, and merge to develop following the corporate Git workflow.

Frequently Asked Questions about telos-git-core

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

FAQPage Schema
How do I enforce Jira ID checks in Git branch names across a team?

To enforce Jira ID checks in Git branch names, you need a standardized Git workflow that validates branch naming conventions before pull requests are merged. This skill applies those corporate Git workflow rules automatically across dev-team, dev-solo, and documental contexts.

What is the best way to standardize SemVer tagging and prevent direct commits to protected branches?

Standardizing SemVer tagging and blocking direct commits to protected branches requires a corporate Git workflow that governs the full branch lifecycle. This skill enforces those release tagging rules and PR readiness checks to keep the trunk branch healthy.

How does a Git workflow handle feature, bugfix, release, and hotfix branches?

A corporate Git workflow handles feature, bugfix, release, and hotfix scenarios by enforcing specific branch naming, PR-based reviews, and synchronized merging back to develop. This skill standardizes that lifecycle to ensure compliance and reduce chaos.

Can I use a standardized Git workflow for solo development or only for dev teams?

You can use a standardized Git workflow for solo development as well as team environments. This skill applies corporate Git rules to dev-team, dev-solo, and documental modes, ensuring consistent branch naming and PR reviews across all working contexts.

Why do I need a pull request review workflow with synchronized merging back to develop?

You need a pull request review workflow with synchronized merging back to develop to maintain a healthy trunk and ensure compliance. This skill enforces PR reviews and synchronized merges, preventing unreviewed code from entering protected branches.

Git workflow branch naming and SemVer tagging not working for corporate compliance?

When Git workflow branch naming and SemVer tagging fail to meet corporate compliance, it is usually due to missing enforcement checks. This skill solves it by standardizing branches, validating Jira IDs, and enforcing release tagging rules across all pull requests.