git-history-analyzer
Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist. Use when you need historical context for code changes.
Explorez les skills IA publiés de udecode et consultez leurs instructions source.
Skills indexés
15Étoiles des dépôts des skills indexés
28,116Forks du dépôt
1,841Moyenne des étoiles par skill indexé
1,874Les étoiles d’un dépôt peuvent se répéter entre ses skills.
Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist. Use when you need historical context for code changes.
Use when creating or updating draft pull requests without code review - streamlines draft PR workflow with meaningful descriptions and commit messages, focusing on work-in-progress documentation
Use when implementing complex logic that needs test coverage - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first; NOT for UI comp...
Use when updating CHANGELOG.md. Enforces consistent formatting with bolded item names, dash separators, and specific section ordering.
Look up documentation and source code for libraries and packages. Use when the user asks a question about a library, needs to understand a library's API, or when you need information about a library that you do...
Use when creating or updating pull requests with comprehensive descriptions and meaningful commits - streamlines PR workflow with branch management and commit best practices
Use when reviewing pull requests with comprehensive code analysis, incremental or full review options, and constructive feedback - provides thorough code reviews with severity ratings
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source o...
Continuous learning system that extracts reusable knowledge from work sessions. Triggers: (1) /learn command to review session learnings, (2) "save this as a skill" or "extract a skill from this", (3) "what did...
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures u...
Use when writing changesets for releases
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures u...
Run browser tests on pages affected by current PR or branch
Generate comprehensive app design document with project stage assessment
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.