一键导入
check-formatting
Verify and fix code formatting with dotnet format. Run before opening any PR, and whenever formatting errors are reported by CI or the Stop hook.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Verify and fix code formatting with dotnet format. Run before opening any PR, and whenever formatting errors are reported by CI or the Stop hook.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | check-formatting |
| description | Verify and fix code formatting with dotnet format. Run before opening any PR, and whenever formatting errors are reported by CI or the Stop hook. |
| allowed-tools | ["Bash(git rev-parse *)","Bash(dotnet format)","Bash(dotnet format *)"] |
A Stop hook (.claude/hooks/scripts/check-format.sh) enforces formatting at the end of every turn — this skill is the fix-it procedure.
From the repo root (git rev-parse --show-toplevel), run:
dotnet format ZeeKayDa.Auth.slnx --verify-no-changes
The explicit ZeeKayDa.Auth.slnx path is required: the repo also carries per-OS solution
filters (ZeeKayDa.Auth.{Windows,MacOS,Linux}.slnf) that dotnet format's auto-discovery
treats as candidate solution files, so a bare dotnet format errors with "Multiple MSBuild
solution files found" instead of running.
If it exits non-zero, run dotnet format ZeeKayDa.Auth.slnx to fix the issues, then re-run the verify step.
Repeat until --verify-no-changes exits 0.
Compare test coverage on the current branch against main and fail if it regressed. Run before opening any PR — CI enforces a coverage regression gate, and this catches it locally first.
LSP-first code navigation for ZeeKayDa.Auth — load the LSP tool up front and use it for all symbol-level lookups. Applies to every agent that reads or writes C# in this repository.
Housekeeping after a PR merges — delete the local branch, pull main, remove resolved blockers from draft PRs and issues, and check whether the parent epic can close. Run whenever a PR has been merged.
Write a well-structured GitHub issue for ZeeKayDa.Auth — decides between an ADR issue and an implementation issue, applies the issue templates, hierarchy, and labels, and links sub-issues to their epic. Use when fleshing out a new idea, filing a bug, creating design or implementation issues, or triaging incoming issues.
Set up a git worktree for reviewing or auditing a branch or PR so the review runs against the right code. Use before any code review, audit, or acceptance-criteria verification that targets a branch other than the currently checked-out one.
Security review checklist for ZeeKayDa.Auth. Apply to every change touching tokens, cryptography, endpoints, or storage — during security review, and as a developer self-check before opening a PR that touches those areas.