From 1e35e3c68a46ba8fecac4ce6a27b51f8c6a1d4f9 Mon Sep 17 00:00:00 2001
From: Iko <6572003+iap@users.noreply.github.com>
Date: Thu, 3 Sep 2026 18:34:51 +0700
Subject: [PATCH 1/2] feat(ci): add actionlint workflow validation job

---
 .github/workflows/ci.yml | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 219b31e..0f02c0d 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -28,3 +28,19 @@ jobs:
       - name: Run tests
         run: npm test
         if: hashFiles('package.json') != ''
+
+  lint-workflows:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
+
+      - name: Download and verify actionlint
+        run: |
+          curl -fsSL -o actionlint.tar.gz \
+            https://github.com/rhysd/actionlint/releases/download/v1.7.12/actionlint_1.7.12_linux_amd64.tar.gz
+          echo "8aca8db96f1b94770f1b0d72b6dddcb1ebb8123cb3712530b08cc387b349a3d8  actionlint.tar.gz" | sha256sum -c -
+          tar -xzf actionlint.tar.gz actionlint
+
+      - name: Lint GitHub Actions workflows
+        run: ./actionlint

From 0fa44dd1b145134d13030e3bffff8ced5256eb9c Mon Sep 17 00:00:00 2001
From: Iko <6572003+iap@users.noreply.github.com>
Date: Thu, 3 Sep 2026 18:49:57 +0700
Subject: [PATCH 2/2] docs(agents): forbid self-claiming and unverified detail
 embedding

---
 AGENTS.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/AGENTS.md b/AGENTS.md
index a5f914a..ca4f32d 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -11,6 +11,7 @@ This is a general-purpose GitHub repository template. It contains community heal
 - Keep changes minimal and aligned with the repo's existing style.
 - Do not commit secrets or environment files (`.env`); use `.env.example` instead.
 - Run available linters/formatters/tests before declaring work complete; if none exist, say so.
+- Avoid self-claiming and embedding unverified detail. Never claim you verified something you did not, and do not over-specify routine conventions in comments (e.g. tagging a commit as "GPG-signed" when the repo requires signing by default). State only what you did and observed.
 - Prefer small, focused commits; write subjects as `type(scope): summary` (see `CONTRIBUTING.md`).
 - Use branch naming prefixes: `feat/`, `fix/`, `docs/`, `chore/`, `refactor/`, `test/` (see `CONTRIBUTING.md`).
 - Open PRs early and keep them small — a series of small, merged PRs is easier to review than one large one.