Skip to content
cccskills

Development skills

Coding standards, frameworks, refactoring, and code review (18.4K skills)

Filter by price or sort order

sol-loop

FreeSummary

Review code changes with GPT Sol in a controlled loop before or after opening a pull request. Track findings by severity, make minimal fixes, rerun checks, and continue only while meaningful issues remain, so the review stays focused on the requested change.

  • Reviewing a code change before opening a pull request
  • Checking fixes against findings from an earlier review
  • Keeping a security or permissions review focused
t3dotgg/tstack1.8KUpdated Oct 27, 2026

full-stop

FreeSummary

Take a requested change through implementation, proof, review, and pull request readiness, then hand it back without merging. It follows the full-send workflow for testing and review, checks the live pull request state, and reports whether it is ready, awaiting approval, or blocked.

  • Preparing a pull request for the user to merge
  • Verifying a change and addressing review findings
  • Checking why a pull request is not yet ready
t3dotgg/tstack1.8KUpdated Oct 27, 2026

council

FreeSummary

Get parallel feedback on a request from three delegates using models from different providers. The skill gathers their findings, summarizes agreements and disagreements, and suggests next steps; code reviews also include a score from each delegate.

  • Getting several perspectives on a proposed change
  • Reviewing code with three model providers
  • Summarizing reviewer disagreements before deciding next steps
t3dotgg/tstack1.8KUpdated Oct 27, 2026

Format comments posted on GitHub on the user’s behalf with clear attribution, then review the full Markdown for private details before posting. The skill covers PR comments, inline reviews, replies, and explanations for resolving feedback.

  • Writing a reply to a pull request review
  • Adding an inline code review comment
  • Explaining why a bot finding is dismissed
t3dotgg/tstack1.8KUpdated Oct 27, 2026

file-pr

FreeSummary

Prepare and open a concise pull request by checking for an existing PR, reviewing the branch diff, and writing a clear title and problem-focused description. The skill also checks the submission text and attachments for secrets or private details.

  • Opening a pull request for completed work
  • Checking whether a branch already has a PR
  • Writing a clear PR title and description
t3dotgg/tstack1.8KUpdated Oct 27, 2026

full-send

FreeSummary

Carry a requested code change from implementation through direct proof, review, pull request updates, and merge when the required checks pass. The workflow also tracks review findings and asks the user only when progress is blocked or a decision is outside its permission.

  • Completing a code change through merge
  • Running checks and gathering evidence for a fix
  • Handling review feedback and CI failures on a pull request
t3dotgg/tstack1.8KUpdated Oct 27, 2026

takeover

FreeSummary

Take responsibility for finishing an existing PR, branch, or agent task. Review its history, current code, feedback, and uncommitted work, then make focused changes, verify realistic workflows, and preserve the original contributors’ credit.

  • Taking over an unfinished pull request
  • Continuing work on an existing branch
  • Resuming a task from another agent thread
t3dotgg/tstack1.8KUpdated Oct 27, 2026

modernize

FreeSummary

Review an older pull request against the current codebase, decide whether its goal still fits, and recommend modernization, rework, or closure. For useful changes, rebase the branch onto its latest base and report conflicts, checks, and results.

  • Checking whether an old pull request is still useful
  • Rebasing a pull request onto the latest base branch
  • Finding whether newer code superseded a proposed change
t3dotgg/tstack1.8KUpdated Oct 27, 2026

setup-serena-mcp

FreeSummary

Guides you through setting up the Serena MCP server for a chosen project or user scope. It helps identify your client, check prerequisites, configure the connection, initialize project indexing, and verify that Serena tools are available.

  • Setting up Serena for a project or user account
  • Configuring Serena for Claude Code, Cursor, or another MCP client
  • Initializing project indexing and checking the connection
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

Trace a bug backward through its callers to find where invalid data or behavior first originated. The skill suggests adding logs and stack traces when needed, then fixing the source and adding checks at relevant layers.

  • Tracing an error through a long call stack
  • Finding which test or input triggers a bug
  • Locating the source of invalid data
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

Set up Codemap CLI for a project or user account, install it, verify it, and add configuration guidance and hooks. Codemap presents codebase structure, dependencies, and changes to help agents navigate a project.

  • Set up Codemap for a shared project
  • Install Codemap for personal use
  • Add hooks that show codebase context at session start
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

why

FreeSummary

Trace a problem from its visible symptoms to underlying technical or process causes by asking “why” in repeated steps. The skill helps validate causes by working backward, explore multiple branches, and suggest solutions that address the root cause.

  • Investigating recurring production errors
  • Finding causes of flaky CI/CD runs
  • Tracing delays in feature deployment
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

Delegate independent implementation tasks or investigations to separate agents, then review their results at checkpoints. The workflow supports sequential work for related tasks and parallel work for unrelated problems, with verification and integration steps to catch issues.

  • Implementing a multi-step plan with separate tasks
  • Investigating unrelated failures in parallel
  • Reviewing agent changes before continuing
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

traiage-review

FreeSummary

Prioritize changed repository files for human review by combining agent assessments of the change story, impact, failure risks, and expectations. It produces a focused file list, key facts, a random sample of changed files, and declarative files for review.

  • Prioritizing files in a code review
  • Reviewing staged and unstaged changes
  • Checking a branch diff or a specific commit
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

Set up Context7 MCP and add relevant documentation library IDs to the appropriate CLAUDE.md file. Choose project-shared, project-local, or user-wide configuration, and identify technologies from the supplied input or project structure when needed.

  • Set up Context7 MCP for a project
  • Choose shared, local, or global configuration
  • Add documentation library IDs to CLAUDE.md
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

analyze-issue

FreeSummary

Analyze a GitHub issue and the related project code, then create a structured technical specification covering the problem, proposed approach, implementation and test plans, affected files, and success criteria.

  • Turn a reported GitHub issue into an implementation plan
  • Understand which files and utilities a change may involve
  • Define test scenarios and success criteria before coding
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

actualize

FreeSummary

Compare recent Git changes with the project’s FPF knowledge base to find context drift, evidence tied to changed files, and decisions that may need review. The skill reports findings and updates the baseline commit for the next audit.

  • Checking the knowledge base before starting new work
  • Finding evidence affected by recent code changes
  • Reviewing project decisions after configuration changes
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

kaizen

FreeSummary

Applies an incremental approach to coding, refactoring, system design, and workflow changes. It encourages error prevention through types and early validation, consistency with existing project patterns, and solutions sized to current needs instead of speculative complexity.

  • Making a small, focused improvement during implementation
  • Designing validation and error handling to catch problems early
  • Refactoring while keeping existing project conventions
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

load-pr-comments

FreeSummary

Load unresolved review threads from a GitHub pull request and turn them into focused Markdown task files under `.specs/comments/`. Group related feedback without duplicating work, preserve actionable suggestions, and leave GitHub comments and PRs unchanged.

  • Turning unresolved PR feedback into implementation tasks
  • Grouping review comments for parallel work
  • Keeping resolved threads out of a review task list
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

create-hook

FreeSummary

Analyze a project’s tools and settings, suggest suitable Claude Code hooks, then configure and validate them. Hooks are commands triggered by events such as file edits or before tool use; examples include formatting code, running checks, and blocking sensitive edits.

  • Suggesting hooks for a project’s tools
  • Running checks after code edits
  • Blocking changes to protected files
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

commit

FreeSummary

Review staged changes and create concise commits using emoji paired with Conventional Commit types such as feat, fix, and docs. The workflow can run project checks, suggest splitting unrelated changes, and follow a branch naming pattern when starting from the main branch.

  • Writing a commit message that matches code changes
  • Splitting unrelated changes into separate commits
  • Running pre-commit checks before committing
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

critique

FreeSummary

Review completed work from requirements, architecture, and code quality perspectives. Specialized judges assess it independently, verify their findings, and compare disagreements before producing an evidence-based report with prioritized issues and recommendations. The review does not change files.

  • Reviewing recent implementation work
  • Checking changes against the original request
  • Getting prioritized code improvement suggestions
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

git-worktrees

FreeSummary

Work on several Git branches in separate directories using Git worktrees. The skill covers creating and cleaning up worktrees, reviewing pull requests without interrupting current work, running isolated tests, and comparing or selectively combining changes.

  • Reviewing a pull request while feature work continues
  • Testing changes in an isolated directory
  • Comparing implementations across branches
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026

create-rule

FreeSummary

Turn recurring agent mistakes or behavior gaps into focused `.claude/rules` files. The guidance uses incorrect and correct examples to make expectations clear, and helps distinguish always-on rules from task-specific skills or broad project notes.

  • Documenting a mistake an agent keeps repeating
  • Adding a project-wide behavior constraint
  • Scoping guidance to particular file paths
NeoLabHQ/context-engineering-kit1.8KUpdated Aug 27, 2026