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
- gittower/git-flow-nexttheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- gittower/git-flow-next★ 458same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository44 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- anthropic-multi-agent-research-system-skillSkill
- apply-selectionsSkill
- bootstrap-dogfood-projectSkill
- brainstormSkill
- branch-choiceSkill
- cc-adoption-scoutSkill
- claude-guardianSkill
- continueSkill
- end-sessionSkill
- executing-plansSkill
- five-advisorsSkill
- get-work-doneSkill
- git-branch-lifecycleSkill
- githubSkill
- grill-meSkill
- hook-transcript-fixture-testSkill
- instagramSkill
- linkedinSkill
- modern-data-pipeline-diagramSkill
- pattern-qualitySkill
- platform-event-live-probeSkill
- plugin-lifecycleSkill
- promote-to-coreSkill
- prompt-auto-enhanceSkill
- provision-reportSkill
- redditSkill
- review-new-claude-featuresSkill
- save-sessionSkill
- scan-discovery-reportSkill
- scan-urlSkill
- self-improveSkill
- skill-evaluatorSkill
- skill-masterSkill
- ssot-workflow-auditSkill
- start-sessionSkill
- synthesize-hubSkill
- synthesize-projectSkill
- twitter-xSkill
- verify-effect-at-destinationSkill
- workflow-doc-reviewerSkill
- writing-plansSkill
- writing-skillsSkill
- youtube-transcriptSkill
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
- Distinctive: line 35
Check that the workflow dispatched successfully:
- Distinctive: line 64
MUST validate the repo format before triggering — reject malformed inputs
- Distinctive: line 65
MUST NOT trigger scans for private repos without confirming the user has access
- Distinctive: line 66
MUST report the workflow run URL so the user can monitor progress
≈ “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.
Files
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 directlyhttps://github.com/owner/repo→ extractowner/reporepo→ 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| Status | Action |
queued or in_progress | Report success, provide run URL |
| Not found | Verify gh is authenticated and workflow exists: gh workflow list |
| Error | Report 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
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
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.

