8000 GitHub - alexanderguy/skills: Human and Agent Skills · GitHub
[go: up one dir, main page]

Skip to content
alexanderguyPublic

About

Human and Agent Skills

Resources

Stars

5 stars

Watchers

0 watching

Forks

Latest commit

 

History

182 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 

Repository files navigation

alexanderguy-skills - Claude Code Plugin

Development skills for code review and coding conventions.

Installation

Local Development

claude --plugin-dir /path/to/this/repo

From Git Repository

# In Claude Code
/plugin marketplace add alexanderguy/agent-marketplace
/plugin install alexanderguy-skills@agent-plugins

Skills

linear-create

Create well-structured Linear issues, projects, or initiatives. This skill:

  • Analyzes scope to determine the appropriate artifact type
  • Interviews for missing information (problem, acceptance criteria, goals)
  • Drafts content following conventions (verb phrase titles, checkbox acceptance criteria)
  • Breaks down large features into properly-sized issues with dependencies
  • Creates artifacts in Linear with proper linking and relationships

linear-issue-workflow

Structured workflow for implementing features or fixes tracked in Linear. Includes:

  • Fetching issue details and acceptance criteria
  • Creating implementation plans with user approval
  • Setting up git worktrees for isolated work
  • Self-review before pushing
  • PR creation with proper Linear issue linking

pull-request-review

Review a pull request by branch name or URL. This skill:

  • Accepts a branch name or GitHub/GitLab PR/MR URL
  • Creates a git worktree at ../worktree/<branch-name> relative to repo root
  • Loads the code-review skill to perform the actual review
  • Keeps the worktree available for further investigation after review

dispatch

Orchestrate parallel subagent execution with DAG-based scheduling. This skill:

  • Breaks goals into tasks with dependency edges, fans out to parallel subagents
  • Validates plans before executing, critiques results before accepting
  • Runs quality gates (build, test, lint) with iterative fix loops and escalation
  • Orchestrates commits after verification with configurable strategy and approval
  • Supports resumability from dispatch.yaml state

implement

Disciplined per-commit workflow for standalone implementation work. Each commit goes through:

  • Greybeard architectural review before coding
  • Build gate (full pipeline: format, lint, build, test)
  • Critique loop with iterative fixes until clean
  • Commit following style conventions

Standalone skill loaded on request. Not part of dispatch.

bug-triage

Validate a filed bug against the source before fixing it. This skill:

  • Treats the report as a hypothesis and the code as the truth
  • Verifies every load-bearing claim with an adversarial, file:line-backed reader
  • Hunts the broader class of the same defect, then verifies the promoted siblings
  • Traces the contract/design question the ticket never asked
  • Stress-tests the proposed fix for relocation, version skew, and adjacent bugs
  • Splits the outcome into a tiny correctness fix plus an orthogonal robustness fix

code-review

Guidance for performing code reviews and pull request reviews. Includes:

  • Scope determination using git diff
  • Handling pre-existing code (exempt from review)
  • Delegating to sub-agents with proper context
  • Test coverage philosophy (focus on business logic, trust libraries)
  • Review checklist

style

General coding conventions that apply to any language:

  • Documentation guidelines (avoiding redundant comments)
  • Git commit message format
  • Code reuse and refactoring (search before implementing, prompt with options)
  • Build verification (full build before declaring complete)
  • Configuration files (don't modify unless asked)
  • Personality (no emojis, act professionally)

philosophy

Engineering philosophy and work culture principles. Load this skill when making architectural decisions or to understand the team's work principles.

  • Guiding principles (pragmatic over idealistic, do no harm, benevolent dictatorship)
  • Collaboration and communication culture (public discussion, respect, learning from others)
  • Testing philosophy (tests as friends, safe refactoring)
  • Automation timing and tool-building (automate by the third time)
  • Business context (engineering/sales symbiotic relationship)
  • Issue management (self-contained, 2-3 day sizing, status updates)

typescript

TypeScript-specific conventions and type system patterns:

  • Naming conventions (files, types, functions, variables, acronyms)
  • Type system patterns (runtime validation, type guards, generics)
  • Async patterns (factory functions, parallel execution, timeouts, retries)
  • Import/export patterns (barrel exports, named exports, import ordering)
  • Error handling idioms
  • Testing patterns
  • TSDoc documentation

Customization

These skills provide general guidance. For project-specific conventions:

  1. Create a project-level CLAUDE.md or .claude/settings.json with overrides
  2. Reference specific conventions that differ from these defaults
  3. The project-level instructions take precedence

License

MIT

About

Human and Agent Skills

Resources

Stars

5 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

0