sase_changespecs

Query and manage SASE ChangeSpec lifecycle states and metadata via CLI.

5|Updated Dec 6, 2021

Search Tags:#automation #workflow #code-review #pr-tracking #sase #changespec

Ready to run

npx skills add https://github.com/bbugyi200/dotfiles --skill sase-changespecs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sase_changespecs
Source: https://github.com/bbugyi200/dotfiles/tree/main/home/dot_codex/skills/sase_changespecs
Command: npx skills add https://github.com/bbugyi200/dotfiles --skill sase-changespecs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of tracking SASE ChangeSpecs, providing a unified interface to inspect PR status, dependencies, and blockers across projects.

Core Features & Use Cases

ChangeSpec Inspection: Quickly query current PRs, branches, or specific ChangeSpecs to view status, parentage, and file locations.
Blocker Diagnostics: Identify failed hooks, unresolved review comments, or running processes that prevent a ChangeSpec from moving to the next lifecycle stage.
Use Case: When a feature branch is stuck, use this skill to audit the ChangeSpec tree, identify which specific hook or mentor review is failing, and determine if the spec is ready for submission.

Quick Start

Use the sase_changespecs skill to search for the current status and any blocking issues for the specified changespec name.

Frequently Asked Questions about sase_changespecs

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

FAQPage Schema

How do I check SASE ChangeSpec PR status and dependencies?▼

You can query current PRs and branches to view SASE ChangeSpec status, parentage, and file locations. This interface allows you to inspect dependency chains and track lifecycle states across SASE-managed projects.

Why does my SASE ChangeSpec workflow get stuck during code review?▼

SASE ChangeSpec workflows get stuck due to blockers like failed hooks, unresolved review comments, or running process locks. You can run automated diagnostics to identify the specific hook or mentor review preventing the spec from moving to the next lifecycle stage.

What is the best way to audit a SASE ChangeSpec tree for unresolved blockers?▼

The best way to audit a SASE ChangeSpec tree is to run automated diagnostics that inspect PR status and commit history. This identifies failed hooks, unresolved comments, and active process locks preventing lifecycle progression.

How do I find out if a SASE ChangeSpec is ready for submission?▼

To determine if a SASE ChangeSpec is ready for submission, inspect the ChangeSpec tree to audit its lifecycle state and dependency chains. Resolving identified blockers like failed hooks or active process locks confirms submission readiness.

Can I filter SASE ChangeSpecs by lifecycle state and metadata?▼

Yes, you can filter SASE ChangeSpecs by lifecycle state and metadata using the provided command-line interface. This enables targeted querying of specific ChangeSpecs to inspect their current PR status and blocking issues.