القائمة
Use when bumping the Wayland version: update package.json, run checks, branch, commit, push, create PR, wait for merge, tag release.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Wayland's own how-to guide: explains what Wayland can do and gives the exact steps to operate it. Covers what can Wayland do, connecting an AI provider or model, creating an assistant, building and launching a workflow, setting up a team, scheduling a task, connecting an MCP server or outside tool, and switching models or using Flux Auto. Use when the user asks what Wayland can do, what features exist, how do I connect a provider or model, how do I add Claude or OpenAI or Gemini, how do I create or edit an assistant, how do I build or run a workflow, how do I set up a team of assistants, how do I schedule a task or set up a recurring job, how do I connect an MCP server or outside tool, or how do I switch models or turn on Flux Auto automatic model routing. Do NOT use when the user wants help with a non-Wayland task (writing, coding, research, document creation) — those have their own skills; this skill is only about operating Wayland itself.
Security operations center expertise covering SIEM query writing, alert triage workflows, incident investigation procedures, IOC analysis, threat hunting techniques, playbook design, log analysis patterns, Splunk and Elastic SIEM queries, alert fatigue reduction, escalation procedures, and shift handoff practices. Use when the user asks about soc analyst, soc analyst best practices, or needs guidance on soc analyst implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.
Orchestrates the process of deploying a software application to production, from CI pipeline verification through monitoring confirmation, chaining six software-development skills into a structured release workflow. Use when the user needs to deploy an application to production with a repeatable, safe process that includes database migration, monitoring, and rollback planning. Do NOT use for local development setup, staging-only deployments, or infrastructure provisioning without application deployment.
End-to-end workflow for building a complete DevOps pipeline from an empty repository through CI/CD, infrastructure as code, monitoring, alerting, and incident response. Covers the full lifecycle from first commit to production-grade operations. Use when the user wants to devops pipeline from scratch or needs a structured multi-step process for this goal. Do NOT use when the request is a single-step task or requires professional advice beyond educational guidance.
Orchestrates end-to-end production incident management from detection through resolution and retrospective, chaining five skills into a complete incident lifecycle pipeline. Covers triage, log investigation, monitoring verification, documentation, and team retrospective. Use when handling a production incident that affects users and requires coordinated response, investigation, resolution, and follow-up. Do NOT use for non-production issues, minor bugs that do not affect users, or planned maintenance activities.
Orchestrates the full incident lifecycle from initial triage through postmortem documentation, chaining five software-development skills into a structured incident management workflow. This workflow chains the incident-response skill with logging, monitoring, deployment, and documentation skills. Use when the user is handling an active production incident and needs a structured process from detection through resolution and postmortem. Do NOT use for non-production issues, planned maintenance, or post-incident analysis only (use technical-documentation directly for standalone postmortems).
| name | bump-version |
| description | Use when bumping the Wayland version: update package.json, run checks, branch, commit, push, create PR, wait for merge, tag release. |
Automate the Wayland version bump workflow: update version → quality checks → branch → commit → push → PR → tag.
Usage: /bump-version [version]
/bump-version 1.8.17 - bump to specified version/bump-version - auto-increment patch (e.g. 1.8.16 → 1.8.17)git branch --show-current
git status --short
main → Stop: "Please switch to main before running bump-version."git pull --rebase origin main
Fails → Stop: "Failed to pull latest code. Please resolve conflicts or network issues first."
Read package.json → extract version field.
major.minor.patch, increment patch by 1Display: "Bumping version: {current} → {target}"
Use Edit tool to replace:
"version": "{current}""version": "{target}"bun run lint
bun run format
bunx tsc --noEmit
bunx vitest run
Fails → Stop: "Tests failed. Please fix failing tests before bumping the version."
git checkout -b chore/bump-version-{target}
git add -A
git commit -m "chore: bump version to {target}"
git push -u origin chore/bump-version-{target}
gh pr create --base main \
--title "chore: bump version to {target}" \
--body "Bump version to {target}"
Display PR URL. Then pause:
"PR created: {URL}. Please notify a team member to merge it, then confirm to continue."
Wait for user confirmation before proceeding.
git checkout main
git pull --rebase origin main
git branch -d chore/bump-version-{target}
Check if remote branch still exists:
git ls-remote --heads origin chore/bump-version-{target}
git push origin --delete chore/bump-version-{target}git tag v{target}
git push origin v{target}
Display: "Tag v{target} created and pushed. Version bump complete!"
1. Must be on clean main
2. git pull --rebase
3. Determine target version
4. Edit package.json
5. lint + format + tsc
6. vitest run
7. branch chore/bump-version-{target} → commit → push
8. gh pr create → wait for merge
9. checkout main → pull → delete branch
10. git tag v{target} && git push origin v{target}