scbe-gh-powershell-workflow
Manage GitHub workflows and SCBE-AETHERMOORE repository operations from PowerShell 7 preview. Use for authenticated gh CLI actions, PR and branch workflows, CI triage, and SCBE code-aware repository inspections.
Best use case
scbe-gh-powershell-workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Manage GitHub workflows and SCBE-AETHERMOORE repository operations from PowerShell 7 preview. Use for authenticated gh CLI actions, PR and branch workflows, CI triage, and SCBE code-aware repository inspections.
Teams using scbe-gh-powershell-workflow should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/scbe-gh-powershell-workflow/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scbe-gh-powershell-workflow Compares
| Feature / Agent | scbe-gh-powershell-workflow | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Manage GitHub workflows and SCBE-AETHERMOORE repository operations from PowerShell 7 preview. Use for authenticated gh CLI actions, PR and branch workflows, CI triage, and SCBE code-aware repository inspections.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# SCBE GitHub + PowerShell 7 Workflow Use this skill when the user asks to perform `gh` operations, inspect or manipulate SCBE-related GitHub repos, or run GitHub workflow/debug tasks from PowerShell 7 preview. ## Prerequisites - Use PowerShell 7+ preview: - `"$($PSVersionTable.PSVersion.ToString())"` should show `7.6.0-preview.6` or later in this environment. - Ensure `gh` is installed and authenticated. - For SCBE repo actions, prefer: - local working copy at `C:\Users\issda\SCBE-AETHERMOORE` - local workspace at `C:\Users\issda\SCBE-AETHERMOORE-working` - or fallback remote target `issdandavis/SCBE-AETHERMOORE`. - For workflow-architect / demo systems: - `C:\Users\issda\Kiro_Version_ai-workflow-architect` - `C:\Users\issda\scbe-aethermoore-demo` ## Core GH bootstrap - Check auth: - `gh auth status` - Re-authenticate if needed: - `gh auth login -h github.com` - Confirm repo aliases: - `gh alias list` ## PR and branch workflow - Checkout a PR by number: - `gh pr checkout 204 --repo issdandavis/SCBE-AETHERMOORE` - If `cl` alias is preferred: - `gh alias set cl 'pr checkout' --clobber` - `gh cl 204 --repo issdandavis/SCBE-AETHERMOORE` - View PR without a local checkout: - `gh pr view 204 --repo issdandavis/SCBE-AETHERMOORE` - List PRs: - `gh pr list --repo issdandavis/SCBE-AETHERMOORE` ## Repo context rules (important) - `gh` commands that depend on git metadata require being inside a local git repo. - From any directory, pass `--repo OWNER/REPO` to inspect objects without local checkout. - Never assume `gh repo view` without args will work outside a git checkout. ## Multi-repo roots - SCBE: `C:\Users\issda\SCBE-AETHERMOORE` and `C:\Users\issda\SCBE-AETHERMOORE-working` - Workflow architect: `C:\Users\issda\Kiro_Version_ai-workflow-architect` - SCBE demo: `C:\Users\issda\scbe-aethermoore-demo` ## SCBE operational checks - Before CI triage, gather status: - `gh status --repo issdandavis/SCBE-AETHERMOORE` - Inspect workflow runs: - `gh run list --repo issdandavis/SCBE-AETHERMOORE --limit 20` - `gh run view <run-id> --repo issdandavis/SCBE-AETHERMOORE --log` - Open PR diff review flow: - `gh pr diff <pr>` if local checkout exists - otherwise `gh pr view <pr> --repo issdandavis/SCBE-AETHERMOORE --json files` ## SCBE code assistant - Use the code assistant script for repeatable, context-aware workflow actions: - `.\scripts\scbe_code_assistant.ps1 -Mode status` - `.\scripts\scbe_code_assistant.ps1 -Mode checkout-pr -Pr 204` - `.\scripts\scbe_code_assistant.ps1 -Mode inspect-pr -Pr 204` - `.\scripts\scbe_code_assistant.ps1 -Mode run-list -Limit 30` - `.\scripts\scbe_code_assistant.ps1 -Mode run-view -RunId 1234567890` - `.\scripts\scbe_code_assistant.ps1 -Mode scbe-self-heal -RepoPath 'C:\Users\issda\SCBE-AETHERMOORE-working'` - `.\scripts\scbe_code_assistant.ps1 -Mode scbe-self-heal -SelfHealScript 'C:\path\to\script.ps1'` - `.\scripts\scbe_code_assistant.ps1 -Mode self-heal-catalog` - `.\scripts\scbe_code_assistant.ps1 -Mode code-assistant-scan` - `.\scripts\scbe_code_assistant.ps1 -Mode workflow-architect-scan -RepoPath 'C:\Users\issda\Kiro_Version_ai-workflow-architect'` - `.\scripts\scbe_code_assistant.ps1 -Mode aethermoore-demo-scan -RepoPath 'C:\Users\issda\scbe-aethermoore-demo'` - `.\scripts\scbe_code_assistant.ps1 -Mode llm-training -NotionDocPath 'C:\Users\issda\notion-export' -TrainingManifestOutput 'C:\Users\issda\scbe-training-manifest.json'` - `.\scripts\scbe_code_assistant.ps1 -Mode ai-nodal-dev-specialist -NotionDocPath 'C:\Users\issda\notion-export'` - `.\scripts\scbe_code_assistant.ps1 -Mode self-heal-catalog -RepoPath 'C:\Users\issda\SCBE-AETHERMOORE-working'` ## 3 inspired-system capabilities included - Workflow-architect assistant surfaces: scan code-assistant, proposal, and autonomy APIs. - SCBE-demo self-healing discovery: prioritize `SCBE-AETHERMOORE-v3.0.0/src/selfHealing/*`. - Cross-repo cataloging: discover and run known healing scripts across all configured SCBE-compatible repos. - LLM / AI Nodal Dev Specialist preflight modes: - `llm-training`: generate non-invasive training manifest + reality checks - `ai-nodal-dev-specialist`: adds planner-focused guidance and same manifest output ## Hidden next-coder marker - A non-code handoff marker is maintained at: - `.\.scbe-next-coder-marker.json` - This file contains mode handoff notes and does not modify product code. ## Three SCBE-inspired workflows - Governance envelope audit: - `.\scripts\scbe_code_assistant.ps1 -Mode scbe-governance` - Finds and validates governance decision and envelope-related surfaces in the repo. - Interoperability parity guard: - `.\scripts\scbe_code_assistant.ps1 -Mode scbe-kdf` - Checks for KDF and serialization hotspots that can break cross-language parity. - CI-to-code trace: - `.\scripts\scbe_code_assistant.ps1 -Mode scbe-ci` - Correlates recent failed runs with likely source files for rapid remediation. For deeper SCBE context on these flows, read: - `references/scbe-system-inspired-flows.md` - `references/scbe-workflow-architect-integration.md` - For integration behavior and known self-healing assets, read: - `references/scbe-workflow-architect-integration.md` ## PowerShell 7 execution notes - Use quoted paths for repo and script paths with spaces. - Prefer one command per line and avoid implicit shell parsing assumptions from legacy PowerShell. - When a command fails with “not a git repository,” move into the correct local repo path and rerun with explicit `--repo` only as fallback. ## Internet/research workflow - Use direct repository-native context first (`gh`, local files, commit/history). - Use web search only for up-to-date external references (GitHub docs, API changes, upstream packages). - Keep external references bounded to the exact question to reduce time and ambiguity. ## Failure handling - If `gh` says “Could not create alias”: - rerun with `--clobber`. - If syntax errors appear (`Invalid workflow file`): - inspect YAML for scalar typos and indentation in workflow files immediately. - If `gh auth` indicates invalid token: - re-run `gh auth login` and re-check with `gh auth status`. ## Operational safety - Do not run destructive git operations unless explicitly requested. - Avoid pushing secrets in output or logs.
Related Skills
scbe-training-pair-authoring
Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.
scbe-spin-conversation-engine
Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.
scbe-research-training-bridge
Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.
scbe-document-management
Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.
scbe-colab-bridge
Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.
scbe-claim-to-code-evidence
Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.
scbe-autonomous-worker-productizer
Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.
scbe-code-scanning-ops
Operate GitHub code scanning and CodeQL remediation for SCBE repositories. Use when triaging code-scanning alerts, mapping alert classes to fix patterns, validating targeted regressions, or wiring dedicated CodeQL workflows and runbooks into the repo.
scbe-world-anvil-lore-rag-7th-tongue
Build and operate a lore-focused RAG system using World Anvil exports and SCBE docs, with deterministic Claude/Codex cross-talk packets for handoff. Use when users ask to structure lore canon retrieval, sync worldbuilding data, enforce citation-grounded generation, or coordinate a 7th Tongue overseer lane across multiple AI agents.
scbe-webtoon-book-conversion
Convert The Six Tongues Protocol and related manuscript sections into webtoon/manhwa storyboard packets, episode roadmaps, panel expansion plans, and image-generation-ready prompt lanes. Use when extending the series storyboard, adapting book chapters into vertical scroll episodes, or keeping art generation tied to canon instead of drifting into generic fantasy panels.
scbe-voice-render-verification
Govern and verify SCBE voice rendering work that maps Langues weighting into breath, phase, and Layer 14 audio-axis packets. Use when implementing or reviewing `scripts/voice_gen_hf.py`, emitting sidecar voice packets, validating canonical tongue ordering, tuning breath planning or phase timing, or keeping voice docs and code aligned with `docs/LANGUES_WEIGHTING_SYSTEM.md` and `docs/specs/SCBE_VOICE_EMOTIONAL_TIMBRE_SYSTEM.md`.
scbe-universal-synthesis
Orchestrate all installed Codex skills through an auto-updating synthesis matrix with Sacred Tongues routing, emotion/intent metadata, and decodable lexicon packets tied to established SCBE characters. Use when the user asks for cross-skill coordination, auto skill updates, multi-skill routing, or Sacred Tongues intent mapping.