acmeleme avatar

acmeleme

Official

@acmeleme

0Followers
|
2Public Repos
|
33Published Skills

Standardizes multi-squad governance, repository hygiene, and cross-platform coordination for distributed engineering teams using structured decision protocols and workspace configuration.

Skills Distribution
DomainDeveloper To...Governance & Compl.. (30%)Repository Managem.. (30%)Distributed Coordi.. (25%)Environment Config.. (15%)

Agent Skills by acmeleme

Showing 33 vetted skills indexed across 1 GitHub repositories.

acmelemeacmeleme

session-recovery

Query the session_store SQLite database to resume interrupted Copilot CLI sessions.

Official
Intermediate
acmelemeacmeleme

agent-collaboration

Standardize multi-agent collaboration with decision logging and reviewer workflows.

Official
Advanced
acmelemeacmeleme

reviewer-protocol

Enforce reviewer-driven rejections with strict lockout and reassignment rules.

Official
Advanced
acmelemeacmeleme

git-workflow

Automate squad-based Git workflows with dev/main/insiders branches.

Official
Advanced
acmelemeacmeleme

error-recovery

Apply standardized error-recovery patterns to agent workflows for transient failures.

Official
Intermediate
acmelemeacmeleme

squad-conventions

Standardize coding conventions for Squad CLI projects and PR reviews.

Official
Intermediate
acmelemeacmeleme

secret-handling

Block commits containing secrets and validate staged files against credential patterns.

Official
Advanced
acmelemeacmeleme

test-discipline

Update dependent test assertions and EXPECTED_* arrays after API changes.

Official
Intermediate
acmelemeacmeleme

architectural-proposals

Articulate architectural problems and proposed solutions in a structured, review-ready format.

Official
Advanced
acmelemeacmeleme

pr-review-response

Post replies to PR review threads referencing fixes and optionally resolve them.

Official
Intermediate
acmelemeacmeleme

distributed-mesh

Generate mesh.json and copy sync scripts for git-backed multi-squad coordination.

Official
Advanced
acmelemeacmeleme

history-hygiene

Record final decision outcomes to history.md after confirmation.

Official
Intermediate
acmelemeacmeleme

Ralph — Two-Pass Issue Scanning

Split GitHub issue scanning into a lightweight pass and selective hydration pass.

Official
Intermediate
acmelemeacmeleme

iterative-retrieval

Enforce a max-3-cycle sub-agent spawn protocol with WHY context and coordinator validation.

Official
Advanced
acmelemeacmeleme

docs-standards

Apply Microsoft Style Guide patterns to squad documentation for consistency.

Official
Basic
acmelemeacmeleme

reskill

Audit agent charters and histories to create reusable skills under .squad/skills.

Official
Advanced
acmelemeacmeleme

notification-routing

Route agent notifications by type to dedicated team channels.

Official
Intermediate
acmelemeacmeleme

client-compatibility

Detect execution surfaces and select agent spawning strategies across CLI and VS Code.

Official
Advanced
acmelemeacmeleme

reflect

Extract and categorize conversation learnings by confidence level for storage.

Official
Advanced
acmelemeacmeleme

project-conventions

Standardize code project conventions and patterns with template-driven configuration.

Official
Basic
acmelemeacmeleme

init-mode

Propose a squad roster and initialize the .squad workspace after user confirmation.

Official
Advanced
acmelemeacmeleme

gh-auth-isolation

Detect GitHub identities and switch gh config contexts per operation.

Official
Advanced
acmelemeacmeleme

ci-validation-gates

Apply defensive gating checks to CI/CD publish workflows for semver, tokens, and retries.

Official
Advanced
acmelemeacmeleme

github-multi-account

Detect multiple GitHub accounts and configure persistent gh personal/work aliases.

Official
Advanced

Frequently Asked Questions About acmeleme

FAQPage Schema
What specific engineering tasks are enabled by these capabilities?

These capabilities enable standardized repository governance, automated credential scanning, multi-account identity management, and structured decision logging. They facilitate consistent pull-request reviews, cross-squad project coordination via mesh manifests, and standardized error-recovery patterns for distributed development environments.

Which personas benefit most from these technical standards?

Engineering leads, DevOps architects, and squad coordinators benefit from these standards. They are designed for teams managing complex, multi-repository projects who require strict adherence to semantic versioning, documentation consistency, and secure credential handling across distributed development squads.

What are the prerequisites for implementing these squad conventions?

Implementation requires a GitHub-centric environment and a standardized directory structure utilizing the .squad configuration format. Users must have local access to SQLite for session state management and maintain consistent branch naming conventions across dev, main, and insiders environments.