agentleFS
MarcusJellinghausMarcusJellinghaus/mcp-workspace/.claude/skills/implementation_approve/SKILL.md

implementation_approve

Skill49 starsChanged 2 days agoMITView on GitHub

Approve implementation and transition issue to PR-ready state

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If branch-status reports a base branch other than main, ask the user to confirm this is intentional before proceeding.

    line 17
  2. Very specific:

    Only if the report's Recommendations: line contains Ready to merge, run the set-status command and confirm it succeeded: The line is …

    line 19
  3. Very specific:

    Note: If Ready to merge is absent, report the blockers to the user and do not set the label.

    line 25
  4. Very specific:

    After the label is set, poll for the PR to be created and pass CI: Call mcp__mcp-workspace__check_branch_status.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Approve Implementation

Approve the implementation and transition the issue to PR-ready state.

Instructions:

  1. Run branch-status check: Call mcp__mcp-workspace__check_branch_status.
  2. If branch-status reports a base branch other than main, ask the user to confirm this is intentional before proceeding.
  3. Only if the report's Recommendations: line contains Ready to merge, run the set-status command and confirm it succeeded: The line is comma-separated (e.g. Recommendations: Ready to merge (squash-merge safe), ...); Ready to merge (squash-merge safe) counts. The match is case-sensitive: the blocking recommendation Not ready to merge (GitHub mergeable_state: ...) has a lowercase r and must not satisfy the check.
mcp-coder gh-tool set-status status-08:ready-pr

Note: If Ready to merge is absent, report the blockers to the user and do not set the label. If the set-status command fails, report the error to the user. Do not use --force unless explicitly asked.

Effect: Changes issue status from status-07:code-review to status-08:ready-pr.

  1. After the label is set, poll for the PR to be created and pass CI: Call mcp__mcp-workspace__check_branch_status.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.