Montimage/skills

Montimage/skills

Skill Claude Code

Inspect a git branch against main, summarize its commits, diff, merge status, and staleness, then emit a cleanup action plan. Use when reviewing or cleaning up one branch. Don't use for repo audits, multi-branch sweeps, or PR code review.

Montimage/skills

Skill Claude Code

Configure pre-commit hooks and GitHub Actions for project quality gates. Use when setting up CI/CD automation. Don't use for application features, release management, or documentation.

Montimage/skills

Skill Claude Code

Generate project documentation structure and practical guides. Use when organizing READMEs or adding API docs. Don't use for code changes, CI setup, or branch management.

Montimage/skills

Skill Claude Code

Generate cross-platform install scripts with environment detection, verification, rollback, and docs. Use when automating installs across Windows, Linux, or macOS. Don't use for feature code, CI setup, or docs-only requests.

Montimage/skills

Skill Claude Code

Prepare an end-to-end OSS release flow covering audit, branches, docs, README, publications, and optional Pages. Use when coordinating full OSS prep. Don't use for audit-only checks, single-doc edits, or marketing sites.

Montimage/skills

Skill Claude Code

Prepare a repository for open-source release with standard files, GitHub templates, and an eight-section readiness audit. Use when making a project public. Don't use for marketing pages, closed code, or docs-only edits.

Montimage/skills

Skill Claude Code

Audit a skill directory for security risks and provide an install verdict. Use when reviewing third-party skills before installation. Don't use for application code review, runtime vulnerability scans, or generic dependency audits.

Montimage/skills

Skill Claude Code

Audit npm, Python, Docker, and GitHub Actions supply-chain controls. Use when hardening dependency workflows. Don't use for runtime vulnerabilities, secret scanning, or generic dependency updates.

Montimage/skills

Skill Claude Code

Improve test coverage by finding untested branches, error paths, and edge cases. Use when measuring or strengthening a project's tests. Don't use for production debugging, code review, or feature implementation.