celebrimbor

Name: celebrimbor
Availability: InStock
Author: LarryHsiao

Automate approved counsel into code changes and a forge PR/MR workflow.

Updated Mar 19, 2026

Search Tags:#automation #workflow #devops #ticket #pull-request #forge #counsel

Ready to run

npx skills add https://github.com/LarryHsiao/Skadi --skill celebrimbor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: celebrimbor
Source: https://github.com/LarryHsiao/Skadi/tree/main/skills/celebrimbor
Command: npx skills add https://github.com/LarryHsiao/Skadi --skill celebrimbor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform and operationalize an approved counsel by turning it into concrete code changes, branching from the approved base, and invoking the forge workflow to produce a PR/MR without manual handoffs.

Core Features & Use Cases

Reads the approved counsel from the ticket thread and implements the Steps into the repo.
Creates a feature branch from the base, opens a PR/MR via the forge hook, and posts the resulting status back to the ticket as [GWAITH].
Enforces a one-ticket-per-invocation model to keep scope bounded and auditable.

Quick Start

Invoke /celebrimbor with the tracker and project to begin forging the approved counsel into code.

Frequently Asked Questions about celebrimbor

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

FAQPage Schema

How do I automate code changes from an approved ticket in YouTrack or Jira?▼

To automate code changes from an approved ticket, you use a workflow that reads the approved counsel, implements the steps into your repository, and opens a pull request. This Skill executes that tracker-based development flow end-to-end.

What is the best way to turn an approved development counsel into a pull request automatically?▼

Turning an approved counsel into a pull request automatically requires branching from the base, implementing the steps, and invoking a forge hook. This Skill automates that entire process to produce a PR or MR without manual handoffs.

Does this automation support single-ticket end-to-end deliveries from base to PR?▼

Yes, this automation supports single-ticket end-to-end deliveries from base to PR. It enforces a one-ticket-per-invocation model to keep the development scope bounded and auditable for each request.

How do I post a forge workflow status back to a Jira or YouTrack ticket?▼

To post a forge workflow status back to a Jira or YouTrack ticket, the automation opens a PR via the forge hook and posts the resulting status back to the ticket thread as [GWAITH].

Can I implement multiple tickets in a single workflow invocation?▼

No, you cannot implement multiple tickets in a single workflow invocation. The process enforces a one-ticket-per-invocation model, ensuring that the scope of automated code changes remains strictly bounded and auditable.