Nm Sanctum Pr Prep

PassAudited by ClawScan on May 9, 2026.

Overview

This instruction-only skill is coherently focused on preparing pull requests, with expected local quality-check commands and PR-description drafting steps.

This skill appears safe for its intended purpose. Before installing or using it, be comfortable with the agent running your repository's normal format, lint, test, and documentation-sync commands, and review any resulting file changes and the generated PR description before submission.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

The agent may run local build/test tools and apply fixes in the repository before drafting the PR.

Why it was flagged

The skill instructs the agent to run local project commands and potentially modify files to fix failures. This is expected for PR preparation, but users should notice that project tooling can execute code or change the working tree.

Skill content
Execute formatting, linting, and tests using project-specific commands (e.g., `make fmt`, `make lint`, `make test`). Resolve all failures before proceeding.
Recommendation

Use this skill in a trusted repository, review any file changes after quality gates run, and confirm project commands before allowing broad fixes.

What this means

The agent may update generated documentation or capability reference files when plugin files change.

Why it was flagged

The workflow can invoke a fix command when plugin capability reference files are out of sync. This appears limited and purpose-aligned, but it is still a repository-mutating action.

Skill content
If it reports discrepancies, run `/sync-capabilities --fix` or update the reference manually before proceeding.
Recommendation

Review generated documentation changes before committing or opening a PR.

What this means

Task-tracking entries may remain visible as workflow history or audit context.

Why it was flagged

The skill uses TodoWrite items as workflow state. This is disclosed and low risk, but it means progress/audit context may persist during or after the workflow.

Skill content
Create → Complete → (optionally) Delete stale items after workflow success. Keep proof-of-work and audit items intact.
Recommendation

Avoid placing secrets in task names or PR-prep notes, and clean up stale workflow items when appropriate.