agentleFS
Sign inStart free
AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/checkin-assistant/SKILL.md

checkin

Skill4 starsChanged 29 days agoMITView on GitHub

[UDS] Reference for pre-commit quality gates: gate definitions, checklist items, and never-commit rules. Use when: deciding what must pass before a commit, auditing which quality gates a project enforces, checking readiness to check in. Not for: executing the gate sequence or aborting a commit — that moved to the adoption layer (XSPEC-095); finding and removing debug artifacts — use /sweep. Keywords: check-in, pre-commit, quality gate, commit readiness, never commit, 簽入, 提交前檢查, 品質關卡.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify pre-commit quality gates before committing code to ensure codebase stability.

    line 31
  2. Distinctive:

    Check git status: - Run git status and git diff to understand pending changes

    line 40
  3. Distinctive:

    Verify quality gates: - Check each gate against the checklist below

    line 43
  4. Very specific:

    After verification, proceed with /commit to create the commit message

    line 71
  5. Very specific:

    After /checkin completes, the AI assistant should suggest:

    line 75

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- DEPRECATION NOTICE (XSPEC-086 Phase 4, 2026-04-28): Checkin workflow orchestration (gate execution sequence, abort logic) relocated to adoption layer (XSPEC-095, 2026-04-28). This Skill retains: quality gate definitions, checklist items, never-commit rules. For enforced execution, use your adoption layer's toolchain. -->

Check-in Assistant | 簽入助手

⚠️ Status: Reference（參考用，非可執行流程） — 簽入流程協調（關卡執行序列、abort 邏輯）已於 2026-04-28 移至 adoption layer（XSPEC-095）。此處保留品質關卡定義、檢查清單項、never-commit 規則供參考。 Lifecycle orchestration has moved to the adoption layer (XSPEC-095); this document is reference-only. For enforced execution, use your adoption layer's toolchain.

Verify pre-commit quality gates before committing code to ensure codebase stability.

在提交程式碼前驗證品質關卡，確保程式碼庫的穩定性。

Workflow | 工作流程

📖 以下為流程的參考結構，非可執行步驟；自動化／強制執行請用 adoption layer 工具鏈（XSPEC-095）。 The steps below are a reference structure, not an executable workflow.

  1. Check git status - Run git status and git diff to understand pending changes
  2. Run tests - Execute npm test (or project test command) to verify all tests pass
  3. Run linting - Execute npm run lint to check code style compliance
  4. Verify quality gates - Check each gate against the checklist below
  5. Report results - Present pass/fail summary and recommend next steps

Quality Gates | 品質關卡

GateCheck檢查項目
BuildCode compiles with zero errors編譯零錯誤
TestsAll existing tests pass (100%)所有測試通過
CoverageTest coverage not decreased覆蓋率未下降
Code QualityFollows coding standards, no code smells符合編碼規範
SecurityNo hardcoded secrets or vulnerabilities無硬編碼密鑰
DocumentationAPI docs and CHANGELOG updated if needed文件已更新
WorkflowBranch naming and commit message correct分支和提交格式正確
UpstreamNo .standards/ or .claude/skills/ modifications (advisory)無 UDS 上游檔案修改（建議性）

Never Commit When | 禁止提交的情況

  • Build has errors | 建置有錯誤
  • Tests are failing | 測試失敗
  • Feature is incomplete and would break functionality | 功能不完整會破壞現有功能
  • Contains WIP/TODO in critical logic | 關鍵邏輯中有 WIP/TODO
  • Contains debugging code (console.log, print) | 包含除錯程式碼
  • Contains commented-out code blocks | 包含被註解的程式碼區塊

Usage | 使用方式

  • /checkin - Run full quality gate verification on current changes
  • After verification, proceed with /commit to create the commit message

Next Steps Guidance | 下一步引導

After /checkin completes, the AI assistant should suggest:

品質關卡驗證完成。建議下一步 / Quality gate verification complete. Suggested next steps:

  • 全部通過 ✅ → 執行 /commit 提交變更 ⭐ Recommended / 推薦 — All passed → Run /commit to commit
  • 有失敗項目 ❌ → 修復問題後重新執行 /checkin — Failures found → Fix then re-run /checkin
  • 需要程式碼審查 → 執行 /code-review 進行自我審查 — Need review → Run /code-review for self-review
  • UDS 安裝有異常 → 執行 /audit 診斷問題 — UDS issues detected → Run /audit to diagnose

Reference | 參考

  • Detailed guide: guide.md
  • Core standard: checkin-standards.md

AI Agent Behavior | AI 代理行為

完整的 AI 行為定義請參閱對應的命令文件：/checkin

For complete AI agent behavior definition, see the corresponding command file: /checkin

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free