@hasna/skills 0.1.62 → 0.1.64

package/skills/scancommitpr/SKILL.md

@@ -1,178 +0,0 @@
----
-name: scancommitpr
-description: Scan repo for all changes, group them into logical commits, push to GitHub, and optionally create a pull request. Only creates a PR when the user explicitly asks for one.
----
-
-# Scan, Commit, Push & PR
-
-This skill performs the full scan/commit/push workflow and additionally offers to create a pull request on GitHub.
-
-**IMPORTANT**: Only create a PR if the user explicitly asked for one. If the user just said "commit" or "push", do NOT create a PR.
-
-## Phase 1: Scan, Commit & Push
-
-Follow ALL steps from the scancommitpush workflow:
-
-### Step 1: Pre-flight Checks
-
-1. **Verify git repo**: `git rev-parse --git-dir`. If not a repo, stop.
-2. **Check merge conflicts**: `git diff --name-only --diff-filter=U`. If any, stop and report.
-3. **Check branch**: `git branch --show-current`. Warn on detached HEAD.
-4. **Check remote**: `git remote -v`. If none, stop.
-5. **Check upstream**: `git rev-parse --abbrev-ref @{upstream} 2>/dev/null`. Note if missing.
-
-### Step 2: Scan All Changes
-
-1. `git status` (no `-uall` flag) — note staged, unstaged, untracked.
-2. `git diff --stat` — unstaged summary.
-3. `git diff --cached --stat` — staged summary.
-4. If no changes: "Working tree is clean. Nothing to commit." Stop.
-5. Detect and exclude sensitive files (.env, *.pem, *.key, credentials.json, .secrets/).
-
-### Step 3: Group Changes into Logical Commits
-
-Group by priority:
-1. **Feature/functionality** — related files implementing one feature/fix together
-2. **Type** — config, docs, deps, refactor, tests each separate
-3. **Scope** — unrelated areas get separate commits
-4. **Single-file** — lone changes get own commit
-
-When in doubt, split. Lockfiles go with their package.json. Test files go with the code they test.
-
-### Step 4: Create Commits
-
-For each group, in dependency order:
-
-1. Stage specific files: `git add <file1> <file2>` — NEVER `git add .`
-2. Commit with conventional message format:
-   ```
-   <type>: <imperative summary, max 72 chars>
-
-   <optional WHY body>
-
-   Co-Authored-By: Claude <noreply@anthropic.com>
-   ```
-   Types: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `style`, `perf`
-3. Use HEREDOC for commit message.
-4. Verify with `git log --oneline -1`.
-
-### Step 5: Push to Remote
-
-- No upstream: `git push -u origin <branch>`
-- Has upstream: `git push`
-- NEVER force push unless explicitly asked.
-- Report failures clearly (rejected, auth, permissions).
-
-### Step 6: Summary
-
-List all commits with hashes, types, summaries, and file counts.
-
----
-
-## Phase 2: Pull Request Creation (Conditional)
-
-**Only proceed if the user explicitly requested a PR.**
-
-### Decision Tree
-
-```
-User says "commit" or "push"           -> Phase 1 ONLY, no PR
-User says "commit and push"            -> Phase 1 ONLY, no PR
-User says "commit and create a PR"     -> Phase 1 + Phase 2
-User says "push and open a PR"         -> Phase 1 + Phase 2
-User says "create a PR"                -> Phase 1 + Phase 2
-User says "PR" or "pull request"       -> Phase 1 + Phase 2
-```
-
-If the user did NOT ask for a PR, stop after Phase 1. Do NOT ask "would you like me to create a PR?" — just stop.
-
-### Step PR-1: Determine Base Branch
-
-1. Current branch should NOT be `main` or `master`. If it is, warn: "You are on the main branch. PRs are typically created from feature branches. Proceed anyway?"
-
-2. Find base branch:
-   ```bash
-   git rev-parse --verify origin/main 2>/dev/null && echo "main" || git rev-parse --verify origin/master 2>/dev/null && echo "master"
-   ```
-   If neither exists, ask the user.
-
-3. Check for existing PR: `gh pr list --head <current-branch> --state open`. If PR exists: "A PR already exists for this branch: <url>. New commits have been pushed to it." Stop.
-
-### Step PR-2: Gather PR Information
-
-1. Get full diff: `git log --oneline <base>..HEAD` — ALL commits on this branch, not just new ones.
-
-2. Analyze all commits to understand the full PR scope.
-
-3. Draft PR title:
-   - Under 72 characters
-   - Imperative mood
-   - Specific, not just concatenated commit messages
-
-4. Draft PR body:
-   ```markdown
-   ## Summary
-   <1-3 bullet points: what and why>
-
-   ## Changes
-   <Key changes, grouped logically>
-
-   ## Test plan
-   <Testing steps checklist>
-
-   Generated with [Claude Code](https://claude.ai/code)
-   ```
-
-### Step PR-3: Create the PR
-
-```bash
-gh pr create --title "<title>" --body "$(cat <<'EOF'
-<PR body>
-EOF
-)"
-```
-
-Handle errors:
-- **`gh` not installed**: "Install GitHub CLI: `brew install gh` or https://cli.github.com"
-- **Not authenticated**: "Run `gh auth login`"
-- **No permission**: "You may not have PR access to this repository"
-
-Do NOT add labels, reviewers, or assignees unless asked. Do NOT auto-merge.
-
-### Step PR-4: Final Summary
-
-```
-Committed and pushed to <branch>:
-
-1. <hash> <type>: <summary> (N files)
-2. <hash> <type>: <summary> (N files)
-
-Total: X commits, Y files changed
-
-Pull Request created:
-  Title: <title>
-  URL: <url>
-  Base: <base> <- <branch>
-```
-
-## Edge Cases
-
-| Situation | Action |
-|-----------|--------|
-| On main/master | Warn, ask before creating PR |
-| PR already exists | Report URL, don't create duplicate |
-| `gh` not installed | Provide install instructions |
-| `gh` not authenticated | Tell user to run `gh auth login` |
-| No diff between branch and base | "No differences. Nothing to PR." |
-| Draft PR requested | Use `gh pr create --draft` |
-| Specific reviewers requested | Use `--reviewer` flag |
-| Fork workflow | Use `gh pr create --head <user>:<branch>` |
-
-## Safety Rules
-
-All scancommitpush safety rules apply, plus:
-- **NEVER** create a PR without explicit user request
-- **NEVER** auto-merge PRs
-- **NEVER** force push to create a clean PR
-- **NEVER** modify commit history to make the PR "look better"
-- **NEVER** add labels or reviewers unless asked

package/skills/scancommitpr/package.json

@@ -1,34 +0,0 @@
-{
-  "name": "scancommitpr",
-  "version": "0.1.0",
-  "description": "Instruction-set skill: scan repo changes, group into logical commits, push, and optionally create a PR",
-  "type": "module",
-  "main": "src/index.ts",
-  "bin": {
-    "scancommitpr": "src/index.ts"
-  },
-  "scripts": {
-    "dev": "bun run src/index.ts",
-    "build": "bun build src/index.ts --outdir dist --target node"
-  },
-  "keywords": [
-    "git",
-    "commit",
-    "push",
-    "pull-request",
-    "pr",
-    "automation",
-    "claude-code",
-    "skill"
-  ],
-  "devDependencies": {
-    "@types/bun": "latest"
-  },
-  "peerDependencies": {
-    "typescript": "^5.0.0"
-  },
-  "publishConfig": {
-    "access": "restricted",
-    "registry": "https://registry.npmjs.org/"
-  }
-}

package/skills/scancommitpr/src/index.ts

@@ -1,44 +0,0 @@
-#!/usr/bin/env bun
-
-/**
- * scancommitpr - Instruction-set skill
- *
- * This skill is an instruction set (SKILL.md is the primary artifact).
- * It instructs Claude Code agents to scan, group, commit, push,
- * and optionally create a pull request on GitHub.
- *
- * Install to Claude Code:
- *   skills install scancommitpr --for claude
- */
-
-function printHelp(): void {
-  console.log(`scancommitpr - Scan, Commit, Push & PR
-
-DESCRIPTION:
-  Instruction-set skill for Claude Code agents.
-  When loaded, instructs the agent to:
-    1. Scan the entire repo for changes
-    2. Group changes into logical commits
-    3. Write clear, conventional commit messages
-    4. Push to GitHub
-    5. Optionally create a pull request (only when explicitly asked)
-
-USAGE:
-  This skill is designed to be used as a Claude Code skill (SKILL.md).
-  Install it with:
-
-    skills install scancommitpr --for claude
-
-  The CLI itself has no runtime functionality.
-`);
-}
-
-const args = process.argv.slice(2);
-
-if (args.includes("--help") || args.includes("-h") || args.length === 0) {
-  printHelp();
-  process.exit(0);
-}
-
-console.log("This is an instruction-set skill. Install it to Claude Code with:");
-console.log("  skills install scancommitpr --for claude");

package/skills/scancommitpr/tsconfig.json

@@ -1,13 +0,0 @@
-{
-  "extends": "../tsconfig.base.json",
-  "compilerOptions": {
-    "target": "ESNext",
-    "module": "ESNext",
-    "allowSyntheticDefaultImports": true,
-    "resolveJsonModule": true,
-    "outDir": "./dist",
-    "rootDir": "./src"
-  },
-  "include": ["src/**/*"],
-  "exclude": ["node_modules", "dist"]
-}

package/skills/scancommitpush/SKILL.md

@@ -1,174 +0,0 @@
----
-name: scancommitpush
-description: Scan repo for all changes, group them into logical commits with conventional messages, and push to GitHub. Use when the user says "commit", "push", or invokes /commit. Does NOT create a pull request.
----
-
-# Scan, Commit & Push
-
-Scan the entire repository for changes, group them into logical commits, write high-quality commit messages, and push to GitHub. This skill does NOT create a pull request.
-
-## Step 1: Pre-flight Checks
-
-1. **Verify git repo**: Run `git rev-parse --git-dir`. If not a git repo, stop and inform the user.
-
-2. **Check for merge conflicts**: Run `git diff --name-only --diff-filter=U`. If any files listed, stop: "There are unresolved merge conflicts in: [list]. Please resolve them before committing."
-
-3. **Check current branch**: Run `git branch --show-current`. Note the branch name. If detached HEAD, warn the user and ask whether to proceed.
-
-4. **Check remote**: Run `git remote -v`. If no remote configured, stop: "No git remote configured. Add one before pushing."
-
-5. **Check upstream**: Run `git rev-parse --abbrev-ref @{upstream} 2>/dev/null`. If no upstream, you'll need `git push -u origin <branch>` later.
-
-## Step 2: Scan All Changes
-
-1. **Run `git status`** (never use `-uall` flag). Note staged changes, unstaged modifications, and untracked files.
-
-2. **Run `git diff --stat`** for unstaged modification summary.
-
-3. **Run `git diff --cached --stat`** for staged change summary.
-
-4. **If NO changes exist** (nothing staged, unstaged, or untracked): "Working tree is clean. Nothing to commit." Stop.
-
-5. **Detect sensitive files** and EXCLUDE from commits:
-   - `.env`, `.env.*` (environment files)
-   - `*.pem`, `*.key`, `*.p12` (private keys)
-   - `credentials.json`, `service-account*.json`
-   - `.secrets/`, `secrets/`
-   - Files containing API keys or tokens
-
-   Warn: "Found potentially sensitive files that will NOT be committed: [list]. Add them to .gitignore if needed."
-
-## Step 3: Group Changes into Logical Commits
-
-Do NOT create one giant commit. Analyze changes and group them into logical, atomic commits.
-
-### Grouping Rules (in priority order)
-
-1. **By feature/functionality**: Changes implementing a single feature or fixing a single bug go together.
-   - Files that import or reference each other
-   - Files in the same directory working toward the same goal
-   - Test files paired with the code they test
-
-2. **By type of change**:
-   - Configuration changes (package.json, tsconfig, eslint) → own commit
-   - Documentation changes (README, CHANGELOG) → own commit
-   - Dependency updates (lockfiles + package.json) → one commit
-   - Refactoring (rename, restructure without behavior change) → separate from features
-   - Test additions paired with the code they test → together
-
-3. **By scope/area**: Changes in unrelated parts of the codebase → separate commits.
-
-4. **Single-file changes**: A lone modified file unrelated to others → own commit.
-
-### Decision Process
-
-For each changed file ask:
-- What is the purpose of this change? (feature, fix, refactor, docs, config, test)
-- Which other files does this change relate to?
-- Would this change make sense on its own?
-
-**When in doubt, split into smaller commits.** Small atomic commits are always better than large unfocused ones.
-
-### Special Cases
-
-- **Lockfiles** (package-lock.json, bun.lockb, yarn.lock, pnpm-lock.yaml): Always group with corresponding package.json change
-- **Generated files**: Group with the source change that produced them, or skip if they belong in .gitignore
-- **Already staged changes**: Respect the user's intent — commit staged files as one group, then handle remaining changes separately
-- **Untracked files**: New source files → commit. Build artifacts, logs, editor configs → suggest .gitignore
-
-## Step 4: Create Commits
-
-For each logical group, commit in dependency order (foundational changes first):
-
-1. **Stage files**: `git add <file1> <file2> ...` — use specific paths, NEVER `git add .` or `git add -A`.
-
-2. **Write commit message**:
-
-   ```
-   <type>: <concise summary in imperative mood>
-
-   <optional body explaining WHY, not WHAT>
-
-   Co-Authored-By: Claude <noreply@anthropic.com>
-   ```
-
-   | Type | When |
-   |------|------|
-   | `feat` | New feature or capability |
-   | `fix` | Bug fix |
-   | `refactor` | Code restructuring, no behavior change |
-   | `docs` | Documentation only |
-   | `test` | Adding or updating tests |
-   | `chore` | Config, dependencies, build, CI |
-   | `style` | Formatting, whitespace, linting |
-   | `perf` | Performance improvement |
-
-   Rules:
-   - Subject line max 72 chars, imperative mood ("Add feature" not "Added")
-   - No period at end of subject
-   - Be specific: "fix: resolve null pointer in user auth" not "fix: fix bug"
-
-3. **Create commit** using HEREDOC:
-   ```bash
-   git commit -m "$(cat <<'EOF'
-   <type>: <summary>
-
-   <optional body>
-
-   Co-Authored-By: Claude <noreply@anthropic.com>
-   EOF
-   )"
-   ```
-
-4. **Verify**: `git log --oneline -1` to confirm.
-
-5. **Repeat** for each group.
-
-## Step 5: Push to Remote
-
-1. If no upstream: `git push -u origin <branch>`. Otherwise: `git push`.
-
-2. **Handle failures**:
-   - **Rejected (non-fast-forward)**: "Push rejected — remote has new commits. You may need to pull and rebase first." Do NOT force-push.
-   - **Auth failure**: "Check your Git credentials."
-   - **No permission**: "You may not have push access to this repository."
-
-3. **NEVER force push** unless the user explicitly requests it.
-
-## Step 6: Summary
-
-```
-Committed and pushed to <branch>:
-
-1. <hash> <type>: <summary> (N files)
-2. <hash> <type>: <summary> (N files)
-...
-
-Total: X commits, Y files changed
-Remote: origin/<branch>
-```
-
-## Edge Cases
-
-| Situation | Action |
-|-----------|--------|
-| No changes | "Working tree is clean. Nothing to commit." Stop. |
-| Only staged changes | Commit staged as-is, push |
-| Only untracked files | Evaluate each, stage appropriate ones, commit, push |
-| Hundreds of files | Still group logically, create more commits |
-| Binary files | Include in commit, note in summary |
-| Submodule changes | Commit pointer update separately |
-| Pre-commit hook fails | Report failure, do NOT use --no-verify. Fix the issue, create NEW commit. |
-| Branch behind remote | Warn, suggest pull/rebase |
-| Detached HEAD | Warn, ask before proceeding |
-| Empty commit would result | Skip that group, no --allow-empty |
-
-## Safety Rules
-
-- **NEVER** `git add .` or `git add -A` — always stage specific files
-- **NEVER** `--no-verify` to skip hooks
-- **NEVER** force push without explicit user request
-- **NEVER** commit .env files or secrets
-- **NEVER** amend existing commits unless user explicitly asks
-- **NEVER** rebase or modify published history
-- If pre-commit hook fails, fix the issue and create a NEW commit

package/skills/scancommitpush/package.json

@@ -1,32 +0,0 @@
-{
-  "name": "scancommitpush",
-  "version": "0.1.0",
-  "description": "Instruction-set skill: scan repo changes, group into logical commits, and push to GitHub",
-  "type": "module",
-  "main": "src/index.ts",
-  "bin": {
-    "scancommitpush": "src/index.ts"
-  },
-  "scripts": {
-    "dev": "bun run src/index.ts",
-    "build": "bun build src/index.ts --outdir dist --target node"
-  },
-  "keywords": [
-    "git",
-    "commit",
-    "push",
-    "automation",
-    "claude-code",
-    "skill"
-  ],
-  "devDependencies": {
-    "@types/bun": "latest"
-  },
-  "peerDependencies": {
-    "typescript": "^5.0.0"
-  },
-  "publishConfig": {
-    "access": "restricted",
-    "registry": "https://registry.npmjs.org/"
-  }
-}

package/skills/scancommitpush/src/index.ts

@@ -1,44 +0,0 @@
-#!/usr/bin/env bun
-
-/**
- * scancommitpush - Instruction-set skill
- *
- * This skill is an instruction set (SKILL.md is the primary artifact).
- * It instructs Claude Code agents to scan, group, commit, and push changes.
- *
- * Install to Claude Code:
- *   skills install scancommitpush --for claude
- */
-
-function printHelp(): void {
-  console.log(`scancommitpush - Scan, Commit & Push
-
-DESCRIPTION:
-  Instruction-set skill for Claude Code agents.
-  When loaded, instructs the agent to:
-    1. Scan the entire repo for changes
-    2. Group changes into logical commits
-    3. Write clear, conventional commit messages
-    4. Push to GitHub
-
-  This skill does NOT create a pull request.
-
-USAGE:
-  This skill is designed to be used as a Claude Code skill (SKILL.md).
-  Install it with:
-
-    skills install scancommitpush --for claude
-
-  The CLI itself has no runtime functionality.
-`);
-}
-
-const args = process.argv.slice(2);
-
-if (args.includes("--help") || args.includes("-h") || args.length === 0) {
-  printHelp();
-  process.exit(0);
-}
-
-console.log("This is an instruction-set skill. Install it to Claude Code with:");
-console.log("  skills install scancommitpush --for claude");

package/skills/scancommitpush/tsconfig.json

@@ -1,13 +0,0 @@
-{
-  "extends": "../tsconfig.base.json",
-  "compilerOptions": {
-    "target": "ESNext",
-    "module": "ESNext",
-    "allowSyntheticDefaultImports": true,
-    "resolveJsonModule": true,
-    "outDir": "./dist",
-    "rootDir": "./src"
-  },
-  "include": ["src/**/*"],
-  "exclude": ["node_modules", "dist"]
-}

package/skills/scientific-figure-check/CLAUDE.md

@@ -1,19 +0,0 @@
-# scientific-figure-check
-
-Scientific Figure Check skill.
-
-## Tech Stack
-
-- Runtime: Bun
-- Language: TypeScript
-- CLI: Commander.js
-
-## CLI
-
-```bash
-scientific-figure-check run
-```
-
-## Data Directory
-
-~/.skill/scientific-figure-check/

package/skills/scientific-figure-check/package.json

@@ -1,29 +0,0 @@
-{
-  "name": "scientific-figure-check",
-  "version": "0.1.0",
-  "description": "Scientific Figure Check skill",
-  "type": "module",
-  "bin": {
-    "scientific-figure-check": "./src/index.ts"
-  },
-  "scripts": {
-    "dev": "bun run src/index.ts",
-    "build": "bun build src/index.ts --outdir dist --target node",
-    "typecheck": "tsc --noEmit"
-  },
-  "dependencies": {
-    "image-size": "^2.0.2"
-  },
-  "devDependencies": {
-    "@types/bun": "latest",
-    "typescript": "^5.7.0"
-  },
-  "publishConfig": {
-    "access": "restricted",
-    "registry": "https://registry.npmjs.org/"
-  },
-  "files": [
-    "src",
-    "tsconfig.json"
-  ]
-}

package/skills/scientific-figure-check/src/index.ts

@@ -1,83 +0,0 @@
-#!/usr/bin/env bun
-import { parseArgs } from "util";
-import { existsSync, statSync } from "fs";
-import sizeOf from "image-size";
-
-const { values, positionals } = parseArgs({
-  args: process.argv.slice(2),
-  options: {
-    help: { type: "boolean" },
-  },
-  allowPositionals: true,
-});
-
-if (values.help || positionals.length === 0) {
-  console.log(`
-Scientific Figure Check
-Usage: skills run scientific-figure-check -- <file>
-
-Description:
-  Analyzes image files to check if they meet common journal submission standards.
-`);
-  process.exit(0);
-}
-
-const filePath = positionals[0];
-
-if (!existsSync(filePath)) {
-  console.error(`Error: File not found: ${filePath}`);
-  process.exit(1);
-}
-
-try {
-  const stats = statSync(filePath);
-  const dimensions = sizeOf(filePath);
-  
-  const fileSizeMB = stats.size / (1024 * 1024);
-  const width = dimensions.width || 0;
-  const height = dimensions.height || 0;
-  const type = dimensions.type || "unknown";
-
-  // Heuristics for "Print Quality" (assuming 300 DPI target)
-  // If we don't know physical size, we can only guess based on pixel count.
-  // A 3-inch wide figure at 300 DPI needs 900 pixels.
-  const minWidth = 900; 
-  const minHeight = 900;
-
-  console.log(`
-Figure Analysis Report
-----------------------
-File:   ${filePath}
-Type:   ${type.toUpperCase()}
-Size:   ${fileSizeMB.toFixed(2)} MB
-Pixels: ${width} x ${height}
-
-Checks:
-`);
-
-  // Check Format
-  const validFormats = ["png", "jpg", "jpeg", "tiff", "eps", "pdf"];
-  if (validFormats.includes(type.toLowerCase())) {
-    console.log(`[PASS] Format (${type}) is generally accepted.`);
-  } else {
-    console.log(`[WARN] Format (${type}) might not be accepted. Prefer TIFF, EPS, or high-res PDF/PNG.`);
-  }
-
-  // Check Resolution (Heuristic)
-  if (width >= minWidth && height >= minHeight) {
-    console.log(`[PASS] Dimensions are likely sufficient for print (>3 inches at 300 DPI).`);
-  } else {
-    console.log(`[WARN] Dimensions are small (${width}x${height}). Ensure this provides 300 DPI at print size.`);
-  }
-
-  // Check File Size
-  if (fileSizeMB > 10) {
-    console.log(`[WARN] File size is large (${fileSizeMB.toFixed(2)} MB). Check journal limits.`);
-  } else {
-    console.log(`[PASS] File size is reasonable.`);
-  }
-
-} catch (error) {
-  console.error("Error analyzing image:", error);
-  process.exit(1);
-}

package/skills/scientific-figure-check/tsconfig.json

@@ -1,10 +0,0 @@
-{
-  "extends": "../tsconfig.base.json",
-  "compilerOptions": {
-    "outDir": "dist"
-  },
-  "include": [
-    "src/**/*",
-    "bin/**/*"
-  ]
-}