skills.rest
optave
optaveOFFICIAL
Explore all skills by this author →
WebsiteGitHub

titan-close

Split Git commits into focused PRs and generate a Titan audit report.

86|20|Updated Feb 21, 2026
Search Tags:#automation#git#audit#metrics#reporting#titan#pr-splitting
One-click install
npx skills add https://github.com/optave/ops-codegraph-tool --skill titan-close
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: titan-close
Source: https://github.com/optave/ops-codegraph-tool/tree/main/.claude/skills/titan-close
Command: npx skills add https://github.com/optave/ops-codegraph-tool --skill titan-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating Titan audits across multiple phases can be error-prone and time-consuming; Titan Close automates the consolidation into focused PRs, issue tracking, and a final, auditable report.

Core Features & Use Cases

  • Split a feature branch's commits into focused PRs to simplify reviews and merges.
  • Compile a comprehensive Titan audit report with before/after metrics and drift awareness.
  • Generate an integrated issue tracker and preserve a clear audit trail for governance and compliance.

Quick Start

Run titan-close on your current branch to produce PRs and a Titan audit report.

Frequently Asked Questions about titan-close

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

FAQPage Schema
How do I split a feature branch's commits into focused PRs?▼

Splitting commits into focused PRs requires orchestrating a multi-phase Git audit workflow that groups related changes and publishes pull requests in strict dependency order. This approach simplifies code reviews by isolating broad feature branches into focused, manageable merges.

How do I generate an audit report with before and after metrics for Git changes?▼

Generating a Git audit report with before and after metrics involves running an automated workflow that collects codegraph data and produces a drift-aware executive summary. This ensures governance compliance and preserves a clear audit trail for your repository.

Do I need the gh CLI and codegraph tooling to automate Git PR splitting?▼

Yes, automating Git PR splitting requires the gh CLI to publish pull requests and codegraph tooling to collect metrics. Git is also required to run the multi-phase audit workflow and group commits into focused, dependency-ordered PRs.

Can I dry-run a Git commit splitting workflow before publishing pull requests?▼

Yes, you can dry-run the Git commit splitting workflow to preview the generated PRs and audit report without publishing changes. This verifies dependency ordering and metrics grouping before executing the actual pull request creation.

What is the best way to coordinate multi-phase code changes in Git for compliance?▼

The best way to coordinate multi-phase Git code changes for compliance is to use an automated audit workflow with distinct phases like Recon, Gauntlet, Sync, Forge, Grind, and Gate. This produces dependency-ordered PRs and a comprehensive drift-aware report.

Related Skills

Explore More Software Engineering Skills→
KarlinskySKarlinskyS

github-auth

Configure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI login.

Community
Intermediate
blackplume233blackplume233
12

pr-handler

Automate the five-phase PR gatekeeping workflow for Draft PRs.

Community
Advanced
abnejsolutions-altabnejsolutions-alt

compliance-tracker

Analyze controls, evidence, and findings to produce compliance dashboards and reports.

Community
Advanced
julianobarbosajulianobarbosa
7

uri-scheme

Manage Git history across branches with rebasing, cherry-picking, and reflog recovery.

Community
Advanced