tizen-sdk-skills-review
Skill19 starsChanged 22 days agoApache-2.0View on GitHub
Codex entrypoint for reviewing a pull request that touches tizen-sdk-skills/. Use when asked to review a pull request in this repository, for example "review PR 49" or "PR 49 리뷰해줘". The procedure itself lives in .claude/skills/tizen-sdk-skills-review/SKILL.md.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- tizen-sdk-skills-reviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
stop if the pull request does not touch tizen-sdk-skills/.
- Distinctive: line 18
stop if git status --porcelain is not empty.
- Distinctive: line 19
run only safe-tier checks.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Reviewing tizen-sdk-skills pull requests with Codex
This file is the Codex entrypoint only. The review procedure is kept in one place so that the host entrypoints cannot drift apart.
Read and follow
.claude/skills/tizen-sdk-skills-review/SKILL.md
from start to finish. Every rule there applies unchanged, including:
- comment only — never approve, request changes, merge, push or edit the pull request branch;
- stop if the pull request does not touch
tizen-sdk-skills/; - stop if
git status --porcelainis not empty; - run only safe-tier checks;
- end the comment with the model line
_Reviewed with <model name> (`<model id>`) in Codex._, writingunknownfor anything the agent was not told; - show the draft comment and post it only after the reviewer confirms.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

