AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Dot Verify

skill-fmind-dot-dot-verify · by fmind

Qualify the fmind/dot working tree before a release: review changes, sync docs, run every gate, and smoke-test the dot CLI.

— No reviews yet
0 installs
1 views
0.0% view→install

Install

$ agentstack add skill-fmind-dot-dot-verify

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-fmind-dot-dot-verify)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Dot Verify? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Verify Dot

Prove that the current checkout (committed and uncommitted work) is correct, documented, and releasable. This skill sequences the owners; [repository-review](../../../skills/repository-review/SKILL.md), [repository-docs](../../../skills/repository-docs/SKILL.md), [dot-development](../dot-development/SKILL.md), and [dot-skills](../dot-skills/SKILL.md) own the details. Verification fixes findings in place but never commits, pushes, or releases; [dot-release](../dot-release/SKILL.md) owns that.

Workflow

  1. Baseline: record git status --short, staged and unstaged diffs, untracked files, and git fetch state against origin/main. Commits already on main since the last tag are part of the candidate; preserve unrelated work.
  2. Review the change set: list what changed since the last tag (git diff ) plus uncommitted work, excluding generated locks. For large sets, fan out read-only reviews by area (dot Python, chezmoi and host config, docs and skills) and verify each finding against code or real local data before fixing. Behavior fixes need regression tests per dot-development.
  3. Synchronize docs: check README.md, AGENTS.md, dot_agents/AGENTS.md, .agents/skills/, and skills/ against the code: removed or renamed files, commands and flags (uv run --frozen --directory dot dot --help), tasks (mise tasks), and JSON fields. Bump updated: on changed skills; run mise run format:skills for guide indexes; follow dot-skills for catalog changes.
  4. Run the gates: mise run all, then the host checks it omits: mise run check:completions and mise run test:starters. Check dot agent context --source . --project . --check. Rerun only what a later fix invalidates.
  5. Smoke-test the CLI from the checkout: --help for every top-level command, then read-only commands: doctor, agent doctor, agent context --check, config validate, status --stats, orphan, cache, prune all --dry-run, trust --dry-run ., and agent stats --no-sync. Every exit code must be 0 or explained.
  6. Check the workstation when tools or dotfiles changed: chezmoi diff preview, dot orphan for retired targets (report, never delete), and mise run verify. STALE for the installed dot is expected until release or mise run deploy.
  7. Report: fixed findings, deliberately left items with reasons, each check and its result, and confirm the tested snapshot equals the candidate (the working tree after the last fix).

Gotchas

  • Scanner hits in generated tool locks: universal uv locks list versions for old Python markers. Confirm the installed environment's resolved version; record a false positive as a path-scoped .trivyignore.yaml entry with a statement, never by lowering severity.
  • Removal markers: a new remove_ source must be listed in the outstanding set of test_python_only_owned_sources_and_retired_tool_cleanup until it has shipped everywhere.
  • Upstream CLI changes: an upgraded tool can drop its completion generator or tighten a pinned dependency; fix the source configuration and its skill, not the deployed copy.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

  • Author: fmind
  • Source: fmind/dot
  • License: MIT
  • Homepage: https://fmind.dev

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.