athena-pre-build

Create Git branches from point report verdicts and task types.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Athena-Git-Group/athena-plugin-dev --skill athena-pre-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: athena-pre-build
Source: https://github.com/Athena-Git-Group/athena-plugin-dev/tree/main/skills/athena-pre-build
Command: npx skills add https://github.com/Athena-Git-Group/athena-plugin-dev --skill athena-pre-build

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It automates the process of creating appropriately named Git branches based on point reports, streamlining development workflows and enforcing naming conventions.

Core Features & Use Cases

  • Branch Naming: Derives branch names from point report verdicts, task types, and tickets, ensuring consistency.
  • Context-Aware Creation: Checks existing branches and switches if they already exist, preventing duplication.
  • Use Case: A developer wants to quickly start work on a new feature or fix based on a point report, and this Skill automates branch setup directly from the CI pipeline.

Quick Start

Invoke the skill to automatically produce a Git branch aligned with the current point report and project conventions.

Frequently Asked Questions about athena-pre-build

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

FAQPage Schema
How do I automatically create Git branches from point reports?

To automatically create Git branches from point reports, this skill derives branch names from report verdicts, task types, and tickets. It enforces naming standards and checks for existing branches before safely switching.

How does automated branch creation handle existing branches and local changes?

Automated branch creation handles existing branches by checking for them first and safely switching without disrupting local changes. It prevents duplication and avoids pushing to the remote repository during the workflow.

Can I use this to create different Git branch types like feature and hotfix?

Yes, you can create different Git branch types like feature, bugfix, hotfix, and refactor. The skill determines the appropriate branch type according to task severity and scope derived from the point report outcomes.

What's the best way to enforce Git branch naming conventions in a CI pipeline?

The best way to enforce Git branch naming conventions in a CI pipeline is to automate branch creation directly from point reports. This ensures consistency by deriving names from verdicts, task types, and tickets without manual steps.

Does automated branch creation push branches to the remote repository?

No, automated branch creation does not push branches to the remote repository. It focuses on local branch existence checks and safe switching to prevent disrupting local changes during the development process.