القائمة
Enforces conventional commit messages and good git hygiene. Use this skill automatically whenever creating commits, preparing PRs, or performing any git operations in this repository.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Guides use of the debug_state tool and runtime introspection to diagnose agent issues between turns. Load this skill when something goes wrong during a session and you need to inspect agent state, token usage, event history, or tool availability.
Detects and removes cyclic compile-time dependencies in Elixir codebases using mix xref, with minimal code changes. Use when the user explicitly asks to check for cycles, remove cyclic dependencies, or fix xref cycle failures. Requires Elixir 1.19 or higher for accurate results.
Automatically adds user-provided links and citations to docs/research/references.md. Use this skill whenever the user shares a URL, paper, blog post, or external reference that should be recorded.
Runs the full CI check suite locally before pushing. Use this skill before pushing a branch or when the user asks to verify everything passes, to catch issues before they hit CI.
Verifies TypeScript codegen is in sync with Elixir protocol definitions. Use this skill after modifying Elixir structs, protocol messages, or RPC types in lib/opal/ to regenerate and verify the TypeScript client SDK types.
Maintains evergreen documentation in docs/. Use this skill when a major feature is added, changed, or removed to keep the corresponding explainer up to date. Also use when the user asks to document something or references this skill.
| name | git |
| description | Enforces conventional commit messages and good git hygiene. Use this skill automatically whenever creating commits, preparing PRs, or performing any git operations in this repository. |
| globs | **/* |
You enforce Conventional Commits on every commit in this repository. This is critical for consistent changelogs and semantic version bumps.
Every commit message MUST follow this format:
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
| Type | When to use | Version bump |
|---|---|---|
feat | A new feature or capability | minor |
fix | A bug fix | patch |
docs | Documentation only | none |
style | Formatting, semicolons, whitespace — no logic | none |
refactor | Code change that neither fixes a bug nor adds a feature | none |
perf | Performance improvement | patch |
test | Adding or correcting tests | none |
build | Build system or external dependency changes | none |
ci | CI configuration changes | none |
chore | Maintenance tasks (deps, tooling, releases) | none |
Use a scope to identify the affected area:
| Scope | Meaning |
|---|---|
core | Elixir core (lib/opal/ directory) |
cli | TypeScript CLI (cli/ directory) |
rpc | JSON-RPC protocol layer |
agent | Agent loop / GenServer |
tools | Built-in tool implementations |
ci | GitHub Actions workflows |
release | Release and versioning infrastructure |
docs | Documentation |
sdk | TypeScript SDK client |
Omit the scope only when the change truly spans the entire project.
Append ! after the type/scope for breaking changes:
feat(rpc)!: change message envelope format
Or add a BREAKING CHANGE: footer in the body.
feat(cli): add --json flag for machine-readable output
fix(core): prevent crash when tool returns empty response
docs(tools): document edit tool hashline format
refactor(agent): extract token counting into dedicated module
ci: add Elixir dialyzer step to CI pipeline
chore(release): 0.1.10
feat(rpc)!: switch from JSON-RPC 2.0 to msgpack framing
BREAKING CHANGE: RPC wire format changed from JSON to msgpack.
Clients must update to sdk >= 0.2.0.