Implement Issue Agent Skill

> Implement a Site Kit GitHub issue end-to-end from its implementation brief. Use when the user asks to implement, build, or work on a GitHub issue / feature by number (e.g. "implement issue #12345", "build the feature in issue 12345", "follow the implementation brief for #12345") in the google/site-kit-wp repo.

511 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

1393

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/google/site-kit-wp --skill implement-issue

What it tells the agent to use

found in the instruction text

Bash runs shell commands — read the instruction before connecting

The instruction itself

3 sections, as written by the author

Implement a GitHub issue

Implement GitHub issue #$ARGUMENTS (if no number was given, ask for one) by following the

project's shared playbook. Do not reimplement the procedure here — read and follow the

playbook, which is the single source of truth shared with the other AI tools.

Procedure

Read the playbook docs/context/workflow/implement-issue.md and follow every step:

fetch & parse the issue, determine scope, load only the relevant docs/context/{js,php}

convention docs (per the map in the playbook), branch off develop, implement with

co-located tests/stories, self-review, and verify.

Fetch the issue: gh issue view $ARGUMENTS --json title,body,labels. Stop and ask the

user if the issue is missing, empty, or the Implementation Brief is ambiguous.

Self-review your diff against docs/context/workflow/review-checklist.md and fix gaps

before finishing.

Verify with the exact commands in the playbook (lint, targeted tests, build).

Important

Local only: never commit, push, or open a PR unless the user explicitly asks.
Run only the specific test files you touched (npm -w tests/js run test:js -- <path>),

not the whole suite.

Lint only the files you touched (npm run lint:js:files -- <path> / `composer lint --

<path>`), and if you touched a Storybook story, check just that VRT scenario

(./tests/backstop/bin/backstop test --filter="<scenario label>") rather than the full

suite.

The convention details are in docs/context/{js,php}/ — read what the issue touches, not

everything.

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use 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 cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take google/site-kit-wp-implement-issue from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.