New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Implement GitHub Feature

by AgnosticUI in AgnosticUI/agnosticui

Design and implement a new feature or component from a GitHub issue.

Apache-2.0Auto-check passedDevelopment

Install Implement GitHub Feature

skills CLI
$ npx skills add AgnosticUI/agnosticui --skill implement-github-feature -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AgnosticUI/agnosticui implement-github-feature --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AgnosticUI/agnosticui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/implement-github-feature .claude/skills/implement-github-feature && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
implement-github-feature
GitHub stars
826
Token cost
~1.6k tokens
SKILL.md length
626 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Design and implement a new feature or component from a GitHub issue.

  • Works in 10 steps: Safety Checks (Required) → Branching → Issue Analysis & Intent Extraction (No… → …
  • Net-new functionality
  • SKILL.md covers Setup, Phase 0: Safety Checks…, Phase 1: Branching and Phase 2: Issue Analysis &…, plus 8 more sections
  • Calls git and npm

What it does

Implement GitHub Feature is an agent skill from AgnosticUI/agnosticui. Design and implement a new feature or component from a GitHub issue. Use for net-new functionality, not bug fixes.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Debugging. It works with GitHub, React and Vue.js. The repository describes itself as: AgnosticUI Local (v2) is a CLI-based UI component library that copies components directly into your project. Works with AI tools, agent-driven UIs, and prompt-ready workflows. The licence is Apache-2.0.

When your agent uses it

  • Net-new functionality
  • Tasks that involve Debugging

Example prompts

  • “/implement-github-feature”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Edit, Write, Bash(gh issue view *), Bash(gh pr view *), Bash(git status), Bash(git diff *), Bash(git log *), Bash(git branch *), Bash(git checkout *), Bash(git add *), Bash(git commit *), Bash(npm run build), Bash(npm run lint), Bash(ls *)

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Safety Checks (Required)
  2. Branching
  3. Issue Analysis & Intent Extraction (No Code)
  4. Design Proposal (Hard Stop Before Code)
  5. Scaffolding (Minimal, Intentional)
  6. Core Implementation (Lit Web Components First)
  7. Framework Integrations
  8. Documentation & Examples
  9. Final Review & Commit
  10. Handoff

What it can do on your machine

Read from SKILL.md and the folder at commit c028c27. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Edit
    • Write
    • Bash(gh issue view *)
    • Bash(gh pr view *)
    • Bash(git status)
    • Bash(git diff *)
    • Bash(git log *)

    …and 7 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Implement GitHub Feature loads about 1.6k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 626 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AgnosticUI/agnosticui at commit c028c27, republished under its Apache-2.0 licence (© AgnosticUI). 626 words, ~1,630 tokens.

Download SKILL.mdSave it as .claude/skills/implement-github-feature/SKILL.md (or your agent's skills folder).
name
implement-github-feature
description
Design and implement a new feature or component from a GitHub issue. Use for net-new functionality, not bug fixes.
allowed-tools
Read, Grep, Glob, Edit, Write, Bash(gh issue view *), Bash(gh pr view *), Bash(git status), Bash(git diff *), Bash(git log *), Bash(git branch *), Bash(git checkout *), Bash(git add *), Bash(git commit *), Bash(npm run build), Bash(npm run lint), Bash(ls *)
disable-model-invocation
true

Usage: /implement-github-feature ISSUE_NUMBER

Example: /implement-github-feature 281

Implement GitHub feature request $ARGUMENTS following AgnosticUI conventions, accessibility standards, and CSS-first principles.

Setup

  1. Read project context
    • Read .claude/PROJECT_CONTEXT.md
    • Understand:
      • Repository structure
      • Design principles
      • Accessibility requirements
      • Branch conventions
      • Component workflows

Phase 0: Safety Checks (Required)

  1. Verify clean starting state
    • Run git status
    • Confirm:
      • Working directory is clean
      • Current branch is master
    • If either condition fails:
      • STOP
      • Ask the user to resolve before continuing

Phase 1: Branching

  1. Propose feature branch
    • Follow convention: issue-$ARGUMENTS/short-descriptive-name
    • Example: issue-281/selection-card-group
    • Run:
      git checkout -b issue-$ARGUMENTS/short-description
    • WAIT FOR USER APPROVAL of branch name before proceeding

Phase 2: Issue Analysis & Intent Extraction (No Code)

  1. Analyze the GitHub issue

    • Fetch full details:
      gh issue view $ARGUMENTS
    • Extract and summarize:
      • Feature goals
      • Non-goals / constraints
      • API expectations
      • Accessibility requirements
      • Styling and theming expectations
      • Framework implications (Lit / React / Vue)

  2. Study existing related components

    • Identify components this feature will compose or resemble
    • Read their implementations in v2/lib/src/components/
    • Note patterns for:
      • Props and attributes
      • Slot usage
      • CSS custom properties
      • ::part exposure
      • Event dispatching
      • Accessibility implementation
    • This ensures consistency with established AgnosticUI conventions

  3. Confirm feature classification

    • This is a:
      • Net-new component OR
      • Major enhancement (not a bug fix)
    • If scope appears ambiguous:
      • Ask the user before proceeding

Phase 3: Design Proposal (Hard Stop Before Code)

  1. Propose high-level design

    • Identify:
      • New components to be created
      • Public vs internal APIs
      • Required props vs optional props
      • Slot usage and responsibilities
      • Accessibility model (labels, roles, keyboard behavior)
      • Shadow DOM strategy (::part, ::slotted)
    • Explicitly call out:
      • Web Component constraints
      • CSS-first decisions
      • What is intentionally not supported

  2. Propose file & directory layout

    • Core components:
      • v2/lib/src/components/...
    • Documentation:
      • v2/site/docs/components/...
    • Storybook playgrounds:
      • Lit
      • React
      • Vue
    • Examples:
      • Lit / React / Vue test examples

  3. WAIT FOR USER APPROVAL

  • Do not create files
  • Do not write code
  • Proceed only after explicit approval of:
    • API shape
    • Accessibility approach
    • Styling strategy

Phase 4: Scaffolding (Minimal, Intentional)

  1. Create initial scaffolding

    • Create component directories
    • Add placeholder files where appropriate
    • Add minimal README or doc stubs if needed
    • No implementation logic yet

  2. Show scaffolding diff

    • Use git diff
    • Explain what was created and why
    • WAIT FOR USER APPROVAL
Show full SKILL.md (275 more words)Show less

Phase 5: Core Implementation (Lit Web Components First)

  1. Implement core component(s)

    • Work only in:
      • v2/lib/src/components/
    • Follow:
      • CSS-first approach
      • Design token usage
      • Accessibility requirements
    • Ensure:
      • Keyboard interaction works
      • Labels and semantics are correct
      • Shadow DOM parts are intentional and minimal

  2. Verify build

    • Run npm run build in v2/lib/
    • Fix any compilation errors
    • Run npm run lint if available

  3. Pause for review

    • Explain:
      • DOM structure
      • Slot behavior
      • ::part surface
      • Accessibility decisions
    • WAIT FOR USER APPROVAL before proceeding

Phase 6: Framework Integrations

  1. Integrate with frameworks

    • React playground
    • Vue playground
    • Lit playground
    • APIs should feel idiomatic but map 1:1 conceptually

  2. Add Storybook stories

    • Demonstrate:
      • Core use cases
      • Variants
      • Accessibility states
    • Ensure consistency across frameworks

Phase 7: Documentation & Examples

  1. Write documentation

    • Add VitePress docs:
      • API
      • Slots vs props
      • Styling guidance
      • Accessibility notes
    • Update or add playbooks if applicable

  2. Update examples

    • Verify examples compile and behave correctly
    • Keep examples minimal and educational

Phase 8: Final Review & Commit

  1. Final verification

    • Review:
      • git diff
      • Accessibility behavior
      • Styling hooks
      • API consistency
    • Ensure no accidental breaking changes

  2. Prepare commit

    • Stage changes:
      git add .
    • Commit message format:
      Add #$ARGUMENTS: [concise feature description]
    • Show commit contents
    • WAIT FOR USER APPROVAL before committing

Phase 9: Handoff

  1. Explain next steps
    • User is on branch: issue-$ARGUMENTS/...
    • Review with:
      git diff master
    • Push when ready:
      git push -u origin issue-$ARGUMENTS/...
    • Create PR:
      gh pr create --base master --head issue-$ARGUMENTS/...

Important Rules

  • NEVER work directly on master
  • NEVER push without explicit user permission
  • ALWAYS stop at design gates
  • ALWAYS prioritize accessibility over convenience
  • Prefer slots for layout, props for semantics
  • CSS custom properties > ::part > ::slotted
  • Do not assume intent — if unclear, ask

© AgnosticUI, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/implement-github-feature of AgnosticUI/agnosticui.

Open the folder on GitHubat commit c028c27

Compare with similar skills

Implement GitHub Feature next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Implement GitHub Feature compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Implement GitHub Feature this skillAgnosticUI/agnosticui826—~1.6kAutomated safety check: PassApache-2.0
Web CloneJane-xiaoer/claude-skill-web-clone1k1 repos~2.7kAutomated safety check: PassMIT
Wagmi Feature Developmentwevm/wagmi6.8k—~3.8kAutomated safety check: PassMIT
Electron DevTools Trace Analysiskeybase/client9.3k—~809Automated safety check: PassBSD-3-Clause
Uncodixfypdsuwwz/chatgpt-vue3-light-mvp5782 repos~3kAutomated safety check: PassMIT
Renderdoc GPU Debugrudybear/renderdoc-skill211—~4kAutomated safety check: PassMIT

Similar skills

  • Web Clone

    Jane-xiaoer/claude-skill-web-clone

    网站复刻 / 克隆方法论。USE WHEN 用户说 复刻网站、克隆网站、clone website、抄个站、仿站、 照着这个站做一个、reproduce site、还原某个网页效果、把这个站搬下来改成我的、 复刻某个交互/WebGL/Canvas/Three.js 效果。提供「先拿真源码 → 判路径 → 逆向拆解 → 搭工程 → 替换内容」的可移植决策树，覆盖静态站 /…

    1k GitHub starsUsed in 1 repo~2.7k tokens
    Game DevelopmentAuto-check passed

  • Wagmi Feature Development

    wevm/wagmi

    Walks through adding a Wagmi feature across its layers: a Viem-based core action, TanStack Query options, and React and Vue bindings.

    6.8k GitHub stars~3.8k tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • Electron DevTools Trace Analysis

    keybase/client

    Analyzes Chrome or Electron DevTools Performance trace exports with Python scripts to find where render time actually goes, without opening DevTools.

    9.3k GitHub stars~809 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Uncodixfy

    pdsuwwz/chatgpt-vue3-light-mvp

    Prevents generic AI/Codex UI patterns when generating frontend code.

    578 GitHub starsUsed in 2 repos~3k tokens
    Frontend & DesignAuto-check passed

  • Renderdoc GPU Debug

    rudybear/renderdoc-skill

    GPU frame debugging with RenderDoc via rdc-cli. An agent skill from rudybear/renderdoc-skill.

    211 GitHub stars~4k tokensUpdated 7 mo ago
    DevelopmentAuto-check passed

  • Bit CLI

    teambit/bit

    MUST consult before running ANY bit command. An agent skill from teambit/bit.

    18k GitHub stars~2k tokensUpdated yesterday
    DevelopmentAuto-check: warnings

More from AgnosticUI/agnosticui

  • Implement Ag Playbook

    AgnosticUI/agnosticui

    Implement a playbook from its PROMPT specification files. An agent skill from AgnosticUI/agnosticui.

    826 GitHub stars~1.7k tokensUpdated 3 mo ago
    Auto-check passed

  • Update Component Docs

    AgnosticUI/agnosticui

    Update component documentation when code changes. An agent skill from AgnosticUI/agnosticui.

    826 GitHub stars~607 tokensUpdated 3 mo ago
    Auto-check passed

  • Check Accessibility

    AgnosticUI/agnosticui

    Review component for accessibility issues. An agent skill from AgnosticUI/agnosticui.

    826 GitHub stars~635 tokensUpdated 3 mo ago
    Auto-check passed

  • Fix GitHub Issue

    AgnosticUI/agnosticui

    Fix a GitHub issue by number. An agent skill from AgnosticUI/agnosticui.

    826 GitHub stars~751 tokensUpdated 3 mo ago
    Auto-check passed

  • Explain Code

    AgnosticUI/agnosticui

    Explain what code does in plain English

    826 GitHub starsUsed in 1 repo~507 tokens
    Auto-check passed

Works with

Categories

Questions about Implement GitHub Feature

What does Implement GitHub Feature do?

Design and implement a new feature or component from a GitHub issue. Implement GitHub Feature is an agent skill from AgnosticUI/agnosticui. Design and implement a new feature or component from a GitHub issue.

When should I use Implement GitHub Feature?

Implement GitHub Feature fits situations like: net-new functionality; tasks that involve Debugging.

How do I install Implement GitHub Feature in Claude Code?

Run `npx skills add AgnosticUI/agnosticui --skill implement-github-feature -a claude-code`. Or copy the skill folder (.claude/skills/implement-github-feature in AgnosticUI/agnosticui) into .claude/skills/implement-github-feature in your project. Claude Code loads it when a task matches its description.

How do I install Implement GitHub Feature in Codex?

Run `npx skills add AgnosticUI/agnosticui --skill implement-github-feature -a codex`. Or copy the skill folder (.claude/skills/implement-github-feature in AgnosticUI/agnosticui) into .agents/skills/implement-github-feature in your project. Codex loads it when a task matches its description.

Can I use Implement GitHub Feature in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgnosticUI/agnosticui --skill implement-github-feature -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implement-github-feature, .gemini/skills/implement-github-feature, .github/skills/implement-github-feature and .opencode/skills/implement-github-feature in your project.

What does Implement GitHub Feature need to run?

Going by SKILL.md and its folder, Implement GitHub Feature needs the command-line tools its instructions call (git and npm). Its frontmatter pre-approves these tools: Read, Grep, Glob, Edit, Write, Bash(gh issue view *), Bash(gh pr view *), Bash(git status), Bash(git diff *), Bash(git log *), Bash(git branch *), Bash(git checkout *), Bash(git add *), Bash(git commit *), Bash(npm run build), Bash(npm run lint), Bash(ls *).

Does Implement GitHub Feature access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Implement GitHub Feature safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Implement GitHub Feature use?

Implement GitHub Feature is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Implement GitHub Feature use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Implement GitHub Feature?

Skills that share tags, products or a category with Implement GitHub Feature: Web Clone (Jane-xiaoer/claude-skill-web-clone, 1k stars), Wagmi Feature Development (wevm/wagmi, 6.8k stars), Electron DevTools Trace Analysis (keybase/client, 9.3k stars) and Uncodixfy (pdsuwwz/chatgpt-vue3-light-mvp, 578 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Implement GitHub Feature?

AgnosticUI (a GitHub organization) maintains it in AgnosticUI/agnosticui, which has 826 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on June 30, 2026.

Source: AgnosticUI/agnosticui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.