Borrowing it
Nothing to install: this file belongs to circuit-synth/kicad-sch-api. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/circuit-synth/kicad-sch-api/main/.claude/commands/dev/update-and-commit.mdgit clone --depth 1 https://github.com/circuit-synth/kicad-sch-apiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/circuit-synth/kicad-sch-api/update-and-commit)<a href="https://agentmods.dev/commands/circuit-synth/kicad-sch-api/update-and-commit"><img src="https://agentmods.dev/badge/commands/circuit-synth/kicad-sch-api/update-and-commit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/circuit-synth/kicad-sch-api/update-and-commit"><img src="https://agentmods.dev/badge/commands/circuit-synth/kicad-sch-api/update-and-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01486 |
| Opus 5.5 | $0.00000 | $0.00594 |
| Sonnet 5.5 | $0.00000 | $0.00297 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
update-and-commit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- update-and-commit — 89% identical, 30 lines differ
- update-and-commit — 89% identical, 30 lines differ
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update and Commit Command - kicad-sch-api
Usage
/update-and-commit "Brief description of changes"
Description
Comprehensive workflow for documenting progress, updating documentation, and committing changes to kicad-sch-api with professional quality standards.
Process
1. Update Documentation (REQUIRED for Features)
IMPORTANT: Always update documentation BEFORE committing new features
- IF new user-facing features: Update README.md with examples
- IF new API methods: Add to Advanced Features section in README.md
- IF version increment needed: Update CHANGELOG.md with new version entry
- IF new MCP tools: Update tool documentation
- ALWAYS document new public methods with code examples
- NO documentation changes needed for internal fixes or refactoring
# Documentation update checklist for new features:
# 1. Add examples to README.md "Basic Usage" or "Advanced Features" sections
# 2. Create CHANGELOG.md entry with version bump (patch/minor/major)
# 3. Update any relevant example files in examples/
# 4. Ensure CLAUDE.md reflects new functionality if developer-relevant
2. Format Code Before Committing
IMPORTANT: Always format code before committing
# Format Python code
uv run black kicad_sch_api/ tests/ --quiet
uv run isort kicad_sch_api/ tests/ --quiet
# Format TypeScript (MCP server)
cd mcp-server && npm run format --silent 2>/dev/null || echo "TypeScript formatting skipped"
cd ..
# Format configuration files
prettier --write "*.{json,yml,yaml}" --ignore-path .gitignore 2>/dev/null || echo "Config formatting skipped"
3. Quality Checks Before Committing
IMPORTANT: Run basic quality checks
# Syntax validation
find kicad_sch_api/ tests/ -name "*.py" -exec python -m py_compile {} \; 2>/dev/null || echo "⚠️ Syntax errors found"
# Quick test run
uv run pytest tests/test_component_management.py tests/test_sexpr_parsing.py -q || echo "⚠️ Core tests failing"
# Import validation
uv run python -c "import kicad_sch_api; print('✅ Import successful')" || echo "⚠️ Import failed"
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 201 lines · 0 tokens per session scan A b54fa55841b8
update-and-commit is a command published in the GitHub repository circuit-synth/kicad-sch-api (57 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,486 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
standup
Review my git commits from the past workday and generate a standup summary.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
commit
Context-aware Git commit assistant with smart pre-commit checks.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.