TJaenichenTJaenichen/claude-code-harness/skills/project/find-code/SKILL.md

find-code

Skill0 starsChanged 3 months agoMITView on GitHub

Find controllers, services, models, and views by feature name in the Payments projects.

In this repository27 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- buildSkill
- cleanup-worktreeSkill
- db-querySkill
- db-searchSkill
- dd-errorsSkill
- devops-wiki-updateSkill
- devops-workitem-createSkill
- devops-workitem-readSkill
- devops-workitem-updateSkill
- finalize-taskSkill
- merge-mainSkill
- panel-review-fixSkill
- panel-reviewSkill
- prSkill
- rebase-mainSkill
- starttaskSkill
- testSkill
- ask-codexSkill
- ask-geminiSkill
- councilSkill
- dailySkill
- find-sessionSkill
- merged-prsSkill
- mm-notifySkill
- optimize-promptSkill
- qSkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Search for code related to the feature in the appropriate project.
line 13

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Find Code by Feature

Feature: $ARGUMENTS

Your task

Search for code related to the feature in the appropriate project.

API project locations (`Contoso.Payments.Api/`)

Component	Pattern	Example
Controller	`Contoso.Payments.API/Controllers/{Feature}Controller.cs`	`BonusesController.cs`
Service Interface	`Contoso.Payments.API.Application/Interfaces/I{Feature}Service.cs`	`IBonusService.cs`
Service Implementation	`Contoso.Payments.API.Infrastructure/Services/`	Search for `{Feature}Service.cs`
Domain Models	`Contoso.Payments.API.Domain/Models/{Feature}/`	`Models/Bonus/`
EF Models	`Contoso.Payments.API.EFModels/`	Search for `{Feature}*.cs`
CQRS Commands/Queries	`Contoso.Payments.API.Application/`	Search for `{Feature}Command.cs`, `{Feature}Query.cs`

Web admin project locations (`Contoso.Payments/`)

Component	Pattern	Example
Controller	`Contoso.Payments.Web/Controllers/{Feature}Controller.cs`	`ProcessorsController.cs`
Views	`Contoso.Payments.Web/Views/{Feature}/`	`Views/Processors/`
Services	`Contoso.Payments.Application/Services/`	Search for `{Feature}Service.cs`

Search strategy

Glob for exact matches:

**/Controllers/*{Feature}*.cs
**/Services/*{Feature}*.cs
**/Models/*{Feature}*/**

Grep for references:
```
rg -l -i "{feature}" --type cs
```

Output

Report found files organized by component type (Controller, Service, Model, etc.)

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.

Check your setup, free