All authors
Claude Skills by farhanic017
github.com/farhanic01716 skills0 installs13 views
- Self ExtendUse when you want to evolve your own capabilities — create new tools to avoid repeating patterns, add hooks to improve your own behavior, build skills to accumulate domain knowledge, or override built-in tools to adapt to project needs. This is your self-iteration interface.Votes: 0GitHub stars: 6
- AskUse whenever you need a decision, clarification, or approval from the user — covers how to ask with the question tool, and how to resolve the decision yourself when no user is available (question tool absent, or a [Never-Ask] response)Votes: 0GitHub stars: 6
- BrainstormYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.Votes: 0GitHub stars: 6
- DebugUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesVotes: 0GitHub stars: 6
- ExecuteUse when you have a written implementation plan to execute in a separate session with review checkpointsVotes: 0GitHub stars: 6
- FeedbackUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationVotes: 0GitHub stars: 6
- MergeUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanupVotes: 0GitHub stars: 6
- New SkillUse when creating new skills or editing existing skills for the project or personal skill libraryVotes: 0GitHub stars: 6
- ParallelUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesVotes: 0GitHub stars: 6
- PlanUse when you have a spec or requirements for a multi-step task, before touching codeVotes: 0GitHub stars: 6
- ReportUse after implementation is verified and before merge — consolidates multiple spec iterations into a single final-state report, marks related specs, and records key lessonsVotes: 0GitHub stars: 6
- ReviewUse when completing tasks, implementing major features, or before merging to verify work meets requirementsVotes: 0GitHub stars: 6
- SubagentUse when executing implementation plans with independent tasks in the current sessionVotes: 0GitHub stars: 6
- TddUse when implementing any feature or bugfix, before writing implementation codeVotes: 0GitHub stars: 6
- VerifyUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysVotes: 0GitHub stars: 6
- WorktreeUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackVotes: 0GitHub stars: 6