Abilityai/abilities - Page 2

commit

Commit changed skill files and close the in-progress issue — writes a traceability commit message referencing the issue number

groom

Groom the backlog — tag untagged issues with skill:* labels, verify priorities, surface stale in-progress work

project-plan

Plan and execute large multi-session projects. Analyzes scope, splits into ordered sessions, executes session-by-session with approval gates and state tracking.

roadmap

Strategic view of the agent backlog — open issues grouped by skill, showing which areas have the most work

sprint

Human-supervised development cycle — orchestrates roadmap → claim → autoplan → implement → commit for one skill issue

work-loop

Autonomous work loop — pick one backlog issue, execute it, close it, exit. Re-invoked by scheduler for the next.

clone-cornelius

Clone the Cornelius agent repository and guide the user to open Claude Code inside it

add-testing

Add a Testing section to a feature flow document using the standard template.

autoplan

Auto-review pipeline — runs strategy, engineering, and security review in sequence and produces an implementation plan with auto-decisions. Used at the start of any In Progress issue.

commit

Commit, push, and link to GitHub Issues

cso

Security audit in CSO (Chief Security Officer) mode. --diff scans branch changes only; --comprehensive scans the full codebase. Checks secrets, dependencies, auth boundaries, injection vectors, and platform-specific patterns.

feature-flow-analysis

Create or update a feature flow document for end-to-end understanding of a feature.

generate-user-docs

Generate and update user-facing documentation from code, feature flows, and recent changes into docs/user-docs/

groom

Backlog grooming — audit board coverage, detect unranked items, review priority ordering, and propose rank updates. Requires human approval before applying any changes.

implement

End-to-end feature implementation from requirements to tests to documentation. Takes requirements file, GitHub issue, or description as input.

init

Initialize the dev-methodology in the current project. Scaffolds CLAUDE.md, memory files, workflow docs, and testing templates. Run once per project.

read-docs

Load all project documentation into context for this session.

refactor-audit

Audit codebase for refactoring candidates. Identifies complexity issues, large files/functions, code duplication, and maintainability problems. Outputs report to docs/reports/.

release

Cut a release — runs the pre-release checklist, bumps the version, generates release notes, creates and tags the release PR. Recommended to run after all in-dev issues are confirmed shippable.

review

Pre-landing code review for structural issues — SQL safety, race conditions, auth boundaries, credential exposure, scope drift, enum completeness, and test gaps. Produces a findings report with CRITICAL (block merge) and INFORMATIONAL categories.

roadmap

Query GitHub Issues for roadmap priorities and status

security-analysis

Perform OWASP-based security analysis of the codebase. Use when auditing code for vulnerabilities, before production deployment, or when reviewing authentication/authorization changes.

security-check

Pre-commit security validation. Scans staged/modified files for secrets, API keys, credentials, PII, and sensitive data before committing.

sprint

Full dev cycle orchestrator — runs the complete pipeline for an issue from claim through PR. Orchestrates autoplan, implement, review, cso, sync-feature-flows, and commit in sequence with human approval gates.

sync-feature-flows

Analyze code changes and update affected feature flow documentation. Creates new flows for new features, updates existing flows for modified code.

tidy

Audit and clean up repository structure. Identifies outdated docs, misplaced files, orphan configs, and test artifacts. Reports findings first and requires approval before making changes (except safe artifacts).

update-docs

Update project documentation after making changes. Updates changelog, architecture, feature flows, and requirements as needed.

validate-architecture

Validate the codebase against the architectural invariants documented in architecture.md. Checks naming conventions, dependency directions, API patterns, auth enforcement, and structural rules. Run weekly or before major releases.

validate-config

Check for drift in environment variable definitions across docker-compose.yml, .env.example, and the application codebase. Detects missing declarations, undocumented variables, and inconsistent defaults.

validate-pr

Validate a pull request against the project development methodology and generate a merge decision report.

validate-schema

Check for drift between schema definitions, migrations, and architecture documentation. Detects when the live schema diverges from what's documented or when migrations are out of sync with the model definitions.

batch-claude-loop

Orchestrate batch headless Claude Code calls - loop over inputs with clean context per iteration, collect structured results

bug-report

Create a sanitized GitHub issue from a production incident or bug. Redacts sensitive data (IPs, credentials, paths, user data) before submitting to a public or shared repo. Use after investigating an incident or when a reproducible bug is found.

docker-ops

Docker Compose service management over SSH. Subcommands: logs (view service logs with filtering), restart (graceful service restart), telemetry (CPU/memory/disk/container stats), cleanup (prune Docker resources, dry-run by default). Use for day-to-day…

investigate-incident

Structured production incident investigation. Collects evidence from logs, metrics, and DB, classifies severity, and produces a root cause report. Use when something is broken in production.

safe-deploy

Safe deployment workflow for SSH-accessible docker-compose stacks. Subcommands: update (backup→pull→rebuild→restart→validate), rollback (revert commit + optional DB restore), diagnose (health analysis). Use when deploying, rolling back, or checking deployment…

save-conversation

Save the current conversation as a structured markdown file for selective history preservation. Use when a conversation is worth keeping for future reference.

sync-ops-knowledge

Keep an ops agent's documentation current with codebase changes. Reviews recent commits in a managed codebase, analyzes operational impact (new config vars, API changes, schema changes), and proposes CLAUDE.md or skill updates. Use periodically or after a new…

create-note

Create a new permanent note in the Brain vault with proper metadata

search-brain

Search the Brain vault for notes matching a query