agentleFS
clideyclidey/whodb/.agents/skills/cli-feature/SKILL.md

cli-feature

Skill5.1k starsChanged 3 days agoApache-2.0View on GitHub

Add a new command or TUI view to the WhoDB CLI

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 8 mentionsApr 2026: 4 mentionsMay 2026: 5 mentionsJun 2026: 6 mentionsJul 2026: 5 mentionsAug 2026: 6 mentionsSep 2026: 6 mentionsOct 2026: 9 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the clidey/whodb repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about clidey/whodb

The biggest 5 of 60 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 60

Talked about on GitHub, Bluesky and Hacker News (60 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 7

2 more on Bluesky

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use database.Manager for all DB operations (direct plugin access, not GraphQL)

    line 32
  2. Very specific:

    Keep main.go thin — it calls the shared runtime, nothing else

    line 35
  3. Very specific:

    Add view mode to cli/internal/tui/model.go

    line 55
  4. Very specific:

    Add navigation in Update()

    line 56
  5. Very specific:

    Use pkg/styles for consistent rendering

    line 57
  6. Distinctive:

    Don't use lipgloss Padding with viewport output (use manual prefix)

    line 63
  7. Very specific:

    Use database.Manager for data access

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add a CLI Feature

Adding a New Command

1. Create Command File

cli/cmd/<name>.go:

package cmd

import "github.com/spf13/cobra"

var <name>Cmd = &cobra.Command{
    Use:   "<name>",
    Short: "Description",
    RunE: func(cmd *cobra.Command, args []string) error {
        // Implementation using database.Manager
        return nil
    },
}

func init() {
    rootCmd.AddCommand(<name>Cmd)
}

2. Key Rules

  • Use database.Manager for all DB operations (direct plugin access, not GraphQL)
  • Identity-driven text: write whodb in command examples; use pkg/identity helpers for display names and home-dir paths, never hardcode edition-specific names
  • Structured output: use pkg/output writers (table/json/csv/ndjson) for machine-readable commands
  • Keep main.go thin — it calls the shared runtime, nothing else

3. Verification

cd cli && go build . && go vet ./...

Adding a New TUI View

1. Create View File

cli/internal/tui/<name>_view.go:

Implement the Bubble Tea model interface:

  • Init() tea.Cmd
  • Update(msg tea.Msg) (tea.Model, tea.Cmd)
  • View() string

2. Add to MainModel

  • Add view mode to cli/internal/tui/model.go
  • Add navigation in Update()
  • Use pkg/styles for consistent rendering

3. Key Patterns

  • Vim-like navigation (hjkl)
  • Tab for view switching
  • Esc for going back
  • Don't use lipgloss Padding with viewport output (use manual prefix)
  • Use database.Manager for data access

4. Verification

cd cli && go test ./internal/tui/... && go build .

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.