triumph

Present four integration options after tests pass on feature branches.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Milovan-Crowley/Consilium --skill triumph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triumph
Source: https://github.com/Milovan-Crowley/Consilium/tree/main/generated/claude/skills/triumph
Command: npx skills add https://github.com/Milovan-Crowley/Consilium --skill triumph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates decision-making after tests pass by presenting clear, structured options for integrating or discarding work.

Core Features & Use Cases

  • Verifies test status and identifies readiness for integration.
  • Determines a base branch and proposes standardized actions (merge locally, push PR, keep as-is, or discard).
  • Integrates with typical CI/CD workflows to streamline code reviews and release readiness.

Quick Start

Use Triumph after a successful test run to choose the merge, PR, keep, or discard path.

Frequently Asked Questions about triumph

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

FAQPage Schema
How do I automate post-merge decisions after my git tests pass?

Automating post-merge decisions involves verifying test status and detecting the base branch to present structured options for integrating feature branches, such as merging locally, opening a pull request, keeping the branch, or discarding it.

What is the best workflow for integrating a feature branch after a successful test run?

The best workflow for integrating a feature branch evaluates test status and base-branch readiness to guide standardized actions. It structures your path forward by offering local merging, pushing a pull request, keeping the branch, or discarding it entirely.

Can I streamline branch management to choose between opening a pull request or merging locally?

Yes, you can streamline branch management by automating the choice between opening a pull request or merging locally. The process identifies your base branch and test status to present these standardized integration options after development.

Does this post-implementation integration process work with collaborative software projects?

Yes, this post-implementation integration process works directly with collaborative software projects by verifying test status and proposing standardized branch-management actions to streamline code reviews and release readiness within typical CI/CD workflows.

When should I discard a git branch instead of merging or opening a pull request?

You should discard a git branch instead of merging or opening a pull request when post-implementation validation determines the work is no longer needed. This option is presented alongside keeping or integrating the branch based on test status and base-branch detection.