Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

github-workflows

Sterne7.749

Forks776

Aktualisiert26. März 2026 um 04:18

Work with GitHub Actions CI/CD workflows - read live syntax, monitor runs, and debug failures. Use when writing, running, or debugging GitHub Actions workflows.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

gsd-build

gsd-build/gsd-2

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

10 Dateien

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

gsd-headless

gsd-build/gsd-2

Orchestrate GSD (Get Shit Done) projects programmatically via headless CLI. Use when an agent needs to create milestones from specs, execute software development workflows, monitor task progress, check project status, or control GSD execution (pause/stop/skip/steer). Triggers on requests to "run gsd", "create milestone", "execute project", "check gsd status", "orchestrate development", "run headless workflow", or any programmatic interaction with the GSD project management system. Essential for building orchestrators that coordinate multiple GSD workers.

2026-05-217.7k

forensics

gsd-build/gsd-2

Post-mortem a failed GSD auto-mode run. Traces from symptom to root cause using `.gsd/activity/*.jsonl`, `.gsd/journal/YYYY-MM-DD.jsonl`, `.gsd/metrics.json`, and `.gsd/auto.lock`. Produces a filing-ready bug report with file:line references and a concrete fix suggestion. Use when asked to "forensics", "post-mortem", "why did auto-mode fail", "trace the stuck loop", "debug the crash", after `/gsd forensics` is invoked, or when a session ended in an unexpected terminal state. Reads existing artifacts — does NOT re-run anything.

2026-05-147.7k

gsd-orchestrator

gsd-build/gsd-2

Build software products autonomously via GSD headless mode. Handles the full lifecycle: write a spec, launch a build, poll for completion, handle blockers, track costs, and verify the result. Use when asked to "build something", "create a project", "run gsd", "check build status", or any task that requires autonomous software development via subprocess.

2026-05-117.7k

create-gsd-extension

gsd-build/gsd-2

Create, debug, and iterate on GSD extensions (TypeScript modules that add tools, commands, event hooks, custom UI, and providers to GSD). Use when asked to build an extension, add a tool the LLM can call, register a slash command, hook into GSD events, create custom TUI components, or modify GSD behavior. Triggers on "create extension", "build extension", "add a tool", "register command", "hook into gsd", "custom tool", "gsd plugin", "gsd extension".

2026-05-087.7k

verify-before-complete

gsd-build/gsd-2

Block completion claims until verification evidence has been produced in the current message. Use before marking a task/slice/milestone complete, before creating a commit or PR, before saying "it works" or "tests pass", and any time you are about to claim work is done. The rule is: evidence before claims, always — running the verification must happen now, not "earlier in the session". Fresh output or no claim.

2026-05-017.7k

lint

gsd-build/gsd-2

Lint and format code. Auto-detects ESLint, Biome, Prettier, or language-native formatters and runs them with auto-fix. Reports remaining issues with actionable suggestions.

2026-04-277.7k

name	github-workflows
description	Work with GitHub Actions CI/CD workflows - read live syntax, monitor runs, and debug failures. Use when writing, running, or debugging GitHub Actions workflows.

GitHub Workflows

Mission: Work with GitHub Actions without using stale training data. All syntax, versions, and parameters come from live sources.

Structural Principle

All CI operations go through ci_monitor.cjs. Never reach for gh CLI directly — the script wraps it with observable output.

Primary Tool: ci_monitor.cjs

Path: scripts/ci_monitor.cjs

node scripts/ci_monitor.cjs <command>

Before using any command:

Run --help to discover available arguments

Routing Table:

When You Need	Command
List recent runs	`runs [--branch <name>]`
Monitor running workflow	`watch <run-id>`
Fail fast in scripts	`fail-fast <run-id>`
See why run failed	`log-failed <run-id>`
Test pass/fail counts	`test-summary <run-id>`
Check action versions	`check-actions [file]`
Search logs	`grep <run-id> --pattern <regex>`
Wait for deployment	`wait-for <run-id> <job> --keyword <text>`

Documentation Routing

Base URL: https://docs.github.com/en/actions/reference/workflows-and-actions/

Before writing any workflow syntax:

Fetch the relevant .md file from the URL above
Read only the section you need

Task	File	Section
Create workflow	workflow-syntax.md	`name`, `on`, `jobs`
Set triggers	workflow-syntax.md	`on`
Set permissions	workflow-syntax.md	`permissions`
Concurrency	workflow-syntax.md	`concurrency`
Reusable workflow	workflow-syntax.md	`on.workflow_call`
Annotations	workflow-commands.md	"Setting an error/warning/notice message"
Output variables	workflow-commands.md	"Environment files"
Conditionals	expressions.md	"Operators", "Functions"
Contexts	contexts.md	" context"
Events	events-that-trigger-workflows.md	Event tables

Version Verification

What	Where
Action versions	`node ci_monitor.cjs check-actions <file>`
Node.js LTS	`curl -s https://nodejs.org/dist/index.json \| jq '.[0].version'`

Validation Constraint

"No errors" is not validation. Prove observable change:

BEFORE: [specific state]
AFTER:  [different state]
EVIDENCE: [output from ci_monitor.cjs]

References

references/gh/SKILL.md — gh CLI reference