Skip to main content
GitHub repository

Sharevalue_claude_skills

Sharevalue_claude_skills contains 7 collected skills from amurthygithub, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
7
Stars
1
updated
2026-06-01
Forks
0
Occupation coverage
2 occupation categories · 100% classified
repository explorer

Skills in this repository

agentreview
software-quality-assurance-analysts-and-testers

Four-agent consensus review of a PR (correctness / security / observability / style). 3-of-4 APPROVE = ship. Posts a single structured comment. Orchestrator on a larger model, sub-agents on a smaller model.

2026-06-01
handoff
software-developers

Snapshot the active ticket session (done / tried-and-failed / next step + git state) into a gitignored .claude/handoff-notes.md so a fresh agent resumes without re-walking dead ends.

2026-06-01
linear
software-developers

CLI for <TRACKER> ticket operations (create epic / story / task, update status, show, list) — no committed secrets, reads $<TRACKER>_API_KEY from env. The most-replaceable skill in this template — swap the API layer for any tracker.

2026-06-01
promote
software-developers

Promote <STAGING_BRANCH> → <DEFAULT_BRANCH> (production). USER-INVOKED ONLY. Opens a promote PR, posts a "promotion ready" digest, and waits for the user's explicit confirmation before merging. Tags + drafts a release on merge.

2026-06-01
ship
software-developers

Ship the current feature branch to <STAGING_BRANCH> — commit any uncommitted changes, push (triggers pre-push hook + agent review), open PR if missing, wait for consensus, merge to <STAGING_BRANCH> unless blockers or danger-zone hits.

2026-06-01
triage-review
software-quality-assurance-analysts-and-testers

Classify the latest /agentreview consensus comment via a 3-agent council (Cost / Correctness / Risk lenses). Prints a report sorting each finding into fix / skip / false-positive / human-required. Read-only — no Edit, no push, no tracker write.

2026-06-01
work-on
software-developers

Start work on a <TRACKER> ticket — fetch its details, branch off <STAGING_BRANCH> with a conventional name, acquire a per-branch lock, set status to In Progress, and load context into a file the user's session can read.

2026-06-01