القائمة
Use when the user wants to run the linter, pre-commit checks, or markdownlint/yamllint on this project. Covers the requirement to stage/commit changes first.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when committing changes made with AI assistance. Adds the AI agent as a co-author to the git commit using the GitHub Co-authored-by trailer convention. Trigger phrases: "commit with co-author", "add AI as co-author", "commit changes".
Create a new documentation page/chapter in the OpenShift Examples site. Use when the user asks to create a new page, add a new chapter, add a new topic, or scaffold new content under content/.
| name | run-linter |
| description | Use when the user wants to run the linter, pre-commit checks, or markdownlint/yamllint on this project. Covers the requirement to stage/commit changes first. |
This project uses ./run-local-pre-commit.sh to execute markdownlint and yamllint via pre-commit.
All changes must be committed (or at least staged) before running the linter. Pre-commit hooks in this project operate on committed/staged content. Uncommitted file changes will not be picked up correctly.
Stage or commit all relevant changes:
git add .
git commit -m "wip: changes before lint check"
(Or use git add . alone if you want to keep them as staged rather than committed.)
Run the linter:
./run-local-pre-commit.sh
If lint errors are reported, fix them, stage/commit the fixes, and re-run step 2 until clean.