ccc-skill-create

/ccc-skill-create — a project skill from git history

CC Commander · /ccc-skill-create · a reviewed SKILL.md describing how this repository is actually worked on.

Arguments

$ARGUMENTS:

What happens

1. Confirm a git repository: git rev-parse --show-toplevel. If it fails, say so and stop. Use the top-level directory name as <repo-name>.

2. Gather history (replace 200 with --commits):

   git log -n 200 --name-only --pretty=format:"%H|%s|%ad" --date=short
   git log -n 200 --name-only --pretty=format: | grep -v '^$' | sort | uniq -c | sort -rn | head -20
   git log -n 200 --pretty=format:%s | head -50
   

   If the repository has fewer commits than requested, analyze what exists and report the actual count.

3. Detect patterns, each backed by evidence from step 2:

   Pattern	How to detect
   Commit conventions	Prefixes in subjects (feat:, fix:, chore:) and the share that follow them
   File co-changes	Files that appear in the same commits repeatedly
   Workflow sequences	Recurring sets of files changed for one kind of task
   Architecture	Folder structure and naming, from git ls-files
   Testing	Test file locations, naming, and the framework in the manifest

   Report a pattern only when it recurs; give its count (for example "41 of 50 subjects use conventional prefixes").

4. Draft <output>/<repo-name>-patterns/SKILL.md in this shape:

   ---
   name: <repo-name>-patterns
   description: "Coding conventions and workflows used in <repo-name>. Use when writing commits, adding features or tests in this repository."
   metadata:
     source: local-git-analysis
     analyzed_commits: <n>
   ---
   
   # <Repo name> patterns
   
   ## Commit conventions
   ## Code architecture
   ## Workflows   (numbered steps per recurring task, with the exact files and commands)
   ## Testing patterns