How do I install the Ignsabbag Logmancer Rust Quality Gate skill?

Run npx skillmds@latest add tomevault-io/ignsabbag-logmancer-rust-quality-gate in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Ignsabbag Logmancer Rust Quality Gate skill do?

Activation Contract It is listed under Coding & Dev Tools on SkillMD.

Is Ignsabbag Logmancer Rust Quality Gate safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ignsabbag Logmancer Rust Quality Gate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ignsabbag Logmancer Rust Quality Gate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ignsabbag Logmancer Rust Quality Gate?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ignsabbag Logmancer Rust Quality Gate by tomevault-io

Name: Ignsabbag Logmancer Rust Quality Gate
Author: tomevault-io

File contents

Activation Contract

Use this skill before creating a commit, opening a PR, or preparing changes for review in Logmancer.

Hard Rules

Run cargo fmt before any commit or PR preparation.
Run cargo clippy --workspace -- -D warnings after formatting.
Do not create the commit or PR while either command fails.
If cargo fmt changes files, include those formatting changes in the same reviewable work unit.
Do not run cargo build; this project explicitly avoids builds during agent changes unless the user asks.
Update CHANGELOG.md before committing any relevant user-facing, release, packaging, workflow, or behavior change.
Keep Conventional Commit style and never add AI attribution trailers.

Decision Gates

Situation	Action
`cargo fmt` succeeds with changes	Continue, then include changed files in commit/PR scope
`cargo fmt` fails	Stop, report the formatter error, and do not commit or open a PR
`cargo clippy --workspace -- -D warnings` fails	Fix warnings if in scope; otherwise stop and report blockers
Change affects users, releases, packaging, CI behavior, or documented behavior	Update `CHANGELOG.md` in the same work unit before committing
Change is purely internal and not notable for release notes	Leave `CHANGELOG.md` unchanged and mention why in the commit/PR summary
User asks to skip gates	Push back and require explicit confirmation before bypassing

Execution Steps

Decide whether the change is changelog-worthy before staging the commit.
If it is notable, update CHANGELOG.md under [Unreleased] or the active release section.
Run cargo fmt from the repository root.
Run cargo clippy --workspace -- -D warnings from the repository root.
Inspect the resulting working tree before committing or preparing a PR.
Proceed only when the changelog decision is explicit and both commands pass.

Output Contract

Report:

cargo fmt: pass/fail and whether files changed.
cargo clippy --workspace -- -D warnings: pass/fail.
CHANGELOG.md: updated or intentionally unchanged, with a short reason.
Any blockers that prevent commit or PR creation.

References

@AGENTS.md — Logmancer workspace commands, style, and agent rules.

Source: ignsabbag/logmancer — distributed by TomeVault.

---name: ignsabbag-logmancer-rust-quality-gatedescription: Activation Contract---## Activation ContractUse this skill before creating a commit, opening a PR, or preparing changes for review in Logmancer.## Hard Rules- Run `cargo fmt` before any commit or PR preparation.- Run `cargo clippy --workspace -- -D warnings` after formatting.- Do not create the commit or PR while either command fails.- If `cargo fmt` changes files, include those formatting changes in the same reviewable work unit.- Do not run `cargo build`; this project explicitly avoids builds during agent changes unless the user asks.- Update `CHANGELOG.md` before committing any relevant user-facing, release, packaging, workflow, or behavior change.- Keep Conventional Commit style and never add AI attribution trailers.## Decision Gates| Situation | Action ||-----------|--------|| `cargo fmt` succeeds with changes | Continue, then include changed files in commit/PR scope || `cargo fmt` fails | Stop, report the formatter error, and do not commit or open a PR || `cargo clippy --workspace -- -D warnings` fails | Fix warnings if in scope; otherwise stop and report blockers || Change affects users, releases, packaging, CI behavior, or documented behavior | Update `CHANGELOG.md` in the same work unit before committing || Change is purely internal and not notable for release notes | Leave `CHANGELOG.md` unchanged and mention why in the commit/PR summary || User asks to skip gates | Push back and require explicit confirmation before bypassing |## Execution Steps1. Decide whether the change is changelog-worthy before staging the commit.2. If it is notable, update `CHANGELOG.md` under `[Unreleased]` or the active release section.3. Run `cargo fmt` from the repository root.4. Run `cargo clippy --workspace -- -D warnings` from the repository root.5. Inspect the resulting working tree before committing or preparing a PR.6. Proceed only when the changelog decision is explicit and both commands pass.## Output ContractReport:- `cargo fmt`: pass/fail and whether files changed.- `cargo clippy --workspace -- -D warnings`: pass/fail.- `CHANGELOG.md`: updated or intentionally unchanged, with a short reason.- Any blockers that prevent commit or PR creation.## References- `@AGENTS.md` — Logmancer workspace commands, style, and agent rules.---> Source: [ignsabbag/logmancer](https://github.com/ignsabbag/logmancer) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Ignsabbag Logmancer Rust Quality Gate