From agent-almanac
Guides contributions to OpenClaw ecosystem projects via a 9-step workflow: target verification, parallel audit, false positive prevention, and PR creation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agent-almanac:polish-claw-projectThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Structured workflow for contributing to OpenClaw ecosystem projects. The novel value is in Steps 5-7: parallel audit, false positive prevention, and cross-referencing findings against open issues to select high-impact contributions. Mechanical steps (fork, PR creation) delegate to existing skills.
Structured workflow for contributing to OpenClaw ecosystem projects. The novel value is in Steps 5-7: parallel audit, false positive prevention, and cross-referencing findings against open issues to select high-impact contributions. Mechanical steps (fork, PR creation) delegate to existing skills.
repo_url — GitHub URL of the target Claw project (e.g., https://github.com/NVIDIA/NemoClaw)contribution_count — Number of contributions to aim for (default: 1-3)focus — Preferred contribution type: security, tests, docs, bugs, any (default: any)fork_org — GitHub org/user to fork into (default: authenticated user)Confirm the project accepts external contributions and is actively maintained.
CONTRIBUTING.md, CODE_OF_CONDUCT.md, and LICENSESECURITY.md or security policy if present — note responsible disclosure rulesExpected: CONTRIBUTING.md exists, commits within last 30 days, clear contribution guidelines.
On failure: If no CONTRIBUTING.md or no recent activity, document why and stop — stale projects rarely merge external PRs.
Create a working copy of the repository.
gh repo fork <repo_url> --clonegit remote add upstream <repo_url>git remote -v shows both origin (fork) and upstreamgit fetch upstream && git checkout main && git merge upstream/mainExpected: Local clone with both remotes configured and up to date.
On failure: If fork fails, check GitHub authentication (gh auth status). If clone is slow, try --depth=1 for initial exploration.
Build a mental model of the project architecture.
README.md for architecture overview and project goalsExpected: Clear understanding of project structure, conventions, and where contributions would fit.
On failure: If architecture is unclear, focus on a specific subsystem rather than the whole project.
Survey existing issues to understand project needs and avoid duplicate work.
gh issue list --state open --limit 50help wanted, good first issue, or hacktoberfestExpected: Categorized list of unclaimed issues with type labels.
On failure: If no open issues exist, proceed to Step 5 — audit may uncover unlisted improvements.
Run security and code quality audits in parallel. This is where novel findings emerge.
security-audit-codebase skill against the project rootreview-codebase skill with scope qualityExpected: List of verified findings with severity ratings and false positive annotations.
On failure: If no findings emerge, shift focus to test coverage gaps, documentation improvements, or developer experience enhancements.
Map verified audit findings to open issues — the core judgment step.
Expected: Prioritized list with finding-to-issue mapping and merge probability assessment.
On failure: If all findings are already addressed, return to Step 4 and look for documentation, test, or developer experience contributions.
Pick 1-3 contributions based on impact, effort, and expertise.
Expected: 1-3 selected contributions with clear scope and acceptance criteria.
On failure: If no contributions score well, consider filing well-written issues instead of PRs.
Create a branch per contribution and implement the fix.
git checkout -b fix/<description>Expected: Clean implementation with passing tests and no linter warnings.
On failure: If tests fail on pre-existing issues, document them and ensure the PR doesn't introduce new failures.
Submit contributions following the project's CONTRIBUTING.md.
git push origin fix/<description>create-pull-request skillExpected: PRs created, linked to issues, following project conventions.
On failure: If PR creation fails, check branch protection rules and contributor license agreements.
git fetch upstream && git merge upstream/main).npx claudepluginhub pjt222/agent-almanacOpen-source pull request creation: PR descriptions, titles, fork workflows, and contribution compliance. Invoke whenever task involves any interaction with pull requests for external repositories — contributing code, opening PRs from forks, writing PR descriptions, or preparing changes for upstream submission.
Hunts high-impact OSS contribution opportunities in trending GitHub repositories by discovering active repos, extracting help-wanted/good-first-issue/bug labels, analyzing feasibility, and generating dossiers with fix strategies.
Analyzes open-source GitHub libraries for contribution readiness. Produces structured Markdown reports on codebase structure, project lifecycle, and contribution paths.