All authors

Claude Skills by athola
github.com/athola225 skills6 installs783 views
- Python AsyncMaster Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications.Votes: 0GitHub stars: 342
- Python PackagingPython package creation and PyPI distribution via pyproject.toml and entry points. Use when publishing a package or setting up build configuration.Votes: 0GitHub stars: 342
- Python PerformanceProfiles Python code for performance bottlenecks and memory issues. Use when Python code is slow or when profiling for optimization before a release.Votes: 0GitHub stars: 342
- Python TestingPython testing patterns with pytest, fixtures, TDD, mocking, async and integration tests. Use when writing or auditing a Python test suite.Votes: 0GitHub stars: 342
- Api ReviewEvaluates API surface design, consistency, and exemplar alignment. Use when reviewing public API changes or before releasing a new API surface.Votes: 0GitHub stars: 342
- Architecture ReviewAssesses architecture decisions, ADR compliance, and coupling. Use when evaluating design changes or validating structural decisions before merging.Votes: 0GitHub stars: 342
- Bug ReviewHunts bugs with evidence trails. Use when investigating unexpected behavior or before merging code with potential hidden defects.Votes: 0GitHub stars: 342
- Makefile ReviewAudits Makefiles for build correctness, portability, and recipe duplication. Use when reviewing a Makefile or before committing Makefile changes.Votes: 0GitHub stars: 342
- Math ReviewVerifies math-heavy code for algorithmic correctness and numerical stability. Use when reviewing scientific algorithms, ML models, or numerical code.Votes: 0GitHub stars: 342
- Rust ReviewAudits Rust code for unsafe blocks, ownership issues, and Cargo dependency risks. Use when reviewing Rust code or before merging Rust changes.Votes: 0GitHub stars: 342
- Test ReviewEvaluates test suites for coverage gaps, TDD/BDD compliance, and anti-patterns. Use when auditing test quality or before a major release.Votes: 0GitHub stars: 342
- Unified ReviewOrchestrates multi-domain review (code, arch, tests, security) in a single pass. Use when thorough pre-release review is needed.Votes: 0GitHub stars: 342
- Commit MessagesGenerates conventional commit messages from staged changes. Use when committing and needing a well-formatted message. Do not use for full PR prep; use pr-prep.Votes: 0GitHub stars: 342
- Doc ConsolidationMerges ephemeral report and analysis artifacts into permanent documentation. Use when LLM-generated markdown files have accumulated and need consolidation.Votes: 0GitHub stars: 342
- Doc UpdatesUpdates documentation after code changes with quality gates, slop detection, and accuracy checks. Use when code changes require corresponding doc updates.Votes: 0GitHub stars: 342
- Git Workspace ReviewVerifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct.Votes: 0GitHub stars: 342
- Pr PrepPrepares pull requests by running quality gates, drafting descriptions, and validating tests. Use when completing a feature and ready for review.Votes: 0GitHub stars: 342
- Pr ReviewReviews pull requests with scope validation, requirements compliance, and line comments. Use when reviewing GitHub or GitLab PRs.Votes: 0GitHub stars: 342
- Test UpdatesUpdates, generates, and validates tests using git-workspace context and TDD/BDD methodology. Use when code changes require new or updated test coverage.Votes: 0GitHub stars: 342
- Update ReadmeRefreshes README structure favoring concision (an index, not a manual). Use when the README needs a structural update after significant project changes.Votes: 0GitHub stars: 342
- Version UpdatesBump project versions across configs, docs, and changelog using git-workspace-review context.Votes: 0GitHub stars: 342
- Workflow ImprovementRetrospective workflow to evaluate the most recent command/session slice in the current context window and drive improvements to the skills, agents, commands, and hooks involved.Votes: 0GitHub stars: 342
- Spec WritingCreate clear, testable specifications from natural language descriptions. Focus on what users need and why, not implementation details.Votes: 0GitHub stars: 342
- Speckit OrchestratorOrchestrates Spec Driven Development by coordinating spec, plan, and task skills. Use when running the full speckit workflow from spec to implementation.Votes: 0GitHub stars: 342
- Task PlanningGenerate dependency-ordered implementation tasks from specifications and plans. Create actionable, phased task breakdowns.Votes: 0GitHub stars: 342
- Methodology CuratorSurface expert frameworks. Use when creating or evaluating skills, hooks, or agents.Votes: 0GitHub stars: 342
- Subagent TestingTest skills via TDD in fresh subagents. Use when validating behavior or preventing bias.Votes: 0GitHub stars: 342
- Architecture Aware InitSelects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.Votes: 0GitHub stars: 342
- Makefile GenerationGenerates Makefiles with testing, linting, formatting, and automation targets. Use when starting a project or standardizing build automation.Votes: 0GitHub stars: 342
- Precommit SetupConfigure three-layer pre-commit quality system with linting, type checking, and testing hooks. Use when: setting up quality gates, configuring pre-commit, establishing code quality standards. Do not use when: pre-commit already configured optimally.Votes: 0GitHub stars: 342
- Project BrainstormingGuides project ideation via Socratic questioning to produce a validated brief. Use before specification when requirements are unclear.Votes: 0GitHub stars: 342
- Project ExecutionExecute implementation plans systematically with checkpoint validation, progress tracking, and continuous quality gates. Use when: implementing tasks, executing plans, tracking progress, validating checkpoints. Do not use when: no implementation plan exists or still in planning phase.Votes: 0GitHub stars: 342
- Project InitScaffolds new projects with git, CI/CD workflows, pre-commit hooks, and build config. Use when starting a new Python, Rust, or TypeScript project from scratch.Votes: 0GitHub stars: 342
- Project PlanningTransform specifications into structured implementation plans with architecture design and dependency-ordered task breakdown. Use when: converting specs to plans, designing architecture, breaking down tasks, estimating effort. Do not use when: no specification exists yet or still brainstorming approaches.Votes: 0GitHub stars: 342
- Project SpecificationTransforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.Votes: 0GitHub stars: 342
- War Room CheckpointAssesses decision reversibility and risk at critical checkpoints. Use when a workflow reaches a high-stakes branch needing escalation check.Votes: 0GitHub stars: 342
- War RoomConvenes a multi-LLM expert panel to pressure-test hard-to-reverse decisions. Use when reversibility score is low and adversarial review is warranted.Votes: 0GitHub stars: 342
- Workflow SetupConfigures GitHub Actions CI/CD workflows for testing, linting, and deployment. Use when setting up automation for a Python, Rust, or TypeScript project.Votes: 0GitHub stars: 342
- Bloat Detector'Detect codebase bloat through progressive analysis: dead code, duplication,Votes: 0GitHub stars: 342
- Clear ContextManages context overflow by handing off to a fresh subagent at 80% usage. Use when context pressure is critical and work must continue uninterrupted.Votes: 0GitHub stars: 342
- Code Quality PrinciplesApplies KISS, YAGNI, and SOLID principles for clean code with reduced complexity. Use when refactoring or reviewing code for over-engineering.Votes: 0GitHub stars: 342
- Decisive ActionGuides when to ask clarifying questions versus proceed autonomously. Use to reduce unnecessary clarifying questions when intent is clear.Votes: 0GitHub stars: 342
- Response CompressionCompresses verbose responses by removing filler and framing to save 200-400 tokens. Use when responses feel bloated or context is filling fast.Votes: 0GitHub stars: 342
- Rule CatalogBrowse hookify rule catalog. Use when installing pre-built rules or browsing categories. Do not use when writing custom rules; use hookify:writing-rules.Votes: 0GitHub stars: 342
- Writing RulesCreates behavioral rules in markdown to block dangerous commands or restrict AI behavior. Use when adding safety guardrails or preventing specific commands.Votes: 0GitHub stars: 342
- Feature ReviewScores backlog items with RICE/WSJF/Kano and files GitHub issues for top candidates. Use when triaging a roadmap or prioritizing features for a sprint.Votes: 0GitHub stars: 342
- Proof Of WorkEnforces validation and evidence before claiming work complete. Use before declaring implementation done, creating a PR, or submitting deliverables for review.Votes: 0GitHub stars: 342
- Rigorous ReasoningApplies anti-sycophancy checklist to override agreement bias. Use when analyzing contested claims or avoiding socially convenient but inaccurate conclusions.Votes: 0GitHub stars: 342
- Workflow MonitorDetects workflow failures and inefficient patterns then files GitHub issues. Use when a workflow step repeatedly fails or produces inconsistent output.Votes: 0GitHub stars: 342
- Review ChamberCaptures and retrieves PR-review findings in memory palaces. Use after PR review to store architectural decisions, patterns, and standards for future reference.Votes: 0GitHub stars: 342