← スキル一覧に戻る

tests-and-formatting-discipline
by diey
Give OpenAI Codex new capabilities and expertise
⭐ 0🍴 0📅 2026年1月7日
SKILL.md
name: tests-and-formatting-discipline description: Maintain testing and formatting discipline aligned with the repository CI pipeline without automatically running tools.
Tests & Formatting Discipline
Goal
Maintain code quality and CI stability by:
- Designing changes to be testable
- Updating or adding tests when behaviour changes
- Writing code that conforms to formatting standards
- Never running tests, linters, or formatters without explicit user approval
Project Commands (Reference Only)
Use these exact command names when suggesting verification steps:
composer test— Clears cached config and executes the full Pest test suite.composer clean— Runs Laravel Pint and Prettier.composer analyse— Runs Larastan static analysis.
Do not claim these were run unless the user confirms and provides results.
Testing Expectations
- Behaviour changes must be covered by tests.
- Prefer feature tests unless logic is truly isolated.
- Use existing factories, states, and helpers.
- Follow existing test structure and naming conventions.
If behaviour changes and no test is added:
- Explicitly state why
- Offer test coverage as the next step
Formatting Expectations
- Write code that already conforms to Pint and Prettier standards.
- Avoid unrelated or drive-by formatting changes.
- Do not reformat files outside the scope of the change.
Note:
- On PRs targeting
development, the lint workflow may runcomposer cleanand auto-commit formatting fixes.
Tool Execution Policy
- Never run
composer test,composer clean,composer analyse, or any tooling automatically. - You may suggest commands, but execution is always the user’s responsibility.
End-of-Task Output
After completing an implementation, provide:
- A brief list of files changed
- A minimal list of suggested commands the user can run to validate the change
Anti-patterns
- Running tools without permission
- Claiming tests, lint, or analysis passed without evidence
- Changing behaviour without mentioning test coverage
- Introducing unrelated formatting diffs
スコア
総合スコア
45/100
リポジトリの品質指標に基づく評価
✓SKILL.md
SKILL.mdファイルが含まれている
+20
○LICENSE
ライセンスが設定されている
0/10
○説明文
100文字以上の説明がある
0/10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
○言語
プログラミング言語が設定されている
0/5
○タグ
1つ以上のタグが設定されている
0/5
レビュー
💬
レビュー機能は近日公開予定です