All categories
Documentation
Docs, README files, API references, tutorials, specs, and changelogs
- 14,027
- 585
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse documentation skills
Showing 409–432 of 14,027 skills
- Praxis SyncUpdate local tracking files from the provider, git diff, code TODOs, and linked resources. Use when the user invokes "/praxis-sync" with or without a ticket ID. Analyzes code changes to update progression and advancement.Votes: 0GitHub stars: 3
- Praxis StartSet the active ticket and prepare the git environment. Use when the user invokes "/praxis-start" followed by a ticket ID (e.g., /praxis-start KEY-30636). Updates .current, syncs from the provider, creates a worktree or classic branch (user's choice), and displays ticket status.Votes: 0GitHub stars: 3
- Praxis NewInitialize local tracking for an epic and all its child tickets. Use when the user invokes "/praxis-new" followed by an epic ID (e.g., /praxis-new KEY-30635). Fetches the epic and its children via the configured provider, creates a folder with one markdown file per ticket + an epic summary file.Votes: 0GitHub stars: 3
- Praxis ListList all tracked epics and tickets with their status. Use when the user invokes "/praxis-list" to see an overview of all tracked work or switch context between epics.Votes: 0GitHub stars: 3
- Praxis CaptureCapture an implementation decision or spec correction into the active ticket's tracking file. Use when the user invokes "/praxis-capture" to record decisions that deviate from or complement original specs. Optionally posts to the provider.Votes: 0GitHub stars: 3
- Component DocsGenerate or update component documentation with usage examples, props tables, and Storybook stories. Use when documenting new components or improving existing component docs.Votes: 0GitHub stars: 2
- Compliance ReviewThis skill should be used when the user asks to "check CLAUDE.md compliance", "review against coding standards", "check AI agent instructions", "verify guidelines", "check coding conventions", "check naming conventions", or wants to ensure code follows project-specific rules and standards.Votes: 0GitHub stars: 2
- Communication DraftDraft personalized follow-up communications (email, call script, SMS) based on account context and history.Votes: 0GitHub stars: 2
- CommittingGuidelines for git commit messagesVotes: 0GitHub stars: 2
- CommitsQuick commit and push following Conventional CommitsVotes: 0GitHub stars: 2
- Commit Style EnforcerGenerates properly formatted commit messages following project conventions. Use when creating commits or when users need help writing commit messages. Inspects staged changes and creates messages with component tags, concise summaries, and detailed descriptions.Votes: 0GitHub stars: 2
- Commit StandardsFormat commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, feat, fix, refactor.Votes: 0GitHub stars: 2
- Commit Message HelperHelps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, or mentions git commits.Votes: 0GitHub stars: 2
- Commit Message Helper 1Helps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, or mentions git commits.Votes: 0GitHub stars: 2
- Commit Message GeneratorAutomatically generate conventional commit messages when user has staged changes and mentions committing. Analyzes git diff and status to create properly formatted commit messages following conventional commits specification. Invoke when user mentions "commit", "staged", "committing", or asks for help with commit messages.Votes: 0GitHub stars: 2
- Commit Message 8Generate Git commit messages from staged changes using a conventional commit subject (English, <= 72 chars) and a Korean body (wrapped at 72 chars). Use when asked to write, suggest, or refine a git commit message.Votes: 0GitHub stars: 2
- Commit Message 7Create git commit messages based on current staged changes. Has support for git emoji messages.Votes: 0GitHub stars: 2
- Commit Message 2Generate a conventional commit message from staged git changes. Use this skill when the user wants to create a commit message for their staged changes.Votes: 0GitHub stars: 2
- Commit Helper 2Manage git commit workflow with size limits and conventional commits. Use before any commit. Enforces max_commit_change_lines policy. NOTE: CHANGELOG is updated only during merge, not during individual commits.Votes: 0GitHub stars: 2
- Commit FormatEnsures all git commits follow the Conventional Commits specification with consistent types and scopes. Use this skill when making any commit to maintain consistent commit message format, improve git history readability, and enable automatic changelog generation.Votes: 0GitHub stars: 2
- Commit DetectionDetects optimal commit type from git changes. Use when analyzing commits, determining commit type, or before committing.Votes: 0GitHub stars: 2
- Commit 8Smart commit and push with auto-splitting across domains. Creates atomic commits. Use when asked to "commit", "push changes", "save my work", or after completing implementation work. Automatically groups changes into logical commits.Votes: 0GitHub stars: 2
- Commit 71Enforces Conventional Commits 1.0.0 for all git commit messages.Votes: 0GitHub stars: 2
- Commit 7Smart commit creation with conventional commits, emoji, and GPG signing. Use when user says "commit" or requests committing changes. Handles staged file detection, suggests splits for multi-concern changes, and applies proper commit format.Votes: 0GitHub stars: 2