implementation — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited implementation (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Split all current git changes into multiple atomic commits, each scoped to one feature or concern, following conventional commits best practices.
Use get_changed_files to retrieve every staged and unstaged file with its diff. Also run git status in the terminal to get a complete picture of new/deleted/renamed files.
Read each diff and assign every file to a logical group. Apply these rules:
| Signal | Rule |
|---|---|
| Same feature folder or module | Group together |
| Only docs / README changes | Separate docs commit |
Only config / tooling files (.gitignore, package.json, CI files) | Separate chore or build commit |
| Style-only changes (whitespace, formatting) | Separate style commit |
| Test files only | Separate test commit |
| Bug fix in one module | Separate fix commit |
| New capability in one module | Separate feat commit |
| Refactor with no behavior change | Separate refactor commit |
If a file touches multiple concerns, assign it to the dominant concern. Flag ambiguous files for user confirmation before committing.
Present a numbered commit plan in this format:
Proposed commit plan
────────────────────
1. feat(cart-freeship-bar): add free shipping progress bar UI
Files: cart_freeship_bar/main-display-and-settings.html
2. feat(cart-freeship-bar): handle language change event
Files: cart_freeship_bar/event-change-lang.html
3. fix(cart): handle remove-item and clear-cart edge cases
Files: cart_freeship_bar/event-remove-item-from-cart.html
cart_freeship_bar/event-clear-cart.html
4. docs(cart-freeship-bar): update README and project overview
Files: cart_freeship_bar/README.md
cart_freeship_bar/cart_freeship_bar.md
cart_freeship_bar/project-overview.mdAsk the user to confirm, merge, reorder, or rename commits before proceeding.
For each commit in the approved plan:
git add <file1> <file2> ... git commit -m "<type>(<scope>): <subject>"git log --oneline -1).Never stage files from a different group during a commit step.
After all commits:
git status — working tree should be clean (or show only intentionally untracked files).git log --oneline -<N> (where N = number of commits made) to display the final history for the user to review.<type>(<scope>): <subject> ← max 72 chars
<blank line>
[optional body] ← wrap at 72 chars; explain *why*, not *what*
<blank line>
[optional footer] ← e.g. Closes #123, BREAKING CHANGE: ...Types:
| Type | When |
|---|---|
feat | New feature or capability |
fix | Bug fix |
docs | Documentation only |
style | Formatting, whitespace, no logic change |
refactor | Code restructure, no behavior change |
test | Adding or updating tests |
chore | Build process, tooling, dependencies |
perf | Performance improvement |
ci | CI/CD configuration |
revert | Reverts a previous commit |
Rules:
cart, email-collector)! after type/scope (feat!:) and a BREAKING CHANGE: footerMixed concern in one file? → If the diff is small and inseparable, include it in the most relevant group and note it in the commit body.
Unclear feature boundary? → Ask the user: "Should [file X] be part of commit #2 (feat: cart step) or a separate commit?"
Many small files in one folder? → Group into one commit unless they serve clearly distinct purposes.
Untracked new files? → Include them in the commit that introduces the feature they belong to.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.