skills.rest
TomasGC
TomasGCCOMMUNITY
Explore all skills by this author →
GitHub

analyze-feature

Analyzes features across GitHub issues, KANBAN entries, wiki pages, and git commits.

Updated May 11, 2026
Search Tags:#architecture#multi-repository#github#report generation#kanban#feature analysis#git commits
One-click install
npx skills add https://github.com/TomasGC/Meerkat --skill analyze-feature-tomasgc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-feature
Source: https://github.com/TomasGC/Meerkat/tree/main/skills/analyze-feature
Command: npx skills add https://github.com/TomasGC/Meerkat --skill analyze-feature-tomasgc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding a complete feature requires manually piecing together scattered information across KANBAN boards, GitHub issues, wiki documentation, and git history across multiple repositories, which is slow and error-prone. ## Core Features & Use Cases - Multi-Source Discovery: Finds all related tickets, commits, and documentation links from KANBAN tags and GitHub issue IDs across multiple repositories. - Commit and Code Analysis: Examines git diffs on main/master branches to extract implementation details, database changes, and architectural decisions. - Structured Report Generation: Produces a seven-section report with executive summary, architecture, Mermaid diagrams, code examples, and recommendations. - Use Case: Run an analysis on the #payments tag to get a complete feature report covering business value, technical architecture, database schema changes, and actionable technical debt recommendations. ## Quick Start Ask the assistant to analyze a feature by providing KANBAN tags or GitHub issue IDs, such as analyzing the #payments tag or issue #123.

Frequently Asked Questions about analyze-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a feature across multiple git repositories?▼

Provide KANBAN tags or GitHub issue IDs, and the analysis reads ARCHITECTURE.md to detect all connected repositories. It then searches each repo's KANBAN.md for matching entries and analyzes commits from main or master branches.

How to generate a feature report from GitHub issues and commits?▼

Pass issue IDs or tags to the analysis command, which retrieves issue details and comments via GitHub CLI, follows wiki links, examines commit diffs, and synthesizes everything into a structured seven-section report with Mermaid diagrams.

What happens if a commit is not found in any repository?▼

The analysis warns that the commit was not found, lists the repositories checked, and continues without blocking. Missing commits are treated as non-blocking so the report still completes with available data.

Does the feature analysis work without a KANBAN.md file?▼

Without KANBAN.md, tag-based discovery is unavailable, but you can still provide GitHub issue IDs directly. The analysis will warn about the missing file and offer options to continue or abort.

What language is the feature analysis report written in?▼

All reports are written in English regardless of the conversation language. Quoted GitHub or wiki content remains in its original language, but every report section, diagram, and recommendation is in English.

Related Skills

Explore More Software Engineering Skills→
hamzaPixlhamzaPixl
2

changelog

Generate grouped markdown changelog entries from conventional commit histories.

Community
Intermediate
webrix-aiwebrix-ai
1

sprint-planning

Analyze sprint capacity and prioritize Jira or Linear backlog items.

Official
Intermediate
Coverage-CreativesCoverage-Creatives

Quality Gates

Enforce quality thresholds across code, tests, performance, and security in CI/CD pipelines.

Official
Advanced
ZeydenZeyden

Code Review

Review git branch code changes for quality, security, and performance.

Community
Advanced