🔌
QualityPython

Completion Check

by parcadei

Completion Check is a Quality skill for Claude Code, published by parcadei in Continuous-Claude-v3.

3.9K stars296 forkson parcadei/Continuous-Claude-v3Added 2026/08/16Repository updated 2026/01/26
agentsclaude-codeclaude-code-cliclaude-code-hooksclaude-code-mcpclaude-code-skillsclaude-code-subagentsclaude-skillsmcp
Install in seconds
Install Completion Check
Copy Completion Check into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/completion-check ~/.claude/skills/completion-check

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/parcadei/Continuous-Claude-v3.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
.claude/skills/completion-check/SKILL.md in parcadei/Continuous-Claude-v3
Installs to
~/.claude/skills/completion-check
Collection
One of 25 skills cataloged from this repository
Category
Quality1354 skills

What Completion Check does

Completion Check verifies that infrastructure code is actually connected and invoked before marking work complete. Use it to trace execution paths, confirm hooks and database backends are registered, and run end-to-end tests.

Completion Check is cataloged under Quality on DirSkills. Completion Check comes from a repository tagged agents, claude-code, claude-code-cli, claude-code-hooks and claude-code-mcp.

Documentation

README

Completion Check: Verify Infrastructure Is Wired

When building infrastructure, verify it's actually connected to the system before marking as complete.

Pattern

Infrastructure is not done when the code is written - it's done when it's wired into the system and actively used. Dead code (built but never called) is wasted effort.

DO

  1. Trace the execution path - Follow from user intent to actual code execution:

    # Example: Verify Task tool spawns correctly
    grep -r "claude -p" src/
    grep -r "Task(" src/
    
  2. Check hooks are registered, not just implemented:

    # Hook exists?
    ls -la .claude/hooks/my-hook.sh
    
    # Hook registered in settings?
    grep "my-hook" .claude/settings.json
    

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Completion Check

  • What else does parcadei publish alongside Completion Check?

    Completion Check is one of 25 skills that DirSkills catalogs from parcadei/Continuous-Claude-v3, the repository it ships in. Its siblings there include AST-Grep Find, Agent Context Isolation and Agent Orchestration. Each one is a separate skill with its own page in this directory, installs the same way Completion Check does, and is maintained by parcadei in that same repository. The rest of the collection is listed on the parcadei/Continuous-Claude-v3 page.

  • How does Completion Check compare to other Quality skills?

    Completion Check ranks #349 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Completion Check against them. Open each page to compare what they document and how they install.

More from parcadei/Continuous-Claude-v3

Completion Check is one of 25 skills cataloged on DirSkills from parcadei/Continuous-Claude-v3.

See all 25 skills
🔍
2w ago

AST-Grep Find

AST-Grep Find performs syntax-aware code search and refactoring using ast-grep patterns. Use it to find function calls, imports, and class definitions, or rename and replace code across a codebase.
Quality
3.9K296
🧠
2w ago

Agent Context Isolation

Agent Context Isolation prevents agent output from polluting the main context window by using background agents with file-based coordination instead of reading full transcripts. Use it when you need to preserve conversation context while delegating work to subagents.
AI Engineering
3.9K296
🤖
2w ago

Agent Orchestration

Agent Orchestration defines rules for delegating implementation tasks to subagents so the main context stays lean. Use it when planning multi-file features or following a plan phase to avoid burning context in the main chat.
AI Engineering
3.9K296
🤖
2w ago

Agentic Workflow

Agentic Workflow defines a multi-agent pipeline for implementation tasks in Claude Code, using background agents, file-based handoffs, and TDD. Use it to orchestrate research, planning, validation, implementation, and review without flooding the main context.
AI Engineering
3.9K296
🔌
2w ago

Agentica Claude Proxy

Agentica Claude Proxy connects Agentica SDK to Claude Code CLI through a local proxy so agents can use Read, Write, Edit, and Bash tools. Use it when setting up or debugging agent integrations, fixing permission errors, or preventing hallucinations.
AI Engineering
3.9K296
🧩
2w ago

Agentica Infrastructure

Agentica Infrastructure documents the Agentica multi-agent coordination APIs, including 11 pattern classes, primitives, and the coordination database schema. Use it when building multi-agent workflows, implementing custom patterns, or debugging agent tracking.
AI Engineering
3.9K296