菜单
Use the GitButler CLI (`but`) to create a branch, commit changes, push, and open a GitHub PR in the frontend repo. Optionally accepts a description to filter which changes to include. Use when the user asks to push changes, create a PR, or commit using GitButler.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Enable or disable maintenance mode for the frontend. Use when the user asks to put the site in maintenance mode, take it down for maintenance, or bring it back up after maintenance.
Run the frontend linter, analyze failures, and fix them iteratively. Use when linting fails, lint errors appear, or the user asks to fix lint issues in the frontend repo.
Add dark mode styles to components using Tailwind dark: variant classes. Use when creating new components, adding dark mode support to existing components, or when the user mentions dark mode, theming, or light/dark variants.
| name | create-frontend-pr |
| description | Use the GitButler CLI (`but`) to create a branch, commit changes, push, and open a GitHub PR in the frontend repo. Optionally accepts a description to filter which changes to include. Use when the user asks to push changes, create a PR, or commit using GitButler. |
/create-frontend-pr — include all unstaged changes/create-frontend-pr <description> — only include changes related to the description (e.g. /create-frontend-pr dark mode fix)GitButler must be set up in the repo (but setup). Run but status to verify.
Check workspace state: Run but status to see unstaged changes and existing branches.
Filter changes (if a description was provided): Review the unstaged files and their diffs. Only include files that are related to the description. Read file contents or diffs if needed to determine relevance.
Create a branch: but branch new <branch-name>
Stage files: but stage <file> <branch-name> for each relevant file. Run but status after to confirm.
Commit: but commit -m "<message>" --only <branch-name>
Push: but push
Create PR: Use -m to pass title and body non-interactively:
but pr new <branch-name> -m "<title>
<body>"
The first line of -m is the PR title, the rest is the body.
but pr requires forge auth. If it fails, check but config forge.but status between steps to verify state.