Menu
SkillsMP has collected 30 skills from Marshall-Hallenbeck/dot_files. Open a skill to review its source and details.
Showing 30 of 30 collected skills.
Use when asked to work on, implement, or complete a GitHub issue — before writing any code, checks issue state, existing PRs, git history, and codebase to determine what work remains or if the issue is already resolved
Use when starting, checking, or finishing work on a GitHub issue in any repo where multiple agents may work in parallel — posts a session-info claim comment and manages the in-progress label so other agents skip claimed issues
Use when asked to create, open, publish, or submit a pull request from the current branch
Use when asked to create, open, file, or draft a GitHub issue
Commit session changes only, or all changes if no session edits.
Autonomous test-fix pipeline. Runs full suite, diagnoses each failure, fixes source code, and iterates until all tests pass. Asks the user when uncertain about intended behavior.
Group ALL working-tree changes into logical commits.
Set up or repair a persistent Claude Remote Control environment for a project using a systemd user service, including blocker checks, project symlink, linger, verification, and URL capture.
Guide for using the Sentry CLI to interact with Sentry from the command line. Use when the user asks about viewing issues, events, projects, organizations, making API calls, or authenticating with Sentry via CLI.
Holistic review pipeline: simplification, correctness, security, overcautious check, lint/fix, all tests, fix failures, audits, and final review. Fixes EVERYTHING — every severity and every warning — so nothing is left open.
Run full quality gate: linting, type checks, unit tests, and integration tests — all in parallel.
Review uncommitted changes for missing test coverage, then create the missing tests. Use after implementation and before commit.
Get straight to the point in every response. Use whenever responding to ANY user message — coding, debugging, explanations, planning, casual chat. Lead with the answer or next concrete action, number multi-step work, restate state across turns, suppress…
Write comprehensive unit tests for a module or function. Handles test runner detection, mock conventions, and iterates until all tests pass.
Summarize git changes for PRs or commits. Does not commit unless explicitly asked.
Run formatting, linting, and type checking. Auto-detects project languages (Python, JS/TS, Bash). Fixes auto-fixable issues and stages changes.
Use when reviewing changes before commit to catch patterns that silence failures, fail open, add unauthorized fallbacks, or hide errors behind graceful degradation.
Security audit of uncommitted changes. Scans for OWASP top 10, injection, exposed secrets, auth bypasses, and unsafe patterns.
End-to-end Claude Code setup optimization: update CLAUDE.md with session learnings, recommend new automations, audit config quality, clean stale memory, and check for new capabilities.
Spawn an agent team in tmux split panes for parallel exploration. Best for investigation, debugging, ambiguous tasks, and multi-angle review where you want to steer work in real-time.
Review uncommitted code changes for bugs, security issues, and correctness. Finds AND fixes all issues.
Run integration-level suites. Auto-detects runner (pytest markers, Jest, E2E).
Decompose a plan into parallel work tracks and execute with subagents. Reads PLAN.md, splits into non-overlapping tracks, spawns agents, and runs integration tests.
Dispatcher skill for unit, integration, or full quality-gate workflows. Auto-detects language and scope.
Run unit-test suites. Auto-detects runner (pytest, Jest, Vitest, cargo, go test).
Run Codex and Claude code reviews iteratively until both find no issues. Use after making changes and before committing.
Look up documentation for any library using Context7. Resolves library IDs and queries versioned docs.
Normalize agents/skills/hooks so responsibilities are separated and workflows are coherent.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes