agentleFS
abhaylaabhayla/claude-best-practices/.claude/skills/scan-repo/SKILL.md

scan-repo

Skill9 starsChanged 7 months agoMITView on GitHub

Trigger a project scan for a specific repository. Normalizes repo input and triggers scan workflow.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    Check that the workflow dispatched successfully:

    line 35
  2. Distinctive:

    MUST validate the repo format before triggering — reject malformed inputs

    line 64
  3. Distinctive:

    MUST NOT trigger scans for private repos without confirming the user has access

    line 65
  4. Distinctive:

    MUST report the workflow run URL so the user can monitor progress

    line 66

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

Scan Repo — Trigger Project Pattern Scan

Scan a GitHub repository for reusable Claude Code patterns.

Input: $ARGUMENTS


STEP 1: Normalize Input

Accept various formats:

  • owner/repo → use directly
  • https://github.com/owner/repo → extract owner/repo
  • repo → assume current org or ask for owner

STEP 2: Trigger Scan

gh workflow run scan-projects.yml -f repo="$OWNER/$REPO"

STEP 3: Verify Trigger

Check that the workflow dispatched successfully:

gh run list --workflow=scan-projects.yml --limit=1
StatusAction
queued or in_progressReport success, provide run URL
Not foundVerify gh is authenticated and workflow exists: gh workflow list
ErrorReport the error message and suggest manual trigger via GitHub UI

STEP 4: Post-Scan Follow-Up

Report the trigger result:

Scan triggered:
  Repo: $OWNER/$REPO
  Workflow: scan-projects.yml
  Monitor: gh run watch <run-id>

Optionally ask if the repo should be added to the tracked repos list in config/repos.yml.


CRITICAL RULES

  • MUST validate the repo format before triggering — reject malformed inputs
  • MUST NOT trigger scans for private repos without confirming the user has access
  • MUST report the workflow run URL so the user can monitor progress

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.