SkillAgentSearch skills...

skillshare-implement-feature

Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare.

Install / Use

npx skills add runkids/skillshare --skill skillshare-implement-feature

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Category

Automation

Supported Platforms

Universal

Our assessment of skillshare-implement-feature

skillshare-implement-feature scores 93/100 on our quality scale, 670th of 2,790 Automation skills we index (top 25%).

Its SKILL.md is 7.6 KB long, well organised into 23 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.

With 2,689 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so skillshare-implement-feature is actively maintained.
  • Our last check on 2026-10-26 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

skillshare-implement-feature compared with similar skills

All 4 of these similar skills score higher than skillshare-implement-feature; compare them before choosing.

SkillScoreStarsUpdatedFormat
skillshare-implement-feature (this skill)by runkids932.7k54d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install skillshare-implement-feature?
Run npx skills add runkids/skillshare --skill skillshare-implement-feature. The install tabs above show the steps for each supported agent.
Which AI agents does skillshare-implement-feature work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is skillshare-implement-feature safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is skillshare-implement-feature still maintained?
The repository was last updated about 2 months ago, so skillshare-implement-feature is actively maintained.

name: skillshare-implement-feature description: >- Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development, proper handler split conventions, oplog instrumentation, and dual-mode (global/project) patterns. If the request involves writing Go code and tests, use this skill — even if the user doesn't explicitly say "implement". argument-hint: "[spec-file-path | feature description]" metadata: targets: [claude, universal]

Implement a feature following TDD workflow. $ARGUMENTS is a spec file path (e.g., specs/my-feature.md) or a plain-text feature description.

Scope: This skill writes Go code and tests. It does NOT update website docs (use update-docs after) or CHANGELOG (use changelog after).

Before acting, run python3 scripts/ai-context.py cli-development testing. Those topics are the source of truth for repository patterns, execution boundaries and verification; this skill retains the TDD orchestration.

Workflow

Step 1: Understand Requirements

If $ARGUMENTS is a file path:

  1. Read the spec file
  2. Extract acceptance criteria and edge cases
  3. Identify affected packages

If $ARGUMENTS is a description:

  1. Search existing code for related functionality
  2. Identify the right package to extend
  3. Ask the user only if ambiguity would materially change scope or public interfaces

Step 2: Identify Affected Files

List all files that will be created or modified:

# Typical pattern for a new command
cmd/skillshare/<command>.go          # Command handler
cmd/skillshare/<command>_project.go  # Project-mode handler (if dual-mode)
internal/<package>/<feature>.go      # Core logic
tests/integration/<command>_test.go  # Integration test

Display the file list and continue.

Step 3: Write Failing Tests First (RED)

Write integration tests using testutil.Sandbox:

func TestFeature_BasicCase(t *testing.T) {
    sb := testutil.NewSandbox(t)
    defer sb.Cleanup()

    // Setup
    sb.CreateSkill("test-skill", map[string]string{
        "SKILL.md": "---\nname: test-skill\n---\n# Content",
    })

    // Act
    result := sb.RunCLI("command", "args...")

    // Assert
    result.AssertSuccess(t)
    result.AssertOutputContains(t, "expected output")
}

Verify tests fail (inside the devcontainer, see the skillshare-devcontainer skill):

docker exec "$CONTAINER" bash -c 'cd /workspace && go test ./tests/integration -run TestFeature_BasicCase -count=1'

Step 4: Implement (GREEN)

Write minimal code to make tests pass:

  1. Follow existing patterns in cmd/skillshare/ and internal/
  2. Use internal/ui for terminal output (colors, spinners, boxes)
  3. Add oplog instrumentation for mutating commands:
    start := time.Now()
    // ... do work ...
    e := oplog.NewEntry("command-name", statusFromErr(err), time.Since(start))
    oplog.Write(configPath, oplog.OpsFile, e)
    
  4. Register command in main.go commands map if new command

Verify tests pass:

docker exec "$CONTAINER" bash -c 'cd /workspace && make test-int'

Step 5: Refactor and Verify

  1. Clean up code while keeping tests green
  2. Run full quality check:
    docker exec "$CONTAINER" bash -c 'cd /workspace && make check'  # fmt-check + lint + test
    
  3. Fix any formatting or lint issues

Project Patterns Reference

These patterns appear throughout the codebase. Follow them when implementing new features.

Handler Split Convention

Large commands are split by concern rather than kept in a single file. When a command handler grows beyond ~300 lines, split it:

| Suffix | Purpose | Example | |--------|---------|---------| | <cmd>.go | Flag parsing + mode routing (dispatch) | install.go | | _handlers.go | Core handler logic | install_handlers.go | | _render.go / _audit_render.go | Output rendering | audit_render.go | | _prompt.go / _prompt_tui.go | Decision/prompt logic | install_prompt.go | | _tui.go | Full-screen TUI (bubbletea) | list_tui.go | | _batch.go | Batch operation orchestration | update_batch.go | | _resolve.go | Target/skill resolution | update_resolve.go | | _context.go | Mode-specific context struct | install_context.go | | _format.go | Output formatting helpers | log_format.go |

Principle: dispatch file does ONLY flag parsing + mode routing. Logic goes in sub-files.

Dual-Mode Command Pattern

Most commands support both global (-g) and project (-p) mode:

func handleMyCommand(args []string) error {
    mode, rest, err := parseModeArgs(args)
    if err != nil { return err }

    switch mode {
    case modeProject:
        return handleMyCommandProject(rest)
    default:
        return handleMyCommandGlobal(rest)
    }
}

Create <cmd>_project.go for project-mode handler. Use parseModeArgs() from mode.go.

TUI Components (bubbletea)

All interactive prompts use bubbletea (not survey). Key components:

  • checklist_tui.go — shared checklist/radio picker
  • list_tui.go — filterable list with detail panel
  • search_tui.go — multi-select checkbox list

Color palette: cyan Color("6"), gray Color("8"), yellow #D4D93C.

Dispatch order: JSON output → TUI (if TTY + items + no --no-tui flag) → empty check → plain text.

Web API Endpoint

If the feature needs a Web UI endpoint, add internal/server/handler_<name>.go:

func (s *Server) handle<Name>(w http.ResponseWriter, r *http.Request) {
    // ...
    writeJSON(w, result)       // 200 OK with JSON
    // writeError(w, 400, msg) // for errors
}

Register in server.go route setup. Branch on s.IsProjectMode() for mode-specific behavior.

Oplog Instrumentation

All mutating commands log to operations.log (JSONL):

start := time.Now()
// ... do work ...
e := oplog.NewEntry("command-name", statusFromErr(err), time.Since(start))
e.Args = map[string]any{"key": value}
oplog.Write(configPath, oplog.OpsFile, e)

Security scans write to oplog.AuditFile instead.

Step 6: E2E Runbook (Major Features Only)

If the feature meets any of these criteria, generate an E2E runbook:

  • New command or subcommand
  • Changes to install/uninstall/sync flow
  • Security-related (audit, hash verification, rollback)
  • Multi-step user workflow (init → install → sync → verify)
  • Edge cases that integration tests alone can't cover (Docker, network, file permissions)

Generate ai_docs/tests/<slug>_runbook.md following the existing convention:

# CLI E2E Runbook: <Title>

<One-line summary of what this validates.>

**Origin**: <version> — <why this runbook exists>

## Scope

- <bullet list of behaviors being validated>

## Environment

Run inside devcontainer with `ssenv` isolation.

## Steps

### 1. Setup: <description>

\```bash
<commands>
\```

**Expected**: <what should happen>

### 2. <Action>: <description>
...

## Pass Criteria

- All steps marked PASS
- <additional criteria>

Key conventions:

  • YAML-free, pure Markdown
  • Each step has bash block + Expected block
  • ss = skillshare, ~ = ssenv-isolated HOME
  • Runbook can be executed by the cli-e2e-test skill

If the feature does not meet the criteria above, skip this step.

Step 7: Stage and Report

  1. List all created/modified files
  2. Confirm each acceptance criterion is met with test evidence
  3. Remind user to run update-docs if the feature affects CLI flags or user-visible behavior

Rules

Apply cli-development and testing. Load documentation as well when the authorized task includes user-facing documentation.

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryAutomation
Updated1mo ago
Forks167

Languages

Go

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions