ワンクリックでManusで任意のスキルを実行

始める

$pwd:

github-actions-ci

Name: Github Actions Ci
Author: willyu1007

// GitHub Actions CI skill: integrate automated tests (web/api/mobile/perf) with consistent artifacts.

Manusで実行

$ git log --oneline --stat

stars:0

forks:0

updated:2026年2月10日 01:16

ファイルエクスプローラー

7 ファイル

SKILL.md

readonly

name: github-actions-ci description: GitHub Actions CI skill: integrate automated tests (web/api/mobile/perf) with consistent artifacts.

GitHub Actions CI Integration (workflow)

Operating mode (token-efficient)

Treat this skill as a router + governor.
Do not load multiple procedures. Select exactly one procedure below and follow the chosen procedure end-to-end.

Routing (pick one procedure)

Task	Open this procedure	Optional templates
Enable/adjust test jobs (web/api/mobile/perf)	`reference/procedures/enable-test-jobs.md`	`reference/templates/github-actions/ci.yml`
Standardize artifacts + reporting	`reference/procedures/artifacts-and-reporting.md`	—
Troubleshoot CI failures	`reference/procedures/troubleshoot.md`	—

Shared non-negotiables (apply to all procedures)

Test command contract
- Each suite must have a single deterministic command runnable in CI:
  - API (Newman): pnpm test:api
  - Web (Playwright): pnpm test:e2e:playwright
  - Web (Cypress): pnpm test:e2e:cypress
  - Perf (k6): pnpm test:perf:k6 or direct runner (k6 run ... / docker run grafana/k6 ...)
  - Mobile: pnpm test:mobile:<detox|maestro|appium>
- Commands must:
  - exit non-zero on test failures
  - write artifacts to artifacts/<suite>/
Artifacts are mandatory
- Always upload artifacts even on failure: artifacts/ or a well-defined subset.
- Avoid writing artifacts outside the workspace.
Secrets management
- All credentials must use GitHub Actions secrets.
- Never echo secrets in logs.
- Prefer OIDC + short-lived tokens if your org supports OIDC.
Gating policy
- PR gating should run only fast, stable suites (typically API + 1 web suite + perf smoke).
- Heavy suites (mobile, load/stress) should be scheduled or manually dispatched.

Minimal inputs before changing CI

Which workflows exist today
Which suites are PR-gated vs scheduled
Required secrets and how they map to env vars
Node version and OS runners required (ubuntu vs macOS)
Artifact retention needs and size constraints

Verification

If you changed skills:
- node .ai/scripts/lint-skills.mjs --strict
- node .ai/skills/features/ci/github-actions-ci/scripts/validate-skill.mjs
If you changed workflow YAML:
- Run a PR test run (or use workflow_dispatch) and confirm:
  - correct suite execution
  - artifacts uploaded
  - failures show clear signals

Boundaries

Do not hardcode secrets or base URLs in workflow YAML.
Do not add third-party actions without reviewing supply-chain risk.
Do not make PR gating flaky; move unstable suites to scheduled runs.

related-skills.json

同じリポジトリ

apply-frontend-common-patterns.md

from "willyu1007/The-UniAssist-Entrance-App"

Apply local React patterns (derived state, memoization, callback stability, controlled inputs) to improve predictability and render efficiency inside components. Primary intent: component-internal logic quality and render behavior; complements but does not replace routing/data/styling skills.

2026-02-100

apply-frontend-ui-guidelines.md

from "willyu1007/The-UniAssist-Entrance-App"

Orchestrate end-to-end frontend feature implementation across components, hooks, routing, data fetching, styling, and user-visible states with consistent architecture and verification. Primary intent: cross-cutting implementation alignment; pairs with specialized skills when one concern needs deeper treatment.

2026-02-100

build-react-components.md

from "willyu1007/The-UniAssist-Entrance-App"

Build or refactor React components with typed props, clear composition, and explicit interaction/loading/empty/error behavior. Primary intent: component contract and behavior correctness; pairs with styling or design-direction skills for visual decisions.

2026-02-100

frontend-design.md

from "willyu1007/The-UniAssist-Entrance-App"

Define and execute a distinctive visual direction for net-new UI or brand refresh work (art direction, typography, color, motion, composition), then deliver a polished reference implementation. Primary intent: creative design direction and visual differentiation; pairs well with style-frontend-ui and build-react-components for engineering hardening.

2026-02-100

style-frontend-ui.md

from "willyu1007/The-UniAssist-Entrance-App"

Implement and normalize UI styling within an existing design system using theme tokens, reusable style primitives, responsive rules, and accessibility checks. Primary intent: styling execution consistency; can follow frontend-design when a creative direction needs maintainable implementation.

2026-02-100

handle-frontend-loading-and-errors.md

from "willyu1007/The-UniAssist-Entrance-App"

Implement resilient loading/empty/error/permission/retry UX states for async interfaces with user-safe messaging and recoverable flows. Primary intent: failure-state UX quality; pairs with component, data-fetching, and UI-guideline skills when needed.

2026-02-100

package.json

"author": "willyu1007"

"repository": "willyu1007/The-UniAssist-Entrance-App"

GitHub リポジトリを開く Creator のリポジトリを見る

$ install --global

$ download --local

Manusで実行

$ useful --forSOC

ソフトウェア開発者コンピュータ・数学職15-1252L4

GitHub Actions CI Integration (workflow)

Operating mode (token-efficient)

Treat this skill as a router + governor.

Do not load multiple procedures. Select exactly one procedure below and follow the chosen procedure end-to-end.

Routing (pick one procedure)

Task

Open this procedure

Optional templates

Enable/adjust test jobs (web/api/mobile/perf)

reference/procedures/enable-test-jobs.md

reference/templates/github-actions/ci.yml

Standardize artifacts + reporting

reference/procedures/artifacts-and-reporting.md

—

Troubleshoot CI failures

reference/procedures/troubleshoot.md

—

Shared non-negotiables (apply to all procedures)

Test command contract

Each suite must have a single deterministic command runnable in CI:
- API (Newman): pnpm test:api
- Web (Playwright): pnpm test:e2e:playwright
- Web (Cypress): pnpm test:e2e:cypress
- Perf (k6): pnpm test:perf:k6 or direct runner (k6 run ... / docker run grafana/k6 ...)
- Mobile: pnpm test:mobile:<detox|maestro|appium>
Commands must:
- exit non-zero on test failures
- write artifacts to artifacts/<suite>/

Artifacts are mandatory

Always upload artifacts even on failure: artifacts/ or a well-defined subset.
Avoid writing artifacts outside the workspace.

Secrets management

All credentials must use GitHub Actions secrets.
Never echo secrets in logs.
Prefer OIDC + short-lived tokens if your org supports OIDC.

Gating policy

PR gating should run only fast, stable suites (typically API + 1 web suite + perf smoke).
Heavy suites (mobile, load/stress) should be scheduled or manually dispatched.

Minimal inputs before changing CI

Which workflows exist today

Which suites are PR-gated vs scheduled

Required secrets and how they map to env vars

Node version and OS runners required (ubuntu vs macOS)

Artifact retention needs and size constraints

Verification

If you changed skills:

node .ai/scripts/lint-skills.mjs --strict
node .ai/skills/features/ci/github-actions-ci/scripts/validate-skill.mjs

If you changed workflow YAML:

Run a PR test run (or use workflow_dispatch) and confirm:
- correct suite execution
- artifacts uploaded
- failures show clear signals

Boundaries

Do not hardcode secrets or base URLs in workflow YAML.

Do not add third-party actions without reviewing supply-chain risk.

Do not make PR gating flaky; move unstable suites to scheduled runs.

github-actions-ci

name: github-actions-ci description: GitHub Actions CI skill: integrate automated tests (web/api/mobile/perf) with consistent artifacts.

GitHub Actions CI Integration (workflow)

Operating mode (token-efficient)

Routing (pick one procedure)

Shared non-negotiables (apply to all procedures)

Minimal inputs before changing CI

Verification

Boundaries

このリポジトリの他の Skills

このリポジトリの他の Skills

name: github-actions-ci description: GitHub Actions CI skill: integrate automated tests (web/api/mobile/perf) with consistent artifacts.

GitHub Actions CI Integration (workflow)

Operating mode (token-efficient)

Routing (pick one procedure)

Shared non-negotiables (apply to all procedures)

Minimal inputs before changing CI

Verification

Boundaries