メニュー
Monitor and operate GitHub Actions for the proxysss repository with the GitHub CLI. Use when checking CI/release workflow status, reading failed job logs, rerunning workflows, inspecting release assets, or when the user asks to watch GitHub Actions with gh.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Inspect, validate, and fix GitHub Actions workflows in this repository. Use when working on .github/workflows, actionlint, runner labels, checkout/setup action versions, CI failures, workflow packaging, release automation, or local Actions verification with act and gh.
Built-in proxysss ACME DNS-01 provider strategies. Use when adding, fixing, or configuring wildcard SSL via http.tls.acme.challenge=dns01 and http.tls.acme.dns.provider for cloudflare, aliyun_cn, aliyun_intl, tencent, volcengine, aws, azure, or google.
Install, update, initialize, verify, and hand over proxysss to an AI agent. Use when Codex is asked to one-click install proxysss, replace nginx with proxysss, bootstrap proxysss config/service files, verify default ports 80 and 7777, or prepare proxysss so another agent can inspect and operate it.
| name | gh-cli |
| description | Monitor and operate GitHub Actions for the proxysss repository with the GitHub CLI. Use when checking CI/release workflow status, reading failed job logs, rerunning workflows, inspecting release assets, or when the user asks to watch GitHub Actions with gh. |
gh is installed: gh --versiongh auth statusgh auth login (repo + workflow scopes).Default repository: neko233-com/proxysss
gh repo view neko233-com/proxysss --json name,defaultBranchRef
gh workflow list -R neko233-com/proxysss
gh run list -R neko233-com/proxysss --limit 10
gh release list -R neko233-com/proxysss --limit 5
| Workflow | File | Purpose |
|---|---|---|
ci | .github/workflows/ci.yml | actionlint, rustfmt, clippy, tests, multi-OS build |
deploy | .github/workflows/deploy.yml | package bundles |
release | .github/workflows/release.yml | tag builds + GitHub Release assets |
# Latest failed runs
gh run list -R neko233-com/proxysss --status failure --limit 5
# Inspect one run
gh run view <run-id> -R neko233-com/proxysss
# Failed step logs only
gh run view <run-id> -R neko233-com/proxysss --log-failed
# Watch an in-progress run
gh run watch <run-id> -R neko233-com/proxysss --exit-status
Filter by workflow:
gh run list -R neko233-com/proxysss --workflow=ci.yml --limit 5
gh run list -R neko233-com/proxysss --workflow=release.yml --limit 5
After pushing a v* tag:
gh run list -R neko233-com/proxysss --workflow=release.yml --limit 3
gh release view vX.Y.Z -R neko233-com/proxysss
Verify all six assets exist:
proxysss-windows-amd64.zipproxysss-windows-arm64.zipproxysss-linux-amd64.tar.gzproxysss-linux-arm64.tar.gzproxysss-darwin-amd64.tar.gzproxysss-darwin-arm64.tar.gzIf publish fails on Extract current changelog, the tagged commit is missing ## vX.Y.Z in CHANGELOG.md. Fix the changelog on main, bump version if needed, commit, then push a new tag on that commit (do not rely on rerunning an old tag).
Cargo.toml version and add ## vX.Y.Z - YYYY-MM-DD to CHANGELOG.md.main and wait for green ci (gh run watch on the latest CI run).git tag vX.Y.Z && git push origin vX.Y.Z.gh run list -R neko233-com/proxysss --workflow=release.yml --limit 1 then gh run watch <id> --exit-status.gh release view vX.Y.Z -R neko233-com/proxysss.Workflows use upload-artifact@v6 / download-artifact@v6 (Node.js 24 LTS). Do not downgrade to v4.
gh run rerun <run-id> -R neko233-com/proxysss --failed
gh workflow run release.yml -R neko233-com/proxysss --ref main
When reporting Actions status to the user, include:
success, failure, in_progress)gh run view)--log-failed.github/skills/github-actions/SKILL.md — edit and validate workflow YAML locallyskills/proxysss-install/SKILL.md — install released binaries after a green release run