pre-build-feature-audit
Use when a proposed open-source feature must be checked across source, history, branches, issues, pull requests, roadmaps, and contributor guidance before implementation begins.
npx skills add asimons81/hermes-field-kit --skill pre-build-feature-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# pre-build-feature-audit ## Overview A read-only multi-surface duplicate check across source, history, branches, issues, pull requests, roadmaps, and contributor guidance. The skill is evidence-first. It identifies unavailable evidence, separates facts from interpretations, and does not claim a repair or successful outcome merely because a command returned without an obvious error. ## When to Use
What does the pre-build-feature-audit skill do?
Use when a proposed open-source feature must be checked across source, history, branches, issues, pull requests, roadmaps, and contributor guidance before implementation begins.
How do I install it?
Run `npx skills add asimons81/hermes-field-kit --skill pre-build-feature-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From asimons81/hermes-field-kit, a repository with 120 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.