commit-operations
View and analyze commits in GitHub repositories - commit history, diffs, and commit details using gh CLI
আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
View and analyze commits in GitHub repositories - commit history, diffs, and commit details using gh CLI
Review and improve repository documentation including both human-readable docs (`docs/`), `README.md`, and AI agent memory context files (`CLAUDE.md`, `CODEX.md`, `AGENTS.md`, `.cursorrules`, etc.) for clarity, minimal duplication, and modularity. Use when asked to review, audit, refactor, or improve documentation structure, consolidate rules, reduce redundancy, establish shared standards, or modularize monolithic instruction files.
This skill should be used when the user asks about "snapshot.md", "constraints.md", "decisions.md", "debt.md", ".ctx/", "living context", "documentation freshness", "stale docs", "ADR", "architecture decision", "technical debt", "system context", "co-located documentation", "context health", "validation", or needs help managing co-located documentation that stays synchronized with code.
Pick up and implement the next available feature from /.agent-features/. Use when user says "develop feature", "work on next feature", "implement feature", or starts a new session to continue feature-driven development. Handles the full cycle from implementation through code review to commit.
Generates conventional commit messages. Use when creating git commits or reviewing staged changes. Ensures NO AI attribution in commits.
Remove AI-generated code slop from a branch. Use to delete unnecessary comments/docs, defensive checks, broad try/catch blocks, type-cast hacks, lint suppressions, dead code, duplication, and style drift. Diff against base (main/master) and align changes with existing project idioms without altering intended behavior.
Set up btca (Better Context) in a project by scanning dependencies, proposing resources, creating btca.config.jsonc, updating AGENTS.md, and explaining usage modes. Use when asked to configure btca/better-context for a repo.
Manage the PR review feedback loop: monitor CI checks, fetch review comments, and iterate on fixes. Use when: (1) pushing changes to a PR and waiting for CI/reviews, (2) user says "new reviews available", (3) iterating on PR feedback from Gemini, Cursor, Claude, or other reviewers, (4) monitoring PR status. Supports multiple review bots: Gemini Code Assist, Cursor Bugbot, and Claude agent fallback. Automatically detects priority levels from different bot formats and handles rate limits. RECOMMENDED: Spawn a Task agent (subagent_type: general-purpose) to execute the review loop autonomously. See "Recommended Usage: Run as Task Agent" section for the prompt template. CRITICAL: When using this skill, NEVER use raw git commit/push commands. ALWAYS use commit-and-push.sh script. The user has NOT granted permission for raw git commands - only the script is allowed.
Use when creating or updating CLAUDE.md files for projects or subdirectories - covers top-level vs domain-level organization, capturing architectural intent and contracts, and mandatory freshness dates
Dotfiles management best practices for XDG-compliant, cross-platform, and maintainable configurations. Use when adding new config files to dotfiles, refactoring existing configurations, improving setup scripts, or ensuring security with sensitive data separation. Covers automation (Makefile, CI/CD), maintainability (modularity, documentation), and security (.local pattern).
⚠️ MANDATORY - Automatically invoked by safe-commit. Runs language-specific linting, formatting, static analysis, and type checking. Treats linter issues as build failures that MUST be fixed before commit. Auto-fixes when possible. NEVER run linters manually.
Commit and push changes to GitHub with proper messages. Use when ready to save changes, push to production, or deploy updates to GitHub Pages.
Analisa as issues do GitHub e as classifica por dificuldade.
Reviews code changes for correctness, security, and maintainability with actionable feedback. Triggers on: review this code, code review, check this PR, review my changes.
Git workflows, branching strategies, and commit conventions
Skill for recording changes to the local repository. Typical use cases include (1) Committing product code and tests after completing a feature or bug fix, (2) Recording structural changes such as architecture updates or ADR drafting, and (3) Staging and committing multiple small maintenance changes or documentation updates.
[DEPRECATED] Worktree CLI is now available via npm - no setup needed
Clean up after an issue PR is merged. Merges the PR if needed, removes the worktree, deletes the branch, updates main, and starts a fresh session. Use when asked to clean up an issue, finish an issue, or after a PR is approved.