Install
$ agentstack add skill-d-o-hub-rust-self-learning-memory-commit ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
About
Git Commit with Quality Gates
Enforce code quality before every commit.
Workflow (MANDATORY ORDER)
- Quality Gates (BLOCKING - must pass)
``bash ./scripts/quality-gates.sh ``
- Validates >90% test coverage
- Runs all tests with strict warnings
- Checks security vulnerabilities
- Verifies code quality standards
- Checks for
.pyor.shfiles in repository root (forbidden)
If quality gates FAIL: STOP. Fix issues before proceeding.
- Check Status
``bash git status git diff --stat ``
- Stage Changes
``bash git add -p # Interactive staging for atomic commits # OR git add ``
- Create Commit (use message format below)
``bash git commit ``
- Sync with Remote
``bash git pull --rebase ``
- Handle Conflicts (if any)
- STOP - DO NOT AUTO-FIX
- Notify user for manual resolution
- Only proceed after user confirms resolution
- Push
``bash git push ``
Commit Message Format
type(scope): Brief description (50 chars max)
- Why this change was necessary from user perspective
- What problem it solves or capability it enables
- Reference issue/ticket numbers if applicable
Commit Types
| Type | Purpose | |------|---------| | feat | New user-facing feature | | fix | Bug fix resolving user issue | | docs | Documentation changes | | refactor | Code restructure (no user-facing changes) | | perf | Performance improvement | | test | Test additions/changes | | chore | Build/dependency updates |
Message Rules
- Subject: 50 chars max, capitalized, no period
- Body: Wrap at 72 chars
- Use imperative mood: "Add feature" not "Added feature"
- Explain WHY from user perspective, not WHAT code changed
Examples
Good:
feat(search): Add filters to help users find documents faster
Users were spending too much time scrolling through results.
New filters reduce search time by 60% in user testing.
Fixes #123
Bad:
improved stuff
Atomic Commit Principle
- Each commit = ONE logical change
- Commit must compile and pass tests
- Use
git add -pfor partial staging
Optional Pre-Push Checks
For larger changes:
./scripts/check-doctests.sh
./scripts/check_performance_regression.sh
References
- [AGENTS.md - Required Checks Before Commit](../../../AGENTS.md)
- [commit command](../../../.opencode/commands/commit.md)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: d-o-hub
- Source: d-o-hub/rust-self-learning-memory
- License: MIT
- Homepage: https://d-o-hub.github.io/rust-self-learning-memory/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.