docs(agent): 에이전트 문서 규칙을 정리한다

.opencode/commands/commit.md

@@ -1,22 +0,0 @@
----
-description: commit-policy 스킬을 로드해 커밋 메시지 생성과 전후 검증을 수행한다
-agent: build
-subtask: true
----
-
-작업 목표:
-현재 변경사항을 안전하게 커밋한다.
-
-필수 시작 단계:
-1. `skill` 도구로 `commit-policy` 스킬을 먼저 로드한다.
-   - `skill({ name: "commit-policy" })`
-
-실행 단계:
-1. 로드한 `commit-policy` 스킬의 Hard Requirements와 Execution Flow를 그대로 수행한다.
-2. `AGENTS.md`의 최소 정책(형식/한글 description/검증 스크립트)을 항상 만족한다.
-3. `$ARGUMENTS`가 있으면 scope 또는 description 의도에 반영하되, 스킬 규칙과 형식을 깨지 않는다.
-4. 가능하면 메시지 파일을 검증한 뒤 같은 파일을 `git commit -F`에 전달해 검증을 통과한 메시지를 그대로 사용하고, `Ultraworked with [Sisyphus]...` 및 `Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>` 라인이 본문에 추가되지 않도록 확인한다.
-5. 마지막에 실행 명령과 pre-check/post-check PASS/FAIL 핵심 결과를 간단히 보고한다.
-
-추가 사용자 의도:
-$ARGUMENTS

.opencode/skills/commit-policy/SKILL.md

@@ -1,49 +0,0 @@
----
-name: commit-policy
-description: Apply this skill for any git commit task in this repository. It enforces commit message format and validation flow defined in AGENTS.md and work/scripts/check-commit-message-rules.sh, including pre-commit and post-commit verification.
----
-
-# Commit Policy Skill
-
-Use this workflow whenever the task includes creating a commit.
-
-## Required References
-
-- `@AGENTS.md`
-- `@work/scripts/check-commit-message-rules.sh`
-
-## Hard Requirements
-
-1. Use commit subject format: `<type>(scope): <description>`.
-2. `type` must be lowercase (for example `feat`, `fix`, `chore`, `docs`, `refactor`, `test`).
-3. `description` must include Korean text and stay concise in imperative present tone.
-4. Optional footer must use `Refs: #123` or `Refs: #123, #456` format.
-5. Never commit secret files (`.env`, key/token/secret credential files).
-6. Never bypass hooks with `--no-verify`.
-7. Never include `Ultraworked with [Sisyphus]...` or `Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>` in the commit body.
-
-## Execution Flow
-
-1. Inspect context with:
-   - `git status`
-   - `git diff --cached`
-   - `git diff`
-   - `git log -5 --oneline`
-2. Stage commit target files only. Exclude suspicious secret-bearing files.
-3. Draft commit message from the change intent (focus on why, not only what).
-4. Run pre-commit validation with the full draft message:
-    - `./work/scripts/check-commit-message-rules.sh --message "<full message>"`
-5. If validation fails, revise message and re-run until PASS.
-6. Prefer validating a message file with `./work/scripts/check-commit-message-rules.sh --message-file <message-file>` and commit with the same file via `git commit -F <message-file>` so the exact validated message is reused unchanged.
-7. Run post-commit validation:
-    - `./work/scripts/check-commit-message-rules.sh`
-8. If post-commit validation fails because an automatic footer was appended, stop and report the failure instead of treating the commit as valid.
-9. Report executed commands and PASS/FAIL summary.
-
-## Output Checklist
-
-- Final commit subject.
-- Whether pre-check passed.
-- Whether post-check passed.
-- Any excluded files and reason.
-- Whether forbidden Sisyphus footer lines were absent in the final commit body.