Coding standards, frameworks, refactoring, and code review (15.8K skills)
Create a draft pull request from the current branch using the project’s template. The skill checks changes, detects the base branch, gathers label choices, and prepares a title, description, and testing details.
Work through unresolved GitHub pull request reviews one at a time. The skill explains each comment, proposes a fix, asks how to proceed, and handles chosen edits, replies, commits, and thread resolution.
Set up a working preview file and stories, examples showing real components, in an existing Storybook project. Check the installed version first, then follow the setup instructions produced by Storybook’s command.
Upgrade an existing Storybook installation to version 11.0 or later using the official upgrade instructions. When the latest stable release is below 11.0, the skill directs the agent to use the 11.0 alpha release.
Add Storybook to a project that has no existing setup. Check the stable release to choose the installation tag, use the appropriate package manager, and hand off project-specific configuration to the separate /storybook-setup skill.
Prepare a CHANGELOG.md entry for a Storybook minor or major release. Collect changes from prereleases, filter out changes already backported to patch releases, select significant highlights, and combine them with the full change list.
Set up an existing Storybook installation with a working preview file and stories that display real components. The skill checks prerequisites, then uses Storybook’s setup command and the instructions it provides.
Update all Storybook packages in a project to a chosen release or canary, an early development build. Use it to test changes in external apps, reproduce bugs, and keep package versions aligned while handling peer dependencies.
Add Storybook to a project that does not have it configured, choosing the installation tag based on the latest stable version. Then use the separate setup skill to configure Storybook for the project.
Upgrade an existing Storybook installation to version 11.0 or later using the official upgrade guide. If the latest stable release is below 11.0, the skill uses the 11.0 alpha, a prerelease version.
Rebuild modified packages in the Storybook monorepo and restart its internal UI after code changes. The workflow provides the running URL and can optionally create a UI review of stories related to the changes.
Check out a GitHub pull request, fix linting and TypeScript errors, and commit and push the changes. The workflow supports forked pull requests and repeats type checks to verify fixes while keeping changes focused on these errors.
Create a draft pull request for reviewing Storybook changes. Prepare a title, required labels, and a description using the repository template, including verified manual testing steps that another maintainer can follow.
Review Storybook's minimum supported browser versions using Plausible documentation traffic data. The skill presents usage evidence and proposed versions for approval, then updates pinned settings and documentation and opens a pull request with the recorded decision.
Extract website content into Markdown, HTML, or plain text with Scrapling. Handle JavaScript-rendered pages and anti-bot challenges, or write Python crawlers that follow links, collect structured data, and resume interrupted runs.
Analyze project code, configuration, and documentation to build a graph for interactive architecture exploration. It maps components and dependencies, supports Japanese descriptions, and can update the analysis based on changes since the previous analyzed commit.
Launch the Understand Anything web dashboard to explore an existing codebase knowledge graph, a map of its structure and relationships. Open the current project or a specified directory and receive the local access URL.
Extract business areas, workflows, and process steps from a codebase and display them as an interactive horizontal flow graph. Use an existing knowledge graph, a map of project components, or run a lightweight scan of project files.
Get a detailed explanation of a file, function, or module using an existing knowledge graph and its source code. It explains architectural roles, dependencies, callers, and data flow for readers who may not know the programming language.
Ask questions about a codebase using a knowledge graph, a map of its components and relationships. Get explanations tied to specific files, functions, dependencies, and architectural layers, with warnings when the graph may be outdated.
Analyze Git changes or pull requests against a knowledge graph, a map of code components and relationships. Identify modified files, nearby dependencies, affected architectural layers, and review risks, then save data for a dashboard visualization.
Audit a codebase for unnecessary complexity, including dead code, duplicated state, redundant interfaces, and obsolete compatibility paths. Receive evidence-backed simplification candidates, or authorize changes that remove justified targets and validate the behavior that must remain.
Evaluate improvements to Archify diagrams using actual outputs and agent work records. Compare accuracy, readability, and total delivery time to investigate layout, connection routing, diagnostics, and authoring guidance, then document what the evidence supports.
Review Archify issues, pull requests, and code by weighing user value, implementation and maintenance costs, and wider impact. Use evidence to decide whether work is worthwhile, compare alternatives, and identify questions that still affect the decision.